• Save
The Year of Living Dangerously: Extraordinary Results for an Enterprise Agile Revolution
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

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

on

  • 3,395 views

Keynote presentation at the Scrum Gathering 2008 Conference in Chicago. The talk describes the "Big Bang" agile transformation at Salesforce.com, the continuous improvement in the methodology over ...

Keynote presentation at the Scrum Gathering 2008 Conference in Chicago. The talk describes the "Big Bang" agile transformation at Salesforce.com, the continuous improvement in the methodology over the next year and metrics / measurements of our extraordinary results and ROI.

Statistics

Views

Total Views
3,395
Views on SlideShare
1,980
Embed Views
1,415

Actions

Likes
2
Downloads
0
Comments
0

9 Embeds 1,415

http://www.redqueen.de 1103
http://borisgloger.com 238
http://redqueen.de 44
http://scrum4you.wordpress.com 20
http://redqueen.de.www238.your-server.de 6
http://www.google.de 1
http://webcache.googleusercontent.com 1
http://www.slashdocs.com 1
https://www.google.at 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

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

  • 1. YEAR O F L I V I N G DANGEROUSLY Steve Greene | Chris Fry How Salesforce.com delivered Extraordinary Results through a “Big Bang” Enterprise Agile Revolution Scrum Gathering Conference, Chicago April 2008
  • 2.  
  • 3.  
  • 4. History
  • 5. 8 Age of Salesforce in years
  • 6. from the beginning
  • 7. 3 Number of people in R&D
  • 8. fast innovative smart
  • 9. 4 Number of Major Releases per year
  • 10. 7 years later
  • 11. rapid success
  • 12. 35,000+ Customers 41,000+
  • 13. 900,000 Subscribers 1,000,000
  • 14. 100 Million transactions per day 150 Million
  • 15. 200+ people in R&D 350+
  • 16. it was getting more difficult to deliver
  • 17. 2000 2001 2002 2003 2004 2005 2006 Features Delivered per Team Days between Major Releases
  • 18. 1 Number of Major Releases per year
  • 19. Why?
  • 20. Lack of visibility at all stages in the release Late feedback on features at the end of our release cycle
  • 21. Long and unpredictable release schedules
  • 22. Gradual productivity decline as the team grew
  • 23. What did we do about it?
  • 24. Major enterprise-wide Agile Transformation to ADM in just 3 months another 12 months of continuous improvement +
  • 25. What did we do about it?
  • 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 “
  • 27. Transformation Results 2000 2001 2002 2003 2004 2005 2006 2007 Features Delivered per Team Days between Major Releases
  • 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
  • 29. Customers
  • 30. Our customers are happy…
  • 31. ADM has delivered total visibility, total transparency and unbelievable productivity… a complete win! ” Steve Fisher Sr. Vice President, Platform Division Salesforce.com “
  • 32. On time delivery? Last waterfall release 146 148 150 144 152
  • 33. That’s right, every Agile release has been deployed on-time
  • 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.)
  • 35. 94 % of customers that indicate they definitely or probably will recommend salesforce.com to others % * Source: Salesforce.com Relationship survey
  • 36. + 61 improvement in “mean time to release” for major releases in 2007 %
  • 37.
    • +568%
  • 38. + 94 Increase in feature requests delivered - 2007 v. 2006 %
  • 39. + 38 Increase in feature requests delivered per developer - 2007 v. 2006 %
  • 40. Our teams are happier…
  • 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 “
  • 42. 92 of respondents believe ADM is an effective approach for their scrum teams %
  • 43. 91 of respondents believe the quality of our products have improved or stayed the same % * 59% say our quality has improved
  • 44. 86 of respondents are having the “best time” or a “good time” at Salesforce % * Improved from 40% 15 months ago
  • 45. 92 of respondents would recommend ADM to their colleagues inside or outside Salesforce %
  • 46.  
  • 47. How’d we do it?
  • 48. Launched organizational change program
  • 49. Created a dedicated, cross-functional rollout team
  • 50. Everyone jumped in together
  • 51. Positioned as a return to our core values
  • 52. Listen to your customers Iterate KISS
  • 53. Distributed Ken Schwaber’s Agile book Developed 2-hour Agile overview
  • 54. Sent 30 ScrumMasters to ScrumMaster Certification Sent 35 Product Managers to Product Owner Certification
  • 55. Created weekly ScrumMaster and Product Owner forums
  • 56. Created internal, wiki-based website as a reference for team members
  • 57. It wasn’t easy.
  • 58. “ 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.”
  • 59. “ 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...
  • 60. Continuous Improvement “ Agile Launch” Big Bang Rollout January October April October January July Rollout Adoption Excellence Expansion April 144 146 148 150 152 154
  • 61. 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
  • 62. What would we do differently?
  • 63. Involve more individual contributors early
  • 64. Train Product Owners earlier and with more intensity
  • 65. Get outside coaching earlier
  • 66. Give key executives concrete deliverables around the rollout
  • 67. Be more clear about what the agile ‘rules’ are
  • 68. Keys to success?
  • 69. Ensure executive commitment to the change
  • 70. Focus on principles over mechanics
  • 71. Focus on getting several teams to excellence
  • 72. Focus on automation
  • 73. 16332 5752 2656 26212
  • 74.  
  • 75. Provide radical transparency
  • 76.  
  • 77. When the heat is on stick to your guns
  • 78. Experiment, be patient and expect to make mistakes
  • 79. Don’t be afraid to change the entire company all at one time
  • 80.