No planning, no documentation, no problem. That is the Agile development approach right? Well, I might be new to this Agile approach, but I would argue it’s MORE. I am a Project Manager by heart, so NO planning and NO documentation is simply unacceptable. Sorry Dilbert. Seeing how Agile Development is a buzz lately, I figured I would approach this topic from a Strategist’s point of view.
So, what is this Agile Development thing?
Doing a quick search of Agile Development you will get several different definitions. Most all of them say its a hard term to define. The key words you will see are “evolve”, “collaboration”, “iterative” and “cross-functional teams.” However you want to define it, we love agile development because it provides us the freedom to make decisions as we go.
What is the process for Agile Development?
Well…Agile :) We start out with a charter, a mission statement for where we are going. This will be our flag ship document that everything is based on upfront. From there, we plan for the checkpoints to review progress and analyze results. With each milestone that comes it is expected that timelines will adjust. Tasks may be completed quicker, we may add more work to the task. Revisions come as needed, but always with purpose.
When taking on an Agile project I look to document the process. Documentation is the best way to track and show results. From a strategist point of view taking on an Agile Development project can be a bit intimidating. Since Strategists are ultimately responsible for scope, timeline and budget; Agile development may seem like herding cats. We need to defend decisions with documentation.