Today, I took a look at the Agile Manifesto, the document signed by agile gurus such as Ken Schwaber, Jeff Sutherland, Mike Beedle, Alistair Cockburn, Kent Beck, and others at UtahÂ’s Snowbird Ski Resort in 2001. Most folks who have worked in an agile environment know the manifesto well (if not, you should check it out: http://agilemanifesto.org/ ). IÂ’ve noticed that, the longer I use agile, the more deeply I understand the principles that inform the manifesto. For instance, a different part of the document (from the Â“Twelve Principles of Agile SoftwareÂ” section) made an impression on me today:
Â“Welcome changing requirements, even late in development.Â”
That sentiment, to me, really gets at how agile is committed to building products that customers want. ThereÂ’s always a premium on completing work, but this line reminds that, in agile, a projectÂ’s not really complete if it fails to meet the expectations of the customer. Even the wording in the manifesto hits me as radical. How often, when youÂ’ve nearly wrapped a demanding project, would you Â“welcomeÂ” a sweeping scope change that meant your work was far from done? IÂ’d wager the answer is Â“never.Â” But in the iterative, incremental paradigm of agile, the focus isnÂ’t just on churning out product Â— itÂ’s on producing the Â“rightÂ” product.
Posted under Agile Methodology
This post was written by admin on November 21, 2008