Scrum Gathering 2008 Stockholm - Salesforce.com
Download as PPT, PDF25 likes37,906 views
Salesforce.com underwent a major enterprise-wide transformation to Agile Development Methodology (ADM) over 3 months in order to address issues like a lack of visibility, resource bottlenecks, and unpredictable release dates that were causing customer unhappiness and a decline in productivity. This "Big Bang" approach resulted in significant improvements like a 61% reduction in time between major releases, a 94% increase in delivered feature requests, and a 38% increase in features delivered per developer. While the transition was challenging and faced some initial resistance, continuous improvements and refinements over time helped ensure the success and sustainability of the new Agile approach.
Ad
More Related Content
What's hot (20)
Similar to Scrum Gathering 2008 Stockholm - Salesforce.com (20)
Ad
More from Steve Greene (20)
Ad
Recently uploaded (20)
Scrum Gathering 2008 Stockholm - Salesforce.com
- 1. YEAR O F L I V I N G DANGEROUSLY Steve Greene | Chris Fry Scrum Gathering, Stockholm October 2008 How Salesforce.com delivered Extraordinary Results through a โBig Bangโ Enterprise Agile Revolution
- 2. ย
- 3. ย
- 4. ย
- 5. ย
- 8. 3 Number of people in R&D
- 10. 4 Number of Major Releases per year
- 11. 7 years later
- 12. rapid success
- 15. 150 Million transactions per day
- 16. 500+ people in R&D
- 17. it was getting more difficult to deliver
- 18. 2000 2001 2002 2003 2004 2005 2006 Features Delivered per Team Days between Major Releases
- 19. 1 Number of Major Releases in 2006
- 20. Why?
- 24. Lack of responsiveness, lack of team alignment on priorities
- 26. Gradual productivity decline as the team grew
- 27. What did we do about it?
- 28. Major enterprise-wide Agile Transformation to ADM in just 3 months another 18 months of continuous improvement +
- 29. 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 โ
- 30. Transformation Results 2000 2001 2002 2003 2004 2005 2006 2007 Features Delivered per Team Days between Major Releases
- 31. 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
- 32. Customers
- 33. Our customers are happyโฆ
- 34. Agile has delivered total visibility, total transparency and unbelievable productivityโฆ a complete win! โ Steve Fisher Sr. Vice President, Platform Product Management Salesforce.com โ
- 35. On time delivery? Last waterfall release 146 148 150 144 152 154 156
- 36. No really. Every agile release has been deployed on-time (down to the exact minute)
- 37. 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.)
- 38. 94 % of customers that indicate they definitely or probably will recommend salesforce.com to others % * Source: Salesforce.com Relationship survey
- 39. + 61 improvement in โmean time to releaseโ for major releases in 2007 %
- 40. +568%
- 41. + 94 Increase in feature requests delivered - 2007 v. 2006 %
- 42. + 38 Increase in feature requests delivered per developer - 2007 v. 2006 %
- 43. 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 โ
- 44. Our teams are happierโฆ
- 45. 92 of respondents believe ADM is an effective approach for their scrum teams %
- 46. 88 of respondents believe the quality of our products have improved or stayed the same % * 51% say our quality has improved
- 47. 89 of respondents are having the โbest timeโ or a โgood timeโ at Salesforce % * 49% improvement from pre-ADM
- 48. 94 of respondents would recommend ADM to their colleagues inside or outside Salesforce %
- 49. ย
- 50. What is it and how did we do it?
- 51. ย
- 52. What 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.
- 53. What is ADM? Re-factoring Self-organizing Predictable releases Transparent Ftest - Selenium Continuous integration Debt free Just-in-time Iterative Always Potentially Releasable Time-boxed User stories Agile Lean Early feedback Code Reviews Collective Code Ownership Self-correcting
- 54. Launched organizational change program
- 55. Created a dedicated, cross-functional rollout team
- 56. Everyone jumped in together
- 57. Positioned as a return to our core values
- 58. Listen to your customers Iterate KISS
- 59. Distributed Ken Schwaberโs Agile book Developed 2-hour Agile overview
- 60. Sent 30 ScrumMasters to ScrumMaster Certification Sent 35 Product Managers to Product Owner Certification
- 61. Created weekly ScrumMaster and Product Owner forums
- 62. Created internal, wiki-based website as a reference for team members
- 63. Just get started. (the rest will come later)
- 64. Change isnโt easy. (get ready to be hated)
- 65. โ 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.โ
- 66. They donโt like us. (and may never like us again)
- 67. โ 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...
- 68. But, they got over it.
- 69. And. Finally. The rollout is over! (but weโre not done)
- 70. Now for the later stuff.
- 71. Continuous Improvement โ Agile Launchโ Big Bang Rollout January October April October January July Rollout Adoption Excellence Expansion April 144 146 148 150 152 154
- 72. 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
- 73. Continuous Improvement โ Excellence & Expansion October April January July 2008 April October July 2009 IT Rollout Customer & Partner Agile consulting Technical Operations Rollout
- 74. Donโt be like us. (or what would weโd do differently)
- 75. Involve more individual contributors early
- 76. Train Product Owners earlier and with more intensity
- 77. Get outside coaching earlier
- 78. Give key executives concrete deliverables around the rollout
- 79. Be more clear about what the agile โrulesโ are
- 80. Keys to success?
- 81. Ensure executive commitment to the change
- 82. Focus on principles over mechanics
- 83. Focus on getting several teams to excellence
- 85. 16332 5752 2656 27967 Automation
- 86. ย
- 88. ย
- 89. When the heat is on stick to your guns
- 90. We failed. (all along the way)
- 91. Experiment, be patient and expect to make mistakes
- 92. 100% Commitment to agile can radically transform your company
- 93. ย