Title: Adaptive Development Methodology with Scrum
1 UNLEASHING the FOSSA
Agile Leadership Summit Orlando, Florida
November 2008
Scaling Agile in an AMBITIOUS CULTURE
Steve Greene, salesforce.com
2(No Transcript)
3(No Transcript)
4(No Transcript)
5History
6from the beginning
73
Number of people in RD
8innovative
smart
fast
94
Number of Major Releases per year
107 years later
11rapid success
1247,700
Customers
131,100,000
Subscribers
1410 Billion
transactions per quarter
15500
people in RD
16it was getting more difficult to deliver
17Days between Major Releases
Features Delivered per Team
2000 2001 2002 2003
2004 2005 2006
181
Number of Major Releases in 2006
19Why?
20Lack of visibility
21Resource Bottlenecks
22Unpredictable completion of projects or
initiatives
23Lack of responsiveness, lack of team alignment
on priorities
24Unhappy Customers
25What did we do about it?
26Major enterprise-wide Agile Transformation to ADM
In just 3 months another 18 months of
continuous improvement
27I knew we needed radical change to get us back on
track to regular releases and agile delivered.
Parker Harris Founder and Executive Vice
President, Technology Salesforce.com
28Transformation Results
Features Delivered per Team
Days between Major Releases
2000 2001 2002 2003
2004 2005 2006 2007
29ADM has delivered total visibility, total
transparency and unbelievable productivity a
complete win!
Steve Fisher Sr. Vice President, Platform
Product Management Salesforce.com
30On time delivery?
Last waterfall release
31Simple is better. With our agile approach to
product development we've put our amazing people
in charge. They work as a team to do the right
thing for the customers, their fellow employees
and our shareholders.
Todd McKinnon Sr. Vice President, Research
Development Salesforce.com
3261
improvement in mean time to release for major
releases in our first agile year
3338
Increase in feature requests delivered per
developer in our first agile year
34(No Transcript)
3588
of respondents believe the quality of our
products have improved or stayed the same
3689
of respondents are having the best time or a
good time at Salesforce
Improved from 40 18 months ago
3794
of respondents would recommend ADM to their
colleagues inside or outside Salesforce
38 39What is ADM?
ADM is a modified Scrum/XP style of product
development that is specific to Salesforce. It
employs Scrum project management framework,
adopts certain XP practices and is based on lean
principles.
40What is ADM?
Self-organizing
Continuous integration
Lean
Agile
Self-correcting
Time-boxed
Ftest - Selenium
Re-factoring
User stories
Collective Code Ownership
Transparent
Iterative
Just-in-time
Code Reviews
Debt free
Predictable releases
Early feedback
Always Potentially Releasable
Scrum of (Scrum of Scrums)
Seasonal Planning Rhythm
41The Rollout
42Created a dedicated, cross-functional rollout team
43 Everyone jumped in together
44Positioned as a return to our core values
45Iterate
KISS
Listen to your customers
46Distributed Ken Schwabers Scrum book Developed
2-hour Agile overview
47Sent 30 ScrumMasters to ScrumMaster
CertificationSent 35 Product Managers to
Product Owner Certification
48Created weekly ScrumMaster and Product Owner
forums
49Created internal, wiki-based website as a
reference for team members
50Just get started. (the rest will come later)
51Change isnt easy. (get ready to be hated)
52Scrum doesn't account for the fact of the
reality of the waterfall. You cannot deny this
by superimposing scrum over it.
Management is not proactive as we wait for
decisions from management. Scrum gives me the
feeling that Big Brother is watching and
monitoring everything we do
It seems like we spend more time talking about
scrumthan we spend time talking and working on
salesforce.com.
In many ways, scrum seems like an inflexible,
bureaucratic process akin to something at the
Department of Motor Vehicles. ditch the
stupid annoyingly dumb excel spreadsheet.
53They dont like us. (and may never like us again)
54Team is effective but productivity is lower
Stop trying to implement scrum, and look at how
many releases we can really do in a year.
Lack of innovation. No innovation. I can't
innovate. I am at the mercy of my product owner,
who cares not for innovation, only the chirpings
of customers...
We've managed to take a lightweight process and
attach enough to it to make it just as bad as
our previous process, good job!
Scrum does not meaningfully affect the team's
effectiveness it is structure and process that
often distracts the team from their goal, and can
be used to micromanage the team.
The lingo is ridiculous
55But, they got over it.
56And. Finally. The rollout is over! (but were
not done)
57Now for the later stuff.
58Continuous Improvement
59Continuous Improvement
60Continuous Improvement Excellence Expansion
October
January
April
October
July
April
July
2009
2008
61Dont be like us. (or what would wed do
differently)
62 Involve more individual contributors early
63 Provide team members more training earlier and
with more intensity
64 Get outside coaching earlier
65 Key executives should take concrete deliverables
around the rollout
66Keys to success?
67Ensure executive commitment to the change
68 Focus on principles over mechanics
69 Focus on getting several teams to excellence
70Provide radical transparency
71Automation
27967
16332
5752
2656
72(No Transcript)
73 When the heat is on stick to your guns
74We failed. (all along the way)
75 Experiment, be patient and expect to make
mistakes
76 You cant afford to NOT change your organization
to deliver growth
77More information about ADM
- http//www.slideshare.net/sgreene/slideshows
- Tags ADM, agile, scrum, salesforce.com
78(No Transcript)