Agile at Scale - Agile Orlando Lightning Talk

532 views
429 views

Published on

For the reboot of the Agile Orlando use group, we did lightning talks on various topics. I shared some perspectives on scaling agile. More at http://agileorlando.com

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

No Downloads
Views
Total views
532
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
19
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Assume 15-30 seconds per slideI can do this talk in 6.5 min –Mark Kilby
  • Let’s just say, I’ve been doing this for a while …- Guided Agile adoptions at dozens of commercial & government organizations (including Fortune 20)>20 years in software - developer, architect, project manager, ScrumMaster, Product OwnerStarted agile coaching in 2003- co-founder of Agile Orlando and host of Lean Coffee Orlando
  • This is the question of scale: What do you do when you have more work than one team can execute to delivery timely value?
  • There are a number of frameworks currently available to answer this question (like SAFe and DAD) and some emerging frameworks.
  • There are a number of frameworks currently available to answer this question (like SAFe and DAD) and some emerging frameworks.
  • But to answer the question of scale, we need to go back to basics. Why do agile teams work?Here is a typical Scrum team. Why is this considered a successful structure?
  • But to answer the question, we need to
  • But to answer the question, we need to
  • 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
  • The small team commits to stakeholders and each other to complete a small increment of work
  • Then demonstrate results
  • When we scale, we need different cross-functional teams for different jobs
  • - Guided Agile adoptions at dozens of commercial & government organizations (including Fortune 20)>20 years in software - developer, architect, project manager, ScrumMaster, Product OwnerStarted agile coaching in 2003- co-founder of Agile Orlando and host of Lean Coffee Orlando
  • Agile at Scale - Agile Orlando Lightning Talk

    1. 1. Agile at Scale Lightning Talk – Agile Orlando Mark Kilby July 2013
    2. 2. Mark Kilby Enterprise Agile Coach Mark@LeadingAgile.com Mark@markkilby.com @mkilby– twitter http://markkilby.com Software since 1990 Coaching since 2003
    3. 3. WORK > one team’s capacity?
    4. 4. Scaled Agile Framework (SAFe)? Disciplined Agile Delivery (DAD) WORK > one team’s capacity? developing
    5. 5. Scaled Agile Framework (SAFe)? Disciplined Agile Delivery (DAD) Larman & Vodde (Scrum Alliance) Agile Path (Scrum.org) WORK > one team’s capacity? developing emerging
    6. 6. What is an Agile Team? Product Owner Analyst Testers Developers Scrum Master
    7. 7. Back to Basics - Why Teams Work • 5-10 people • Efficient communication • All skills to deliver work • Develop a culture and norms • Know each others strengths Product Owner Analyst Testers Developers Scrum Master
    8. 8. Back to Basics - Why Teams Work • 5-10 people • Efficient communication • All skills to deliver work • Develop a culture and norms • Know each others strengths Results in: • Predictable throughput • Regular delivery Product Owner Analyst Testers Developers Scrum Master
    9. 9. How Agile Teams Work
    10. 10. Team Database Report Screen User Story User Story User Story User Story User Story User Story User Story Clarity
    11. 11. Team Database Report Screen User Story User Story User Story User Story User Story User Story User Story Clarity Accountability
    12. 12. Team Database Report Screen User Story User Story User Story User Story User Story User Story User Story Clarity Accountability Measureable Progress
    13. 13. Different Teams for Different Jobs
    14. 14. Team Product Teams – These teams integrate services and write customer facing features. This is the proto-typical Scrum team.
    15. 15. Team Team Product Teams – These teams integrate services and write customer facing features. This is the proto-typical Scrum team. Services Teams – These teams support common services across product lines. These teams support the needs of the product teams.
    16. 16. Team Team Team Programs Teams – These teams define requirements, set technical direction, and provide context and coordination. Product Teams – These teams integrate services and write customer facing features. This is the proto-typical Scrum team. Services Teams – These teams support common services across product lines. These teams support the needs of the product teams.
    17. 17. Team Team Team Team Portfolio Teams – These teams govern the portfolio and make sure that work is moving through the system. Programs Teams – These teams define requirements, set technical direction, and provide context and coordination. Product Teams – These teams integrate services and write customer facing features. This is the proto-typical Scrum team. Services Teams – These teams support common services across product lines. These teams support the needs of the product teams.
    18. 18. Agile Delivery Structure
    19. 19. Team Team TeamTeam Team Team Team Team Product & Services Teams
    20. 20. Team Team Team Team Team Team Team Team Team Team Team Product & Services Teams Program Teams
    21. 21. Team Team Team Team Team Team Team Team Team Team Team Team Product & Services Teams Program Teams Portfolio Teams
    22. 22. Team Team Team Team Team Team Team Team Team Team Team Team Product & Services Teams Program Teams Portfolio Teams Scrum
    23. 23. Team Team Team Team Team Team Team Team Team Team Team Team Product & Services Teams Program Teams Portfolio Teams Scrum Kanban
    24. 24. Team Team Team Team Team Team Team Team Team Team Team Team Product & Services Teams Program Teams Portfolio Teams Scrum Kanban Kanban
    25. 25. How to Launch
    26. 26. Understand Business Drivers •Predictability •Quality •Early ROI
    27. 27. Set Vision for Scaling Structure GovernanceMetrics
    28. 28. Prep Teams Structure GovernanceMetrics Form Teams Teach Practices Guide Culture
    29. 29. Provide Support Structure GovernanceMetrics Assessment Targeted Coaching Measure Improvement Form Teams Teach Practices Guide Culture
    30. 30. Inspect and Adapt Change Management & Communication Structure GovernanceMetrics Assessment Targeted Coaching Measure Improvement Form Teams Teach Practices Guide Culture
    31. 31. Mark Kilby Enterprise Agile Coach Mark@LeadingAgile.com Mark@markkilby.com @mkilby– twitter http://markkilby.com THANKS! Questions? Join us for Lean Coffee on Friday

    ×