2. For Many of Us Using Traditional
Software Development Methods…
Time-to-market for projects is too long
Project failure rate is unacceptably high
ROI of projects frequently falls short
Responding to change is difficult and costly
Customer collaboration is a problem
Software quality is poor
Productivity could be higher
Employee morale, drive and accountability is weak
Widespread micromanagement is required
Employee retention rates are low
Software development is much harder than it should be!
3. The Emergence of Agile
The major Agile methods – Scrum, XP, TDD – are
growing in popularity around the world
Rapid growth in last 3-5 years at leading global
companies, such as:
Google Microsoft
IBM Infosys
Siemens Wipro
Nokia Motorola
Philips HP
Accenture TCS
4. The Basics of Scrum
Scrum Daily Scrum
Master Meeting
4-Week
Sprint
Review
Product Owner The Team
1
2
Commitment
3
4
Potentially
5
No Changes
Sprint
6
Shippable
Planning
7
Product
8
Meeting (in Duration or Deliverable)
9
10
11
12
13
Retrospective
Product Backlog
5. Scrum vs. Previous Approach:
Productivity / How much team got done?
5% 68%
Scrum WORSE or MUCH WORSE Scrum BETTER or MUCH BETTER
50%
45%
40% +36%
Average
35%
Increase
30%
25%
20%
15%
10%
5%
0%
Scrum
Scrum Much
Scrum MUCH about Scrum MUCH
Scrum Much
Scrum About Scrum
WORSE WORSE same BETTER BETTER
Worse
Worse Better
the Same Better
6. Scrum vs. Previous Approach:
Morale?
9% 52%
Scrum WORSE or MUCH WORSE Scrum BETTER or MUCH BETTER
35%
30%
25%
20%
15%
10%
5%
0%
Scrum
Scrum Much Scrum Much
Scrum About Scrum
Scrum MUCH about Scrum MUCH
Worse
Worse
WORSE WORSE same BETTER BETTER
Better
the Same Better
7. Scrum vs. Previous Approach:
Sense of accountability/ownership in project?
6% 62%
Scrum WORSE or MUCH WORSE Scrum BETTER or MUCH BETTER
35%
30%
25%
20%
15%
10%
5%
0%
Scrum
Scrum Much Scrum Much
Scrum About Scrum
Scrum MUCH about Scrum MUCH
Worse
Worse
WORSE WORSE same BETTER BETTER
Better
the Same Better
8. Scrum vs. Previous Approach:
Collaboration and cooperation in the team?
1% 81%
Scrum WORSE or MUCH WORSE Scrum BETTER or MUCH BETTER
45%
40%
35%
30%
25%
20%
15%
10%
5%
0%
Scrum
Scrum Much Much
Scrum About Scrum
Scrum MUCH Scrum Scrum about Scrum Scrum MUCH
Worse
Worse
WORSE WORSE the same BETTER BETTER
Better
the Same Better
9. Scrum vs. Previous Approach:
Overall quality of what was developed?
10% 44%
Scrum WORSE or MUCH WORSE Scrum BETTER or MUCH BETTER
45%
40%
35%
30%
25%
20%
15%
10%
5%
0%
Scrum
Scrum Much Scrum Much
Scrum About Scrum
Scrum MUCH about Scrum MUCH
Worse
Worse Better
the Same Better
WORSE WORSE same BETTER BETTER
10. If the decision were solely up to you,
would your team continue using Scrum?
No 15%
Yes 85%
11. Scrum Disadvantages
It’s hard!
Makes all dysfunction visible
Scrum doesn’t fix anything: the team has to do it
Feels like things are worse at the beginning
Bad products will be delivered sooner, and
doomed projects will fail faster
Some teams and organizations are not right or
ready for it
Team willingness
Management buy-in and support
Risk of turnover
Partial adoption may be worse than none at all
Failure can be costly