YEAR   O F  L I V I N G  DANGEROUSLY Steve  Greene  |  Chris  Fry Scrum Gathering Conference, Chicago  April 2008 How Sale...
 
 
History
8 Age of Salesforce in years
from the beginning
3 Number of people in R&D
fast innovative smart
4 Number of Major Releases per year
7 years later
rapid success
41,000+ Customers
1,000,000 Subscribers
150 Million transactions per day
200+ people in R&D
it was getting more difficult to deliver
2000  2001  2002  2003  2004  2005  2006   Features Delivered per Team  Days between Major Releases
1 Number of Major Releases in 2006
Yep, that’s it. (just one release all year)
Why?
Lack of visibility at all stages in the release Late feedback on features at the end of our release cycle
Long and unpredictable release schedules
Gradual productivity decline as the team grew
What did we do about it?
Major enterprise-wide Agile Transformation to ADM in just 3 months another 12 months of continuous improvement +
I knew we needed radical change to get us back on track to regular releases and agile delivered. ” Parker Harris Founder a...
Transformation Results 2000  2001  2002  2003  2004  2005  2006   2007 Features Delivered per Team  Days between Major Rel...
Agile Transformation Timeline “ Agile Launch” Big Bang Rollout January October April October January July Rollout Adoption...
Customers
Our customers are happy…
ADM has delivered total visibility, total transparency and unbelievable productivity… a complete win! ” Steve Fisher  Sr. ...
On time delivery? Last waterfall release 146 148 150 144 152 154
No really.  Every agile release has been deployed on-time (down to the exact minute)
Since implementing our iterative development methodology which enables us to deliver more frequent releases, we have seen ...
94 % of customers that indicate they definitely or probably will recommend salesforce.com to others % * Source: Salesforce...
+ 61 improvement in “mean time to release” for major releases in 2007 %
<ul><li>+568% </li></ul>
+ 94 Increase in feature requests delivered - 2007 v. 2006 %
+ 38 Increase in feature requests delivered per developer - 2007 v. 2006 %
Our teams are happier…
Simple is better.  With our agile approach to product development we've put our amazing people in charge.  They work as a ...
92 of respondents believe ADM is an effective approach for their scrum teams %
91 of respondents believe the quality of our products have improved or stayed the same % * 59% say our quality has improved
86 of respondents are having the “best time” or a “good time” at Salesforce % * Improved from 40% 15 months ago
92 of respondents would recommend ADM to their colleagues inside or outside Salesforce %
 
How’d we do it?
Launched organizational change program
Created a dedicated, cross-functional rollout team
Everyone jumped in together
Positioned as a return to our core values
Listen to your customers Iterate KISS
Distributed Ken Schwaber’s Agile book Developed 2-hour Agile overview
Sent 30 ScrumMasters to ScrumMaster Certification Sent 35 Product Managers to Product Owner Certification
Created weekly ScrumMaster and Product Owner forums
Created internal, wiki-based website as a reference for team members
Just get started. (the rest will come later)
Change isn’t easy. (get ready to be hated)
“ In many ways, scrum seems like an inflexible, bureaucratic process akin to something at the Department of Motor Vehicles...
They don’t like us. (and may never like us again)
“ Stop trying to implement scrum, and look at how many releases we can really do in a year.” “ The lingo is ridiculous” Te...
But, they got over it.
And. Finally. The rollout is over! (but we’re not done)
Now for the later stuff.
Continuous Improvement “ Agile Launch” Big Bang Rollout January October April October January July Rollout Adoption Excell...
Continuous Improvement “ Agile Launch” Big Bang Rollout January October April October January July Rollout Adoption Excell...
Don’t be like us. (or what would we’d do differently)
Involve more individual contributors early
Train Product Owners earlier and with more intensity
Get outside coaching earlier
Give key executives concrete deliverables around the rollout
Be more clear about what the agile ‘rules’ are
Keys to success?
Ensure executive commitment to the change
Focus on principles over mechanics
Focus on getting several teams to excellence
Focus on automation
16332 5752 2656 26212
 
Provide radical transparency
 
When the heat is on stick to your guns
We failed. (all along the way)
Experiment, be patient and expect to make mistakes
Don’t be afraid to change the entire company all at one time
 
Upcoming SlideShare
Loading in...5
×

The Year of Living Dangerously: Extraordinary Results for an Enterprise Agile Revolution

11,752

Published on

Keynote address at the Scrum Gathering 2008 in Chicago. Steve Greene and Chris Fry expand the salesforce.com agile transformation story with a year of continuous improvement and metrics / measurements of extraordinary success.

Published in: Technology
2 Comments
11 Likes
Statistics
Notes
No Downloads
Views
Total Views
11,752
On Slideshare
0
From Embeds
0
Number of Embeds
33
Actions
Shares
0
Downloads
4
Comments
2
Likes
11
Embeds 0
No embeds

No notes for slide
  • Transcript of "The Year of Living Dangerously: Extraordinary Results for an Enterprise Agile Revolution"

    1. 1. YEAR O F L I V I N G DANGEROUSLY Steve Greene | Chris Fry Scrum Gathering Conference, Chicago April 2008 How Salesforce.com delivered Extraordinary Results through a “Big Bang” Enterprise Agile Revolution
    2. 4. History
    3. 5. 8 Age of Salesforce in years
    4. 6. from the beginning
    5. 7. 3 Number of people in R&D
    6. 8. fast innovative smart
    7. 9. 4 Number of Major Releases per year
    8. 10. 7 years later
    9. 11. rapid success
    10. 12. 41,000+ Customers
    11. 13. 1,000,000 Subscribers
    12. 14. 150 Million transactions per day
    13. 15. 200+ people in R&D
    14. 16. it was getting more difficult to deliver
    15. 17. 2000 2001 2002 2003 2004 2005 2006 Features Delivered per Team Days between Major Releases
    16. 18. 1 Number of Major Releases in 2006
    17. 19. Yep, that’s it. (just one release all year)
    18. 20. Why?
    19. 21. Lack of visibility at all stages in the release Late feedback on features at the end of our release cycle
    20. 22. Long and unpredictable release schedules
    21. 23. Gradual productivity decline as the team grew
    22. 24. What did we do about it?
    23. 25. Major enterprise-wide Agile Transformation to ADM in just 3 months another 12 months of continuous improvement +
    24. 26. I 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 “
    25. 27. Transformation Results 2000 2001 2002 2003 2004 2005 2006 2007 Features Delivered per Team Days between Major Releases
    26. 28. Agile Transformation Timeline “ Agile Launch” Big Bang Rollout January October April October January July Rollout Adoption Excellence Expansion April 144 146 148 150 152 154
    27. 29. Customers
    28. 30. Our customers are happy…
    29. 31. ADM has delivered total visibility, total transparency and unbelievable productivity… a complete win! ” Steve Fisher Sr. Vice President, Platform Division Salesforce.com “
    30. 32. On time delivery? Last waterfall release 146 148 150 144 152 154
    31. 33. No really. Every agile release has been deployed on-time (down to the exact minute)
    32. 34. Since implementing our iterative development methodology which enables us to deliver more frequent releases, we have seen statistically significant improvements in our satisfactions scores across our service attributes from our features to our platform.   ” Wendy Close Salesforce Customer Satisfaction Survey Sr. Manager Product Marketing Salesforce.com “ (Source: Salesforce.com Relationship survey, conducted by independent third party CustomerSat Inc., July 07 and Feb. 08. Sample size equals 4000+ randomly selected worldwide respondents from all size companies and industry sectors.)
    33. 35. 94 % of customers that indicate they definitely or probably will recommend salesforce.com to others % * Source: Salesforce.com Relationship survey
    34. 36. + 61 improvement in “mean time to release” for major releases in 2007 %
    35. 37. <ul><li>+568% </li></ul>
    36. 38. + 94 Increase in feature requests delivered - 2007 v. 2006 %
    37. 39. + 38 Increase in feature requests delivered per developer - 2007 v. 2006 %
    38. 40. Our teams are happier…
    39. 41. Simple 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 “
    40. 42. 92 of respondents believe ADM is an effective approach for their scrum teams %
    41. 43. 91 of respondents believe the quality of our products have improved or stayed the same % * 59% say our quality has improved
    42. 44. 86 of respondents are having the “best time” or a “good time” at Salesforce % * Improved from 40% 15 months ago
    43. 45. 92 of respondents would recommend ADM to their colleagues inside or outside Salesforce %
    44. 47. How’d we do it?
    45. 48. Launched organizational change program
    46. 49. Created a dedicated, cross-functional rollout team
    47. 50. Everyone jumped in together
    48. 51. Positioned as a return to our core values
    49. 52. Listen to your customers Iterate KISS
    50. 53. Distributed Ken Schwaber’s Agile book Developed 2-hour Agile overview
    51. 54. Sent 30 ScrumMasters to ScrumMaster Certification Sent 35 Product Managers to Product Owner Certification
    52. 55. Created weekly ScrumMaster and Product Owner forums
    53. 56. Created internal, wiki-based website as a reference for team members
    54. 57. Just get started. (the rest will come later)
    55. 58. Change isn’t easy. (get ready to be hated)
    56. 59. “ 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.” “ Scrum 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 scrum…than we spend time talking and working on salesforce.com.”
    57. 60. They don’t like us. (and may never like us again)
    58. 61. “ Stop trying to implement scrum, and look at how many releases we can really do in a year.” “ The lingo is ridiculous” Team is effective but productivity is lower “ 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.” “ 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!” 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...
    59. 62. But, they got over it.
    60. 63. And. Finally. The rollout is over! (but we’re not done)
    61. 64. Now for the later stuff.
    62. 65. Continuous Improvement “ Agile Launch” Big Bang Rollout January October April October January July Rollout Adoption Excellence Expansion April 144 146 148 150 152 154
    63. 66. Continuous Improvement “ Agile Launch” Big Bang Rollout January October April October January July Rollout Adoption Excellence Expansion April Scrumforce Office Hours Release Management Sustainable Velocity Virtual Architecture System Testing PTOn Open Space SoS Cross Team Impact Dependencies Release Planning
    64. 67. Don’t be like us. (or what would we’d do differently)
    65. 68. Involve more individual contributors early
    66. 69. Train Product Owners earlier and with more intensity
    67. 70. Get outside coaching earlier
    68. 71. Give key executives concrete deliverables around the rollout
    69. 72. Be more clear about what the agile ‘rules’ are
    70. 73. Keys to success?
    71. 74. Ensure executive commitment to the change
    72. 75. Focus on principles over mechanics
    73. 76. Focus on getting several teams to excellence
    74. 77. Focus on automation
    75. 78. 16332 5752 2656 26212
    76. 80. Provide radical transparency
    77. 82. When the heat is on stick to your guns
    78. 83. We failed. (all along the way)
    79. 84. Experiment, be patient and expect to make mistakes
    80. 85. Don’t be afraid to change the entire company all at one time

    ×