ADN Columbus 2013 - ScalingAgileWhileSherpasAreThrowingRocks

Transcript

1. Scaling Agile... While Sherpa’s are throwing rocks Brian Watson, CSM, PMI-ACP, IGQI @agilebdub
2. © 2011 VersionOne 2 Humble beginnings 60% of a score ago… Our agile forefathers put forth a new idea... Dedicated to the possibility that not all software development methodologies are created equal
3. © 2011 VersionOne 3 Manifesto Individuals and Interactions over process and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Source: www.agilemanifesto.org
4. © 2011 VersionOne 4 In the beginning...
5. © 2011 VersionOne 5 What are teams doing?
6. © 2011 VersionOne 6 Twelve Principles Behind The Agile Manifesto 1.  Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2.  Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3.  Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4.  Business people and developers must work together daily throughout the project. 5.  Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6.  The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7.  Working software is the primary measure of progress. 8.  Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9.  Continuous attention to technical excellence and good design enhances agility. 10.  Simplicity--the art of maximizing the amount of work not done--is essential. 11.  The best architectures, requirements, and designs emerge from self-organizing teams. 12.  At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Source: www.agilemanifesto.org
7. © 2011 VersionOne 7 Why are they doing it?
8. © 2011 VersionOne 8 IS this new Information?
9. © 2011 VersionOne 9 Shameless...
10. © 2011 VersionOne 10 Traditional Portfolio Management Portfolio Program(s) Projects
11. © 2011 VersionOne 11 Scaled Agile Framework™ Big Picture
12. © 2011 VersionOne 12 Scaled Agile Model Portfolio & Programs
13. © 2011 VersionOne 13 Scaled Agile Model - Team
14. © 2011 VersionOne 14 Team PSI
15. © 2011 VersionOne 15 Program PSI’s
16. © 2011 VersionOne 16 Portfolio PSI
17. © 2011 VersionOne 17 Caution Flags
18. © 2011 VersionOne 18 Positives Projects
19. © 2011 VersionOne 19 Twelve Principles Behind The Agile Manifesto 1.  Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2.  Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3.  Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4.  Business people and developers must work together daily throughout the project. 5.  Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6.  The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7.  Working software is the primary measure of progress. 8.  Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9.  Continuous attention to technical excellence and good design enhances agility. 10.  Simplicity--the art of maximizing the amount of work not done--is essential. 11.  The best architectures, requirements, and designs emerge from self-organizing teams. 12.  At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Source: www.agilemanifesto.org
20. © 2011 VersionOne 20 Hazards
21. © 2011 VersionOne 21 Even more hazards
22. © 2011 VersionOne 22 Who are the Sherpa's
23. © 2011 VersionOne 23 Stay in touch... –  Brian Watson, CBAP, CSM, PMP, PMI- ACP, PSM1, IGQI –  VersionOne Agile Coach and Product Consultant –  IT Background: Agile coach, Recovering project manager, Business Analyst, Scrum Master, –  Contact: brian@versionone.com @agilebdub http://www.linkedin.com/in/agilebdub www.agilebdub.com