Principles behind the Agile Manifesto (Principles the signatories follow)

The Agile Manifesto (Team Desh Apnayen Mod)

See the original here.

Our highest priority is to satisfy the customer stakeholder
through early and continuous delivery
of valuable software engagement options.

Welcome changing requirements, even late in
development in the intervention cycle.
Agile processes harness change for
the customer’s competitive advantage.

Deliver working software outcome-based activities
frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale.

Business people Stakeholders, authors and
developers must work together daily
throughout the project.

Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

The most efficient and effective method of
conveying information to and within a developmental
team is face-to-face over video or in-person conversation.

Working software is the primary measure of progress.

Agile processes promote sustainable development.
The sponsors, developers, and users should be able
to maintain a constant pace indefinitely.

Continuous attention to technical excellence
and good design enhances agility.

Simplicity–the art of maximizing the amount
of work not done–is essential.

The best architectures, requirements, and designs
emerge from self-organizing teams.

At regular intervals, the team reflects on how
to become more effective, then tunes and adjusts
its behavior accordingly.