Why move to Scrum ?
This presentation provides reasons for switching from a waterfall development model to Scrum. The waterfall model is not well-suited to handle changing requirements, produces many unused features due to its lack of flexibility, and reduces chances of project success due to its relatively long length. In contrast, Scrum is designed to handle frequent changes, prioritize and build only high-value features through quick feedback cycles, and takes a more iterative approach to development in shorter cycles. Scrum also aims to improve quality, visibility, and reduce costs through its emphasis on these factors. Finally, the document references surveys that show benefits to quality, customer satisfaction, success rates, and productivity realized by organizations after adopting Agile practices like Scrum.
![Problem: Changing requirements The bigger the project the more changes will occur. The waterfall model is not designed to handle changes. The Scrum model is designed to handle frequent changes. Ever changing requirements [Jones97] and [BP88]](https://image.slidesharecdn.com/whymovetoagile-110330054457-phpapp01/85/Why-move-to-Scrum-3-320.jpg)
![Problem: Unused features Actual use of requested features [Johnson02]](https://image.slidesharecdn.com/whymovetoagile-110330054457-phpapp01/85/Why-move-to-Scrum-4-320.jpg)
![Problem: Project length Project length vs. success [Johnson98]](https://image.slidesharecdn.com/whymovetoagile-110330054457-phpapp01/85/Why-move-to-Scrum-6-320.jpg)
![Quality level A survey to show change in quality after transition to agile. Agile adoption survey [Ambler06]](https://image.slidesharecdn.com/whymovetoagile-110330054457-phpapp01/85/Why-move-to-Scrum-12-320.jpg)
![Customer satisfaction A survey to show change in business stakeholder satisfaction after transition to agile. Agile adoption survey [Ambler06]](https://image.slidesharecdn.com/whymovetoagile-110330054457-phpapp01/85/Why-move-to-Scrum-13-320.jpg)
![Project success rate A survey to show What percentage of Agile projects have been successful. State of agile [VersionOne08]](https://image.slidesharecdn.com/whymovetoagile-110330054457-phpapp01/85/Why-move-to-Scrum-14-320.jpg)
![Productivity A survey to show change in productivity after transition to agile. Agile adoption survey [Ambler06]](https://image.slidesharecdn.com/whymovetoagile-110330054457-phpapp01/85/Why-move-to-Scrum-15-320.jpg)
![Overall improvement A survey to show specific improvements that were realized from implementing Agile practices? State of agile [VersionOne08]](https://image.slidesharecdn.com/whymovetoagile-110330054457-phpapp01/85/Why-move-to-Scrum-16-320.jpg)
Why move to Scrum ?
- 1. Why move to Scrum ? Elad Sofer agile coach.
- 2. Moving to Scrum Before changing the way of working, there is a need to get buy-in from the people that are involved. This presentation will present some good reasons to change the mindset to a more agile mindset and the project’s development method to Scrum.
- 3. Problem: Changing requirements The bigger the project the more changes will occur. The waterfall model is not designed to handle changes. The Scrum model is designed to handle frequent changes. Ever changing requirements [Jones97] and [BP88]
- 4. Problem: Unused features Actual use of requested features [Johnson02]
- 5. Problem: Unused features The waterfall model because of it’s low flexibility produces many unused features Scrum is designed to constantly prioritize and build only the highest value features that reduces unused features because of low value. Scrum is designed with quick feedback cycles that reduces significantly unused features due to misunderstanding. Customers are not programmed to think of everything in advance.
- 6. Problem: Project length Project length vs. success [Johnson98]
- 7. Problem: Project length The waterfall model is designed to be relatively long hence reduces the chances of success. Scrum is designed to is a way that the development is actually a sequence of mini non-waterfall projects the increases chances of success.
- 8. Problem: Cost of low quality The most obvious thing about low quality is that it triggers changes (in code, in requirements etc.). So a major factor should be the cost of change. Original, in waterfall New, in agile (Boehm) (Beck)
- 9. Problem: Cost of low quality The waterfall model is usually driving us to meet the content (milestones) and have no “in process” drive to quality”. Scrum is designed to put quality as the main driver, the assumption being that the cost of low quality is too high.
- 10. Problem: Low visibility The waterfall model is not transparent, and due to many reasons it is very hard to manage it and really have a clear understanding of the state. Scrum is designed to keep a very high level of visibility exposing risks and problems at a very early stage in the project’s lifecycle.
- 11. Agile surveys results Following is some data from recent surveys about agile projects
- 12. Quality level A survey to show change in quality after transition to agile. Agile adoption survey [Ambler06]
- 13. Customer satisfaction A survey to show change in business stakeholder satisfaction after transition to agile. Agile adoption survey [Ambler06]
- 14. Project success rate A survey to show What percentage of Agile projects have been successful. State of agile [VersionOne08]
- 15. Productivity A survey to show change in productivity after transition to agile. Agile adoption survey [Ambler06]
- 16. Overall improvement A survey to show specific improvements that were realized from implementing Agile practices? State of agile [VersionOne08]
- 17. Thank you. Elad Sofer Agile coach