Agile
Download as PPTX, PDF0 likes455 views
The original cost estimate for the project was $100 million with a planned completion in 5 years, however the actual completion was in 2003 and cost $274 million. Mrs. Disney, who initially donated $50 million, died in 1997 before seeing the project completed. A previous project estimated completion in 1963 at $7 million, but was actually finished 10 years late and over budget by over 14 times the original estimate.
Agile
- 1. Original cost estimate in 1987 was $100 million and completion in 5 years. Actual completion in 2003 and cost $274 million. Mrs. Disney died at the age of 98 (1997), 10 years after her initial donation ($50 million) but before she could see her tribute completed.
- 2. Original cost estimate in 1957 was $7 million and completion date was 26 January 1963 The project was completed 10 years late and over-budget by more than 14 times.
- 3. Fixed Requirements Estimated Resource Estimated Time Guess Driven Waterfall changes because of better understanding of requirement Changes Because of market and technology Measure twice, cut once
- 4. Estimated Features Fixed Resource Fixed Time Priority Driven Agile changes because of better understanding of requirement Changes Because of market and technology Less important features may not be implemented Less important features may be postponed Big rocks in first
- 5. Do not finish entire layers by layers Finish a slice of cake
- 7. Requirements Design Development Testing Deploy Design Develop TestIntegrate Deployme nt Design Develop TestIntegrate Deployme nt Design Develop TestIntegrate Deployme nt Return $ Time Why Agile has less risk and better return?
- 12. Pair programming Less QA, Better quality, cross functional training
Editor's Notes
- #4: Assume Knowledge at the beginning: Water Fall (managing time/budget to meet “unclear” requirements), rear facing (are we meeting our budget/schedule goal?) Assume we will know better at each iteration: Agile managing productivity and priority, forward looking are we learning from what we learned and produce more in the order of importance Spending too much measuring and still end up cutting multiple times Do we know better at the beginning or end of the project? (focusing delivery early value, fail quick, just-in-time planning and simplicity)
- #5: Assume Knowledge at the beginning: Water Fall (managing time/budget to meet “unclear” requirements), rear facing (are we meeting our budget/schedule goal?) Assume we will know better at each iteration: Agile managing productivity and priority, forward looking are we learning from what we learned and produce more in the order of importance Continuous improvement Just in time planning/designing/implementing (focusing delivery early value, fail quick, just-in-time planning and simplicity)
- #8: Agile: assume we will know better on the scope and productivity after each cycle Agile plans more but in simple way. Agile looks forward. Better return on investment, cash flow and less risks
- #9: Myth of agile (no planning, no documentation, results focusing, continuous improvement, refactoring
- #10: A framework, not a methodology Getting things done/results Cross functional Not reporting status, but plan/estimate future Add a slice cake, instead of building layers after layers
- #13: Borrowed from XP (pair programming, user stories- how to , TDD)