Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

A holistic approach to scaling Agile

520 Aufrufe

Veröffentlicht am

How we’ve applied agile organizationally at scale and the
challenges of scale

Veröffentlicht in: Technologie
  • Als Erste(r) kommentieren

A holistic approach to scaling Agile

  1. 1. A holistic approach to scaling Agile at CSC Ali Akbar Technical Director
  2. 2. Who are we?
  3. 3. Founded 1959 IT Services & Professional Services Stock Symbol: CSC FY 14 Revenue: 13 B
  4. 4. Problems?
  5. 5. Unpredictable completion of anything
  6. 6. Lack of Visibility
  7. 7. Resource Bottlenecks
  8. 8. Infrequent Customer Feedback
  9. 9. 2009 2010 2011 2012 Apr 2013 Jul 2013 2014 Features Delivered per Team Days between Releases
  10. 10. What did we do about it?
  11. 11. Agile Delivery Methodology (AgDM) Adaptive Delivery Methodology (AdDM)
  12. 12. The Beginning (2006) 2012 1 agile team in Project
  13. 13. 2013 6 agile teams Technical Operations, Optimization, Project, Analytics, Sales Ops & Digital Marketing
  14. 14. What is AgDM & AdDM? AdDM (Adaptive Delivery Methodology) CSC flavor of agile Scrum project management framework XP practices Based on Lean principles AgDM (Agile Delivery Methodology) best practices from cloud based deployment Continuous Integration (CI) Continuous Deployment (CD) DevOps Agile Delivery Acceleration Platform (ADAP)
  15. 15. Next steps to scale
  16. 16. We scale both deep and wide
  17. 17. After success with Project, ADM was rolled out to Operations & Optimization
  18. 18. 3 month rollout: Don’t overthink it, start, inspect and adapt
  19. 19. Next Up: Analytics, Sales Ops & Digital Marketing moved to ADM
  20. 20. Embrace Difference and be prepared to stretch Agility
  21. 21. Wide scale has challenges, scaling deep has more
  22. 22. Challenges
  23. 23. Managing distributed and matrix managed teams
  24. 24. Scale with values
  25. 25. One Codeline
  26. 26. Product and Project Dependencies
  27. 27. Leadership
  28. 28. Solutions
  29. 29. Scale Problem #1 Dependency Management is Hard Dependency Management is Hard
  30. 30. Just enough structure but no more
  31. 31. ADM Release Cycle (4-weeks) Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Release Coordinate release planning with generic framework Planning cycle for next release
  32. 32. Tools Help
  33. 33. But really, it’s the people that make things happen
  34. 34. And we make a big investment in collaboration
  35. 35. Maintain Technical Health Debt is the Enemy
  36. 36. Create a Single Definition of Done
  37. 37. Stop the codeline when test failures are too high
  38. 38. Status   Metric   Now   (7/30)   Release  Criteria   Poten&ally  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  IntegraCons   0   0   Strong Attention to metrics
  39. 39. Maintain team focus
  40. 40. Hire for Values and Culture Fit
  41. 41. Let’s go deeper
  42. 42. Case Study
  43. 43. Agile Program Management
  44. 44. Urgent change based on new strategic direction
  45. 45. The ugly baby
  46. 46. High Level Goals Design & Priorities
  47. 47. Global Prioritized “Feature” backlog
  48. 48. Move teams not people
  49. 49. 6 Teams Team 1 Team 2 Team 3 Team 5Team 4 Team 6
  50. 50. Launch & Collaborate
  51. 51. Align to Workgroups Workgroup 2 Team 4 Team 5 Team 6 Workgroup 1 Team 1 Team 2 Team 3
  52. 52. Collaboration is key (up, down, across)
  53. 53. Meet to realign every day
  54. 54. Full Coordinated Transparency
  55. 55. Visibility to Program feature priorities
  56. 56. Visibility to Workgroup feature priorities Features Priority Status Communities 1 SSO 2 Sharing model 3 Home page redesign 4 Workbench 5 Opportunity UI 6 Encryption 7 VF redesign 8 ICM support 9 OSS workflow 10 API 11
  57. 57. Program Dependencies Delivering Team & Feature Consuming Team & Feature  May   June July Team 2 Team 1 Something more Something I want Team 5 HighMedLow Risk Done Done – Delivered Low – On track Medium – Possible concerns/may miss deadline High – Not scheduled, cannot deliver, or deadline missed Feature at risk Feature Team 4 Team 4 Something I need Cool Feature Team 3 Team 5Something else I need Another Cool Feature Monitor complexity & maintain visibility
  58. 58. Lessons Learned
  59. 59. Be Bold and don’t go Halfway
  60. 60. Don’t be satisfied, always look for things to improve
  61. 61. Stick to your principles Trust the teams over creating mandatory process & structure
  62. 62. Agile does work at scale Lightweight structure & more autonomy
  63. 63. Questions?

×