Why everyone must follow Agile Manifesto

The Agile Manifesto was?written in 2001 by seventeen independent-minded software practitioners. At the end of the agile manifesto,?they put more value on the items on the left?than they do value items on the right.?Over the years, the Agile manifesto?has become a battle cry for organizational transformation.

Individuals and interactions?over processes and tools

Working software?over comprehensive documentation

Customer collaboration?over contract negotiation

Responding to change?over following a plan

Breaking down Agile principles:

• Principle 2 is about welcoming changes.??
• Principles 3 and 7,?refer to continuous software/Product delivery in weeks?as a measure of progress.
• Principle 4 describes?how customers should work closely with the development team.??
• Principles 5 and 11?talk about #motivated self-organized teams.?
• Principles 1, 8, 9, and 10 starts to introduce you to the idea of prioritizing?high-value work.?
• ?Principle 6?describes the importance of face-to-face conversations.?
• Principle 12 encourages the team?to meet frequently to discuss process improvement.?

These 12 principles in the Manifesto?start to lay some of the groundwork?for what your team will actually do?to deliver great #products. Every PM and development engineer must refer to this agile manifesto for delivering successful products and projects.

#changemanagement #agiledevelopment