In my last post, I said that I was committing to a dodeca-thalon of posts on the Agile Manifesto — one for each Agile principle. I think this is great stuff that everyone should be exposed to. If you use Agile, or wonder why people are so hot for Agile, this series is for you.

And with that intro, here’s #2 of 12

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

Everything changes. Software is not set in stone, and even if it was set in stone, it would still change. So, we need a process that gracefully handles change. Part of this trick is by getting rid of the idea of a 12-week project, and instead having 12, 1-week projects. You want to have small, frequent plans.