Why move to Scrum ?

1,114 views
941 views

Published on

Short presentation that describes some of the motivations behind moving to Scrum.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,114
On SlideShare
0
From Embeds
0
Number of Embeds
23
Actions
Shares
0
Downloads
28
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Why move to Scrum ?

  1. 1. Why move to Scrum ? Elad Sofer agile coach.
  2. 2. Moving to Scrum <ul><li>Before changing the way of working, there is a need to get buy-in from the people that are involved. </li></ul><ul><li>This presentation will present some good reasons to change the mindset to a more agile mindset and the project’s development method to Scrum. </li></ul>
  3. 3. Problem: Changing requirements <ul><li>The bigger the project the more changes will occur. </li></ul><ul><li>The waterfall model is not designed to handle changes. </li></ul><ul><li>The Scrum model is designed to handle frequent changes. </li></ul>Ever changing requirements [Jones97] and [BP88]
  4. 4. Problem: Unused features Actual use of requested features [Johnson02]
  5. 5. Problem: Unused features <ul><li>The waterfall model because of it’s low flexibility produces many unused features </li></ul><ul><li>Scrum is designed to constantly prioritize and build only the highest value features that reduces unused features because of low value. </li></ul><ul><li>Scrum is designed with quick feedback cycles that reduces significantly unused features due to misunderstanding. </li></ul><ul><li>Customers are not programmed to think of everything in advance. </li></ul>
  6. 6. Problem: Project length Project length vs. success [Johnson98]
  7. 7. Problem: Project length <ul><li>The waterfall model is designed to be relatively long hence reduces the chances of success. </li></ul><ul><li>Scrum is designed to is a way that the development is actually a sequence of mini non-waterfall projects the increases chances of success. </li></ul>
  8. 8. Problem: Cost of low quality <ul><li>The most obvious thing about low quality is that it triggers changes (in code, in requirements etc.). </li></ul><ul><li>So a major factor should be the cost of change. </li></ul>Original, in waterfall New, in agile (Boehm) (Beck)
  9. 9. Problem: Cost of low quality <ul><li>The waterfall model is usually driving us to meet the content (milestones) and have no “in process” drive to quality”. </li></ul><ul><li>Scrum is designed to put quality as the main driver, the assumption being that the cost of low quality is too high. </li></ul>
  10. 10. Problem: Low visibility <ul><li>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. </li></ul><ul><li>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. </li></ul>
  11. 11. Agile surveys results Following is some data from recent surveys about agile projects
  12. 12. Quality level <ul><li>A survey to show change in quality after transition to agile. </li></ul>Agile adoption survey [Ambler06]
  13. 13. Customer satisfaction <ul><li>A survey to show change in business stakeholder satisfaction after transition to agile. </li></ul>Agile adoption survey [Ambler06]
  14. 14. Project success rate <ul><li>A survey to show What percentage of Agile projects have been successful. </li></ul>State of agile [VersionOne08]
  15. 15. Productivity <ul><li>A survey to show change in productivity after transition to agile. </li></ul>Agile adoption survey [Ambler06]
  16. 16. Overall improvement <ul><li>A survey to show specific improvements that were realized from implementing Agile practices? </li></ul>State of agile [VersionOne08]
  17. 17. Thank you. Elad Sofer Agile coach

×