Agile Past the Team<br />An Experience Report<br />Presented by: Mike Cottmeyer<br />
mike cottmeyervice-president, pillar technology semcottmeyer@pillartechnology.com+1.404.312.1471www.pillartechnology.comww...
Agenda<br />A little project background<br />
Agenda<br />A little project background<br />What was going well<br />
Agenda<br />A little project background<br />What wasn’t going well<br />
Agenda<br />A little project background<br />What wasn’t going well<br />The team’s initial response to problems<br />
Agenda<br />A little project background<br />What wasn’t going well<br />The team’s initial response to problems <br />Tea...
Agenda<br />A little project background<br />What wasn’t going well<br />The team’s initial response to problems <br />Org...
Agenda<br />A little project background<br />What wasn’t going well<br />The team’s initial response to problems <br />Org...
Ready?<br />
Background<br />Waterfall since the company had formed<br />
Background<br />Waterfall since the company had formed<br />Evaluated Scrum<br />
Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />
Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />Chose Scrum because it was quicke...
Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />Chose Scrum because it was they t...
Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />Chose Scrum because it was they t...
Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />Chose Scrum because it was they t...
Going Well?<br />
Going Well?<br />Moved away from functional silos<br />
Going Well?<br />Moved toward cross functional teams<br />
Going Well?<br />Moved toward cross functional teams<br />Moved away from component teams<br />
Going Well?<br />Moved toward cross functional teams<br />Moved toward feature based teams<br />
Going Well?<br />Moved toward cross functional teams<br />Moved toward feature based teams<br />Product Manager for each t...
Going Well?<br />Moved toward cross functional teams<br />Moved toward feature based teams<br />Product Owner for each tea...
Going Well?<br />Moved toward cross functional teams<br />Moved toward feature based teams<br />Product Owner for each tea...
Not Going Well?<br />
Not Going Well?<br />Critical people shared across teams<br />
Not Going Well?<br />Critical people shared across teams<br />Didn’t know what to build<br />
Not Going Well?<br />Critical people shared across teams<br />Didn’t know what to build<br />Teams had trouble delivering<...
Not Going Well?<br />Critical people shared across teams<br />Didn’t know what to build<br />Teams had trouble delivering ...
Not Going Well?<br />Critical people shared across teams<br />Didn’t know what to build<br />Teams had trouble delivering ...
Textbook Scrum<br />
Textbook ScrumNo working software<br />
My Role<br />
My Role<br />Purchased VersionOne<br />
My Role<br />Purchased VersionOne<br />Came in as a product trainer<br />
My Role<br />Purchased VersionOne<br />Came back as an agile coach<br />
My Role<br />Purchased VersionOne<br />Came back as an agile coach<br />The goal was to help the teams get better<br />
My Role<br />Purchased VersionOne<br />Came back as an agile coach<br />The goal was to help the teams get better<br />Lea...
Team Coaching<br />
Team Coaching<br />Big Rocks<br />
Team Coaching<br />Big Rocks<br />The Million Dollar Question<br />
Team Coaching<br />Big Rocks<br />The Million Dollar Question<br />Don’t game the numbers<br />
Team Coaching<br />Big Rocks<br />The Million Dollar Question<br />Don’t game the numbers<br />Retrospectives<br />
Org Coaching<br />
Org Coaching<br />Scrum-But<br />
Org Coaching<br />Scrum-But<br />Product and Architectural Vision<br />
Org Coaching<br />Scrum-But<br />Product and Architectural Vision<br />Product Owner Teams<br />
Org Coaching<br />Scrum-But<br />Product and Architectural Vision<br />Product Owner Teams<br />Well groomed backlog<br />
Million Dollar Question<br />
Plan<br />Execute<br />Close<br />
Plan<br />Close<br />Execute<br />
Plan<br />Execute<br />Close<br />Commit<br />
Deliver<br />Plan<br />Execute<br />Close<br />Commit<br />
Scrum-But<br />
Developers<br />
Testers<br />Developers<br />
Analyst<br />Testers<br />Developers<br />
Analyst<br />CSM<br />Testers<br />Developers<br />
Product Owner<br />Analyst<br />CSM<br />Testers<br />Developers<br />
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<...
Product Owner Teams<br />
Scrum of Scrums<br />Capability 2<br />Capability 1<br />Capability  3<br />
Product Owner Team<br />Capability 2<br />Capability 1<br />Capability  3<br />
Product Owner Team with<br />Architects<br />Capability 2<br />Capability 1<br />Capability  3<br />
Integration Team<br />Capability 2<br />Capability 1<br />Capability  3<br />
Context<br />Capability 2<br />Capability 1<br />Capability  3<br />
Context<br />Coordination<br />Capability 2<br />Capability 1<br />Capability  3<br />
Architecture and Design<br />
Guidance<br />Team<br />PO Team<br />PMO<br />Enterprise<br />Architecture<br />&<br />Epics <br />Solutions<br />Architec...
Feedback<br />Team<br />PO Team<br />PMO<br />Enterprise<br />Architecture<br />&<br />Epics <br />Solutions<br />Architec...
I1-N<br />I0<br />IH<br />
Construction<br />Elab.<br />Inc.<br />Trans.<br />I1-N<br />I0<br />IH<br />
Initiate<br />Plan<br />Execute<br />Monitor & Control<br />Close<br />Construction<br />Elab.<br />Inc.<br />Trans.<br />...
Grooming the Backlog<br />
Epic<br />Epic<br />Epic<br />Epic<br />Enterprise<br />Architecture<br />&<br />Epics <br />
Feature<br />Epic<br />Feature<br />Feature<br />Feature<br />Epic<br />Feature<br />Epic<br />Feature<br />Epic<br />Ente...
Feature<br />Epic<br />User Story<br />User Story<br />Feature<br />User Story<br />User Story<br />Feature<br />User Stor...
Conclusion<br />
Conclusion<br />Forming and developing teams is critical<br />
Conclusion<br />Forming and developing teams is critical<br />The organization has tremendous impact on team effectiveness...
Conclusion<br />Forming and developing teams is critical<br />The organization has tremendous impact on team effectiveness...
Conclusion<br />Forming and developing teams is critical<br />The organization has tremendous impact on team effectiveness...
Thoughts?<br />
mike cottmeyervice-president, pillar technology semcottmeyer@pillartechnology.com+1.404.312.1471www.pillartechnology.comww...
www.slideshare.net/mcottmeyer<br />Agile Past the Team<br />An Experience Report<br />Presented by: Mike Cottmeyer<br />
Upcoming SlideShare
Loading in …5
×

Agile Past The Team - Pillar Template

1,342 views

Published on

This deck describes the key learnings from a coaching engagement I did in early 2009 for VersionOne. . Might be called... how to do Scrum and deliver nothing ;-)

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,342
On SlideShare
0
From Embeds
0
Number of Embeds
35
Actions
Shares
0
Downloads
40
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • Where does a company like this start? How do they go from this siloed and complex project portfolio… one that is trying to manage a complex set of dependencies… to one made up of loosely coupled and independent small agile teams. I hope it goes without saying that this is not a trivial problem. The problem is very similar to the challenge a software architect faces when trying to move from a tightly coupled systems architecture with low cohesion to a loosely coupled modular software architecture with well defined responsibilities and interfaces. The general approach is to look for services that you can pull out… one at a time… and build a parallel system based on sound architectural principles. You have to define what services you are going to pull out… what they are going to do… and how they are going to work with the legacy system to support the operations of the business. You build this new team based system along side the old way of doing things until the entire organization has moved to a team based model.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • Where does a company like this start? How do they go from this siloed and complex project portfolio… one that is trying to manage a complex set of dependencies… to one made up of loosely coupled and independent small agile teams. I hope it goes without saying that this is not a trivial problem. The problem is very similar to the challenge a software architect faces when trying to move from a tightly coupled systems architecture with low cohesion to a loosely coupled modular software architecture with well defined responsibilities and interfaces. The general approach is to look for services that you can pull out… one at a time… and build a parallel system based on sound architectural principles. You have to define what services you are going to pull out… what they are going to do… and how they are going to work with the legacy system to support the operations of the business. You build this new team based system along side the old way of doing things until the entire organization has moved to a team based model.
  • Where does a company like this start? How do they go from this siloed and complex project portfolio… one that is trying to manage a complex set of dependencies… to one made up of loosely coupled and independent small agile teams. I hope it goes without saying that this is not a trivial problem. The problem is very similar to the challenge a software architect faces when trying to move from a tightly coupled systems architecture with low cohesion to a loosely coupled modular software architecture with well defined responsibilities and interfaces. The general approach is to look for services that you can pull out… one at a time… and build a parallel system based on sound architectural principles. You have to define what services you are going to pull out… what they are going to do… and how they are going to work with the legacy system to support the operations of the business. You build this new team based system along side the old way of doing things until the entire organization has moved to a team based model.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • By keeping teams together…. Creating smaller work packages… and coordinating activities aross teams… we provide a platform that helps teams measure progress and get better over time.
  • People are trying to figure out how to effectively run iteration planning meetings and daily standups… they are struggling to figure out the best way to run a retrospectives… They are trying to get predictable…Almost universally I find that these companies are really struggling to create teams. The team concept is so foundational to adopting agile that if you don’t get this right… you have pretty much failed before you even got started. The ideal agile team is also a pretty specific concept and often antithetical to how we are current running our organizations when we decide to adopt agile.
  • Agile teams are cross functional units that have everything they need to deliver some increment of business value. In a software organization… the agile team is going to have one or more developers…
  • They will have one or more QA testers. Sometimes teams have technical testers that are responsible for writing unit tests… sometimes this is left up to the developers. Sometimes teams have manual testers… possibly exercising the UI. Many teams will do both kinds of testing.
  • Sometimes a team will someone playing the role of business analyst. This can be a dedicated position on the team… or it might be blended with some other role… maybe a lead developer. Often times teams will have a BA that is serving as a proxy product owner for the real customer or product owner. Dedicated or blended Custome proxy
  • Agile teams will usually have someone in the role of ScrumMaster or Agile process coordinator. This can be a dedicated position on the team or a role that is shared with another role on the team. Sometimes you have a dedicated ScrumMaster but they are working with more than one agile team at a time.
  • Agile Past The Team - Pillar Template

    1. 1. Agile Past the Team<br />An Experience Report<br />Presented by: Mike Cottmeyer<br />
    2. 2. mike cottmeyervice-president, pillar technology semcottmeyer@pillartechnology.com+1.404.312.1471www.pillartechnology.comwww.leadingagile.comtwitter.com/mcottmeyer<br />
    3. 3. Agenda<br />A little project background<br />
    4. 4. Agenda<br />A little project background<br />What was going well<br />
    5. 5. Agenda<br />A little project background<br />What wasn’t going well<br />
    6. 6. Agenda<br />A little project background<br />What wasn’t going well<br />The team’s initial response to problems<br />
    7. 7. Agenda<br />A little project background<br />What wasn’t going well<br />The team’s initial response to problems <br />Team based coaching approach<br />
    8. 8. Agenda<br />A little project background<br />What wasn’t going well<br />The team’s initial response to problems <br />Organization based coaching approach<br />
    9. 9. Agenda<br />A little project background<br />What wasn’t going well<br />The team’s initial response to problems <br />Organization based coaching approach<br />
    10. 10. Ready?<br />
    11. 11. Background<br />Waterfall since the company had formed<br />
    12. 12. Background<br />Waterfall since the company had formed<br />Evaluated Scrum<br />
    13. 13. Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />
    14. 14. Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />Chose Scrum because it was quicker to implement<br />
    15. 15. Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />Chose Scrum because it was they though quicker to implement<br />
    16. 16. Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />Chose Scrum because it was they thought quicker to implement<br />Flipped the switch overnight<br />
    17. 17. Background<br />Waterfall since the company had formed<br />Evaluated Scrum and RUP<br />Chose Scrum because it was they thought quicker to implement<br />Flipped the switch overnight during the Christmas holidays<br />
    18. 18. Going Well?<br />
    19. 19. Going Well?<br />Moved away from functional silos<br />
    20. 20. Going Well?<br />Moved toward cross functional teams<br />
    21. 21. Going Well?<br />Moved toward cross functional teams<br />Moved away from component teams<br />
    22. 22. Going Well?<br />Moved toward cross functional teams<br />Moved toward feature based teams<br />
    23. 23. Going Well?<br />Moved toward cross functional teams<br />Moved toward feature based teams<br />Product Manager for each team<br />
    24. 24. Going Well?<br />Moved toward cross functional teams<br />Moved toward feature based teams<br />Product Owner for each team<br />
    25. 25. Going Well?<br />Moved toward cross functional teams<br />Moved toward feature based teams<br />Product Owner for each team<br />Committed to following the Scrum process<br />
    26. 26. Not Going Well?<br />
    27. 27. Not Going Well?<br />Critical people shared across teams<br />
    28. 28. Not Going Well?<br />Critical people shared across teams<br />Didn’t know what to build<br />
    29. 29. Not Going Well?<br />Critical people shared across teams<br />Didn’t know what to build<br />Teams had trouble delivering<br />
    30. 30. Not Going Well?<br />Critical people shared across teams<br />Didn’t know what to build<br />Teams had trouble delivering anything<br />
    31. 31. Not Going Well?<br />Critical people shared across teams<br />Didn’t know what to build<br />Teams had trouble delivering anything<br />Unstable and not predictable<br />
    32. 32. Textbook Scrum<br />
    33. 33. Textbook ScrumNo working software<br />
    34. 34. My Role<br />
    35. 35. My Role<br />Purchased VersionOne<br />
    36. 36. My Role<br />Purchased VersionOne<br />Came in as a product trainer<br />
    37. 37. My Role<br />Purchased VersionOne<br />Came back as an agile coach<br />
    38. 38. My Role<br />Purchased VersionOne<br />Came back as an agile coach<br />The goal was to help the teams get better<br />
    39. 39. My Role<br />Purchased VersionOne<br />Came back as an agile coach<br />The goal was to help the teams get better<br />Learned quickly it was the organization that needed help<br />
    40. 40. Team Coaching<br />
    41. 41. Team Coaching<br />Big Rocks<br />
    42. 42. Team Coaching<br />Big Rocks<br />The Million Dollar Question<br />
    43. 43. Team Coaching<br />Big Rocks<br />The Million Dollar Question<br />Don’t game the numbers<br />
    44. 44. Team Coaching<br />Big Rocks<br />The Million Dollar Question<br />Don’t game the numbers<br />Retrospectives<br />
    45. 45. Org Coaching<br />
    46. 46. Org Coaching<br />Scrum-But<br />
    47. 47. Org Coaching<br />Scrum-But<br />Product and Architectural Vision<br />
    48. 48. Org Coaching<br />Scrum-But<br />Product and Architectural Vision<br />Product Owner Teams<br />
    49. 49. Org Coaching<br />Scrum-But<br />Product and Architectural Vision<br />Product Owner Teams<br />Well groomed backlog<br />
    50. 50. Million Dollar Question<br />
    51. 51. Plan<br />Execute<br />Close<br />
    52. 52. Plan<br />Close<br />Execute<br />
    53. 53. Plan<br />Execute<br />Close<br />Commit<br />
    54. 54. Deliver<br />Plan<br />Execute<br />Close<br />Commit<br />
    55. 55. Scrum-But<br />
    56. 56.
    57. 57. Developers<br />
    58. 58. Testers<br />Developers<br />
    59. 59. Analyst<br />Testers<br />Developers<br />
    60. 60. Analyst<br />CSM<br />Testers<br />Developers<br />
    61. 61. Product Owner<br />Analyst<br />CSM<br />Testers<br />Developers<br />
    62. 62. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    63. 63. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    64. 64. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    65. 65. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    66. 66. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    67. 67. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    68. 68. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    69. 69. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    70. 70. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    71. 71. Project (years)<br />Release (months)<br />Release (months)<br />Release (months)<br />I1<br />I2<br />I3<br />I4<br />I5<br />I6<br />I7<br />I8<br />I9<br />
    72. 72. Product Owner Teams<br />
    73. 73. Scrum of Scrums<br />Capability 2<br />Capability 1<br />Capability 3<br />
    74. 74. Product Owner Team<br />Capability 2<br />Capability 1<br />Capability 3<br />
    75. 75. Product Owner Team with<br />Architects<br />Capability 2<br />Capability 1<br />Capability 3<br />
    76. 76. Integration Team<br />Capability 2<br />Capability 1<br />Capability 3<br />
    77. 77. Context<br />Capability 2<br />Capability 1<br />Capability 3<br />
    78. 78. Context<br />Coordination<br />Capability 2<br />Capability 1<br />Capability 3<br />
    79. 79. Architecture and Design<br />
    80. 80. Guidance<br />Team<br />PO Team<br />PMO<br />Enterprise<br />Architecture<br />&<br />Epics <br />Solutions<br />Architecture<br />&<br />Features<br />Detailed<br />Design<br />&<br />Stories<br />
    81. 81. Feedback<br />Team<br />PO Team<br />PMO<br />Enterprise<br />Architecture<br />&<br />Epics <br />Solutions<br />Architecture<br />&<br />Features<br />Detailed<br />Design<br />&<br />Stories<br />
    82. 82. I1-N<br />I0<br />IH<br />
    83. 83. Construction<br />Elab.<br />Inc.<br />Trans.<br />I1-N<br />I0<br />IH<br />
    84. 84. Initiate<br />Plan<br />Execute<br />Monitor & Control<br />Close<br />Construction<br />Elab.<br />Inc.<br />Trans.<br />I1-N<br />I0<br />IH<br />
    85. 85. Grooming the Backlog<br />
    86. 86. Epic<br />Epic<br />Epic<br />Epic<br />Enterprise<br />Architecture<br />&<br />Epics <br />
    87. 87. Feature<br />Epic<br />Feature<br />Feature<br />Feature<br />Epic<br />Feature<br />Epic<br />Feature<br />Epic<br />Enterprise<br />Architecture<br />&<br />Epics <br />Solutions<br />Architecture<br />&<br />Features<br />
    88. 88. Feature<br />Epic<br />User Story<br />User Story<br />Feature<br />User Story<br />User Story<br />Feature<br />User Story<br />User Story<br />Feature<br />Epic<br />User Story<br />Feature<br />Epic<br />Feature<br />Epic<br />Enterprise<br />Architecture<br />&<br />Epics <br />Solutions<br />Architecture<br />&<br />Features<br />Detailed<br />Design<br />&<br />Stories<br />
    89. 89. Conclusion<br />
    90. 90. Conclusion<br />Forming and developing teams is critical<br />
    91. 91. Conclusion<br />Forming and developing teams is critical<br />The organization has tremendous impact on team effectiveness<br />
    92. 92. Conclusion<br />Forming and developing teams is critical<br />The organization has tremendous impact on team effectiveness<br />Managers need to understand their impact<br />
    93. 93. Conclusion<br />Forming and developing teams is critical<br />The organization has tremendous impact on team effectiveness<br />Managers need to understand their impact<br />Have to consider the entire delivery system<br />
    94. 94. Thoughts?<br />
    95. 95. mike cottmeyervice-president, pillar technology semcottmeyer@pillartechnology.com+1.404.312.1471www.pillartechnology.comwww.leadingagile.comtwitter.com/mcottmeyer<br />
    96. 96. www.slideshare.net/mcottmeyer<br />Agile Past the Team<br />An Experience Report<br />Presented by: Mike Cottmeyer<br />

    ×