Why move to Scrum ?
17
Why move to Scrum ? Elad Sofer agile coach.
-
Upload
elad-sofer -
Category
Technology
-
view
813 -
download
0
description
Short presentation that describes some of the motivations behind moving to Scrum.
Transcript of Why move to Scrum ?
Why move to Scrum ?
Elad Soferagile coach.
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.
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.
0
10
20
30
40
50
60
10 100 1000 10000 100000
Project Size in Function Points
Req
uir
em
en
ts c
han
ge
Ever changing requirements [Jones97] and [BP88]
Problem: Unused features
Actual use of requested features [Johnson02]
always, 7%
sometimes, 16%
often, 13%
rarely, 19%
never, 45%
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.
Problem: Project length
Project length vs. success [Johnson98]
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.
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)
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.
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.
Agile surveys results
Following is some data from recent surveys about agile projects
Quality level
A survey to show change in quality after transition to agile.
0%2%
21%
32%13%
32%
Much Lower
Somewhat Lower
No Change
Somewhat Higher
Much Higher
Don't Know
Agile adoption survey [Ambler06]
Customer satisfaction
A survey to show change in business stakeholder satisfaction after transition to agile.
1%2%
39%
41%
17%
Much Lower
Somewhat Lower
No Change
Somewhat Higher
Much Higher
Agile adoption survey [Ambler06]
Project success rate
A survey to show What percentage of Agile projects have been successful.
State of agile [VersionOne08]
Productivity
A survey to show change in productivity after transition to agile.
0%2%
21%
32%13%
32%
Much Lower
Somewhat Lower
No Change
Somewhat Higher
Much Higher
Don't Know
Agile adoption survey [Ambler06]
Overall improvement
A survey to show specific improvements that were realized from implementing Agile practices?
State of agile [VersionOne08]
Thank you.
Elad SoferAgile coach
