I will try to summarize the process of both management practises in the following points.
The waterfall project
- Complete Specification Documentation
- Complete Requirement Documentation
- Complete Risk Analysis and Mitigation documentation
- Actual development of the tasks + buffer available for unforeseen risks
Agile Projects
- Just enough Specifications per sprint
- Just enough requirement per sprint
- Risk assessment only for the sprint
- Actual development of task + no buffer for risks as all unforeseen risks and unplanned specs will be added as a new backlog item
So when we talk about running waterfal projects like agile what does that mean?
As the project costing has anyway to be done hence the specification and requirement process must be done anyway. I am still not sure whether running waterfall projects like agile can even be done. My thoughts may mature after some days of time spent on the idea.
Till then
with regards
Tushar Joshi, Nagpur
Hi Tushar, well, the reverse has been done -- i mean, an overall agile project having waterfall model for each sprint -- for a documentation project.
ReplyDeleteYour idea is intriguing and will give some thought to it.