Adopting Agile

3,059
-1

Published on

Published in: Technology, Business
1 Comment
15 Likes
Statistics
Notes
  • Very interesting ppt. The research indicated PPT only contains 30% of information; therefore the 70% valuable information comes from the presenter himself/herself. soEZLecturing.com provides you a chance to record your voice with your PowerPoint presentation and upload to the website. It can share with more readers and also promote your presentation more effectively on soEZLecturing.com.
    www.soezlecturing.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
3,059
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
44
Comments
1
Likes
15
Embeds 0
No embeds

No notes for slide

Adopting Agile

  1. Adopting Agile (beta release)
  2. Mike Cottmeyer mike.cottmeyer@versionone.com www.linkedin.com/in/cottmeyer www.versionone.com blog.versionone.net www.leadingagile.com
  3. Ideal Agile Team
  4. Ideal Agile Team
  5. Developers Ideal Agile Team
  6. Testers Developers Ideal Agile Team
  7. Analyst Testers Developers Ideal Agile Team
  8. Analyst PM Testers Developers Ideal Agile Team
  9. Analyst CSM Testers Developers Ideal Agile Team
  10. Product Owner Analyst CSM Testers Developers Ideal Agile Team
  11. A Traditional Team
  12. Dev. A Traditional Team
  13. Dev. QA A Traditional Team
  14. Dev. QA BA A Traditional Team
  15. Dev. QA BA PM A Traditional Team
  16. Dev. QA BA PM PO A Traditional Team
  17. Dev. QA BA PM PO The Project Team A Traditional Team
  18. Project One Analysis Design Build Test Deploy Project Two Analysis Design Build Test Deploy Project Three Analysis Design Build Test Deploy
  19. Project One Analysis Design Build Test Deploy Project Two Analysis Design Build Test Deploy Project Three Analysis Design Build Test Deploy
  20. Proejct One Analysis Design Build Test Deploy Project Two Analysis Design Build Test Deploy Project Three Analysis Design Build Test Deploy
  21. Project One Analysis Design Build Test Deploy Project Two Analysis Design Build Test Deploy Project Three Analysis Design Build Test Deploy
  22. Project One Analysis Design Build Test Deploy Project Two Analysis Design Build Test Deploy Proejct Three Analysis Design Build Test Deploy
  23. Project One Analysis Design Build Test Deploy Project Two Analysis Design Build Test Deploy Project Three Analysis Design Build Test Deploy
  24. How do I Untangle…
  25. How do I re-architect the organization…
  26. Where do I start?
  27. The Agile Team
  28. The Agile Team
  29. Team The Agile Team
  30. Team Features The Agile Team
  31. Team Components Features The Agile Team
  32. Team Components Services Features The Agile Team
  33. Team Capabilities The Agile Team
  34. Team Backlog The Agile Team
  35. Team Velocity Backlog The Agile Team
  36. Team Predictable Velocity Backlog The Agile Team
  37. Team Predictable Trust Velocity Backlog The Agile Team
  38. • Build organizations around teams
  39. • Build organizations around teams • Build small features
  40. • Build organizations around teams • Build small features • Garbage in… garbage out
  41. • Build organizations around teams • Build small features • Garbage in… garbage out • Measure progress and get better
  42. Multiple Teams
  43. Capability 1 Multiple Teams
  44. Capability Capability 1 2 Multiple Teams
  45. Capability Capability Capability 1 2 3 Multiple Teams
  46. Scrum of Scrums Capability Capability Capability 1 2 3 Multiple Teams
  47. Product Owner Team Capability Capability Capability 1 2 3 Multiple Teams
  48. Product Owner Team with Architects Capability Capability Capability 1 2 3 Multiple Teams
  49. Integration Team Capability Capability Capability 1 2 3 Multiple Teams
  50. Context Capability Capability Capability 1 2 3 Multiple Teams
  51. Context Coordination Capability Capability Capability 1 2 3 Multiple Teams
  52. • Product Owner too big
  53. • Product Owner too big • Dependencies increase costs
  54. • Product Owner too big • Dependencies increase costs • Feature teams break down
  55. • Product Owner too big • Dependencies increase costs • Feature teams break down • Velocity across teams
  56. Multiple Projects
  57. Project A Capability Capability Capability 1 2 3 Multiple Projects
  58. Project Project A B Capability Capability Capability 1 2 3 Multiple Projects
  59. C1 C2 C3 Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Multiple Projects
  60. C1 C2 C3 Project A Project A Project A Project A Project B Project A Project A Project A Project B Project A Project B Project B Project A Project A Project B Project A Project B Project A Multiple Projects
  61. C1 C2 C3 Project A Project A Project A Project A Project B Project A Project A Project A Project B Project A Project B Project B Project A Project A Project B Project A Project B Project A Project B Project B Project B Project B Project B Project B Project B Project B Multiple Projects
  62. C1 C2 C3 Project A Project A Project A Project A Project B Project A Project A Project A Project B Project A Project B Project B Project A Project A Project B Project A Project B Project A Project B Project C Project B Project B Project B Project C Project C Project B Project C Project B Project B Project B Multiple Projects
  63. Project A Project A Project A 3 months Project B Project B Project B Project C Project C Project C Multiple Projects
  64. Project A Project A Project A 3 months Project B Project B Project B 6 months Project C Project C Project C Multiple Projects
  65. Project A Project A Project A 3 months Project B Project B Project B 6 months Project C Project C Project C 9 months Multiple Projects
  66. Project A Project B Project C Project A Project B Project C Project A 7 months Project B Project C Multiple Projects
  67. Project A Project B Project C Project A Project B Project C Project A 7 months Project B 8 months Project C Multiple Projects
  68. Project A Project B Project C Project A Project B Project C Project A 7 months Project B 8 months Project C 9 months Multiple Projects
  69. Project A Project B Project C Project A Project B Project C Project A 7 months Project B 8 months Project C 9 months Multiple Projects
  70. C1 C2 C3 Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Multiple Projects
  71. C1 C2 C3 Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Multiple Projects
  72. C1 C2 C3 Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Multiple Projects
  73. C1 C2 C3 Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Project B Project B Project B Project B Project B Project B Project B Multiple Projects
  74. C1 C2 C3 Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Project B Project B Project B Project B Project B Project B Project B Project C Project C Project C Project C Project C Project C Project C Project C Project C Multiple Projects
  75. C1 C2 C3 Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Project B Project B Project B Project B Project B Project B Project B Project C Project C Project C Project C Project C Project C Project C Project C Project C Multiple Projects
  76. C1 C2 C3 Project A Project A Project A Project A Project A Project A Project A Project A Project A Project A Refactoring Training Project B Project B Project B Project B Project B Project B Refactoring Training Project B Project C Project C Project C Project C Project C Project C Project C Project C Project C Multiple Projects
  77. • Build organizations around capabilities
  78. • Build organizations around capabilities • Optimize throughput across teams
  79. • Build organizations around capabilities • Optimize throughput across teams • Prioritize for finish…
  80. • Build organizations around capabilities • Optimize throughput across teams • Prioritize for finish… • Smaller projects are better
  81. Agile Enterprise
  82. PMO Agile Enterprise
  83. PMO PO Team Agile Enterprise
  84. PMO PO Team Team Agile Enterprise
  85. PMO PO Team Team Enterprise Architecture & Epics Agile Enterprise
  86. PMO PO Team Team Enterprise Solutions Architecture Architecture & & Epics Features Agile Enterprise
  87. PMO PO Team Team Enterprise Solutions Detailed Architecture Architecture Design & & & Epics Features Stories Agile Enterprise
  88. Guidance PMO PO Team Team Agile Enterprise
  89. Feedback PMO PO Team Team Agile Enterprise
  90. Not the entire Product business Delivery Agile Enterprise
  91. Product Strategy Delivery Agile Enterprise
  92. Product Strategy Support Delivery Agile Enterprise
  93. • Establish direction… give feedback
  94. • Establish direction… give feedback • Business is made up of capabilities
  95. • Establish direction… give feedback • Business is made up of capabilities • The goal is greater profitability
  96. • Establish direction… give feedback • Business is made up of capabilities • The goal is greater profitability • Focus improvements on constraints
  97. Capability Modeling
  98. Teams Capability Modeling
  99. Teams Identify Capability Modeling
  100. Teams Define Identify Capability Modeling
  101. Teams Define Assign Identify Capability Modeling
  102. Teams Optimize Define Assign Identify Capability Modeling
  103. Teams Optimize Define Assign Identify Capability Modeling
  104. Thoughts?
  105. Adopting Agile (beta release)
  106. Mike Cottmeyer mike.cottmeyer@versionone.com www.linkedin.com/in/cottmeyer www.versionone.com blog.versionone.net www.leadingagile.com

×