Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile 2010 conference - a holistic approach to scaling agile at salesforce

10,732 views

Published on

Salesforce.com - presentation at the Agile 2010 conference on scaling agility

Published in: Technology
  • Be the first to comment

Agile 2010 conference - a holistic approach to scaling agile at salesforce

  1. A holistic approach to scaling agile at Salesforce.com Agile 2010 Conference Orlando, Florida Steve Greene Nicola Dourambeis
  2. Who are we?
  3. Steve Greene VP, Program Management Nicola Dourambeis Director, Agile Delivery
  4. Problems?
  5. <ul><li>Unpredictable completion of anything </li></ul>
  6. Lack of Visibility
  7.  
  8. Resource Bottlenecks
  9. Infrequent Customer Feedback
  10. 2000 2001 2002 2003 2004 2005 2006 Features Delivered per Team Days between Major Releases
  11. What did we do about it?
  12.  
  13. The Beginning (2006) 2006 25+ agile teams in R&D
  14. 2010 100+ agile teams R&D, IT, & Technical Operations
  15. What is ADM? ADM (Adaptive Delivery Methodology) Salesforce.com flavor of agile Scrum project management framework XP practices Based on Lean principles
  16. Next steps to scale
  17. We scale both deep and wide
  18. After success with R&D, ADM was rolled out to IT
  19. 3 month rollout: Don’t overthink it, start, inspect and adapt
  20. Next Up: Technical Operations moved to ADM
  21. Embrace Difference and be prepared to stretch Agility
  22. Wide scale has challenges, scaling deep has more
  23. Challenges
  24. Aggressive Hiring Let’s change the world!
  25. Scale with values
  26. One Codeline
  27. Product Dependencies
  28. Leadership
  29. Solutions
  30. Scale Problem #1 Dependency Management is Hard Dependency Management is Hard
  31. Just enough structure but no more
  32. ADM Release Cycle Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Coordinate release planning with generic framework Planning cycle for next release Planning cycle for next release Planning cycle for next release Release Release Release Release
  33. Tools Help
  34. But really, it’s the people that make things happen
  35. And we make a big investment in collaboration
  36. Maintain Technical Health Debt is the Enemy
  37. Create a Single Definition of Done
  38. Stop the codeline when test failures are too high
  39. Strong Attention to metrics Status Metric Now (7/30) Release Criteria Potentially Releasable Metrics Feature Freeze Threshold   Basic Ftest 100% 100.0% Utest 100% 100.0% Full Ftest 100% >99.8% Extended Ftest 96.86% >99.75% Basic Selenium 99.76% 100.0% Selenium 99.6% >99.5% Unresolved Integrations 0 0
  40. Maintain team focus
  41. Hire for Values and Culture Fit
  42. Let’s go deeper
  43. Case Study
  44. Agile Program Management
  45. Urgent change based on new strategic direction
  46. The ugly baby
  47. High Level Goals Design & Priorities
  48. Global Prioritized “Feature” backlog
  49. Move teams not people
  50. 26 to 33 to 27 Teams Team 13 Team 11 Team 9 Team 10 Team 14 Team 8 Team 7 Team 12 Team 19 Team 18 Team 16 Team 15 Team 17 Team 25 Team 21 Team 20 Team 27 Team 22 Team 23 Team 24 Team 26 Team 2 Team 3 Team 4 Team 5 Team 1 Team 6
  51. Launch & Collaborate
  52. Align to Workgroups Team 13 Team 11 Team 9 Team 10 Team 14 Team 8 Team 7 Team 12 Team 19 Team 18 Team 16 Team 15 Team 17 Workgroup 4 Workgroup 2 Team 25 Team 21 Team 20 Team 27 Team 22 Team 23 Team 24 Team 26 Team 2 Team 3 Team 4 Team 5 Team 1 Team 6 Workgroup 1 Workgroup 3
  53. Collaboration is key (up, down, across)
  54. Meet to realign every day
  55. Full Coordinated Transparency
  56. Visibility to Program feature priorities
  57. Visibility to Workgroup feature priorities Features Priority Status <ul><ul><li>Console </li></ul></ul>1 <ul><ul><li>Client-Side Data Binding </li></ul></ul>2 <ul><ul><li>Sharing model </li></ul></ul>3 <ul><ul><li>Home page redesign </li></ul></ul>4 <ul><ul><li>Workbench </li></ul></ul>5 <ul><ul><li>Prioritizer UI </li></ul></ul>6 <ul><ul><li>Investigations support </li></ul></ul>7 <ul><ul><li>VF redesign </li></ul></ul>8 <ul><ul><li>RCA support </li></ul></ul>9 <ul><ul><li>Universal workflow </li></ul></ul>10 <ul><ul><li>api </li></ul></ul>11
  58. Program Dependencies Delivering Team & Feature Consuming Team & Feature May June July Team 8 Team 7 Team 22 High Med Low Risk Done – Delivered Low – On track Medium – Possible concerns/may miss deadline High – Not scheduled, cannot deliver, or deadline missed Team 12 Team 18 Team 10 Team 11 Monitor complexity & maintain visibility Something more Something I want Done Feature at risk Feature Something I need Cool Feature Something else I need Another Cool Feature
  59. Lessons Learned
  60. Be Bold and don’t go Halfway
  61. Don’t be satisfied, always look for things to improve
  62. Stick to your principles Trust the teams over creating mandatory process & structure
  63. Agile does work at scale Lightweight structure & more autonomy
  64. Questions? http://www.slideshare.net/sgreene

×