Agile Manifesto: 12 principles that help businesses build products that their customers will love and value

Why was the Agile Manifesto written?

Photo by Thought Catalog on Unsplash
  • Focus on individual interactions over processes and tools.
  • Deliver working software over comprehensive documentation.
  • Build trust through collaboration with the customer instead of contract negotiations.
  • Adapt and respond to change, more than following a plan.

The importance of the 12 Agile principles

Photo by Clayton Robbins on Unsplash

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

Photo by Jon Tyson on Unsplash

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

Photo by Nick Fewings on Unsplash

3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference for the shorter timescale.

Photo by Agê Barros on Unsplash

4. Business people and developers must work together daily throughout the project.

Photo by Alvaro Reyes on Unsplash

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

Photo by Mika Baumeister on Unsplash

6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Photo by LinkedIn Sales Solutions on Unsplash

7. Working software is the primary measure of progress within the 12 agile principles.

Photo by Christian Kaindl on Unsplash

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

Photo by sporlab on Unsplash

9. The 12 agile principles place the emphasis on continuous attention to technical excellence and that good design enhances agility.

Photo by Hal Gatewood on Unsplash

10. Simplicity — the art of maximizing the amount of work not being done — is essential.

Photo by Alex Kotliarskyi on Unsplash

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

Photo by ZACHARY STAINES on Unsplash

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

Photo by Drew Patrick Miller on Unsplash





Financial Independence | Remote Working

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

What!? Product Operation (產品運營) in China?

Building a quality-centric culture

Build empathy with your team members. Why?

Minimum Business Increment (MBI): When Is It a More Profitable Choice Over Minimum Viable Product…

Three Essential On-boarding Questions

Interview with the client. Quick start of the project

Usability Index for any product feature

How Quality Changes with Product Maturity

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Kape Chur Company

Kape Chur Company

Financial Independence | Remote Working

More from Medium

PRODUCTHEAD: Rearranging the deckchairs


Is a programmer’s itch more important than the customer’s needs?

Management buzzwords explained: Lean, Agile and Design Thinking