Agile Manifesto

The Agile Manifesto was written in February of 2001, at a summit of seventeen independent-minded practitioners of several programming methodologies. The participants didn’t agree about much, but they found consensus around four main values :

  • Individuals and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan.

Supplementing the Manifesto, the Twelve Principles further explicate what it is to be Agile.

Lets dig deeper on the Four core values of the Agile Manifesto.

Individuals and interactions over processes and tools:

Encourage self-organization and collaboration: they are keys to success. Help them learn how to work effectively by means of experiment, fast feedback loops and safe failure. Help them see their conflicts and to choose what to do about them.

Working software over comprehensive documentation

Help people to get things done. Teach, mentor and coach on Agile technical practices, both individuals and teams. Stimulate a culture of SW craftsmanship in your company, based on mastery and apprenticeship, excellence and deliberate practice, ability to find solutions to always new problems.

Customer collaboration over contract negotiation

Teach and coach your company on Agile values and Lean principles, so that they can be more effective on the market. Have business and development like one team: teach them not to play the contract game inside the same company. Promote a culture of continuously creating learning, by means of close collaboration with the customer on the product.

Responding to change over following a plan

Train your team and organization to be able to keep as many options open as possible until the very last responsible moment and make informed decisions. Enable cross-functionality and peer approaches to be more flexible to change. Coach your organization to always look at the big picture to focus on the most important stuff, validate hypothesis instead of blindly follow plans and change direction when needed.

Hope that was helpful.


Agile Manifesto