Agile Project Elaboration: Seed Money
by Kelly Waters
In traditional waterfall projects, it's quite common to have a two-stage approval process, especially when it comes to raising funds to develop a new idea.Stage 1 approval provides sufficient funding to get a project started and complete the analysis phase. Once analysis has been completed and a detailed specification written, the project can be more accurately estimated and a further request is made for full funding of the project.
So how would you tackle an agile project with this kind of approach to the funding?
First of all, this two-stage approval process for funding a new project is still valid with an agile approach. It's simply an unavoidable reality that some work has to be done before a project can be reasonably well understood and estimated. And this work, unless there's a permanent team already in place, needs funding before an investment decision can be made.
So, in an agile project, what outputs might you produce with the initial funding? You certainly wouldn't want to complete a full analysis phase and detailed specification. But you would need something.
Here are some ideas:
- Visuals or Wireframes
- Research (User/Customer/Market Research)
- Prototype
- Proof of Concept
- Technical Feasibility Study
- Initial Product Backlog (feature list)
- High-level Architecture
- Technology Selection
- Estimates
- Team/Resource Requirements
- Release Plan/Product Roadmap
- Costs
- Business Case
- Project Initiation Presentation
If initial funding permits, you may also be able to establish the project team and complete a few short sprints, in order to understand the team's Velocity for planning purposes. But this would depend not only on the initial funds available, but also on the likelihood of full approval.
Kelly.
P.S. Click one of the icons below to join the growing community of people keeping up with this blog by RSS or by email...
Photo by tico bassie
13 October 2008 14:57
This is a good post about a somewhat missed area within agile application. I like your points.
As I'm reading it, I'm getting an impression about the customer. In the early stages of product development, your customer is the VC, fundraiser, or management team that will review and approve the budget. The concept of demonstrable is much lighter and wireframes might be enough.
Once the budget is approved, then the customer shifts to include users, and demonstrable must be a working system.
Cool post!
Kevin E. Schlabach
agile-commentary.blogspot.com