Agile XXL. March 29, Scaling Agile for Project Teams. Alan Bustamante, PMP, PMI - ACP

Transcription

1 Agile XXL Scaling Agile for Project Teams Alan Bustamante, PMP, PMI - ACP March 29, 2011

2 Further Reading To learn more, download Agile XXL: Scaling Agile for Project Teams ebook

3 Agenda Scaling Defined The 3 Pillar Model Final Thoughts

4 Require 2 or more Sub teams One or more team members non collocated

5 Agenda Scaling Defined Three Pillar Model Final Thoughts

6 Success Pillars

7 Workspaces Partnerships Empowerment

8 Workspaces Co-located Project Developmen t Breakout Room Open Space Co-located Production Support Wall space for project schedules, burn downs or other charts Build/ Release Management

9 Planning Team Coordination Sub Team Structure

10 Traditional Process Definition Project Standards Group Dictates The Process Executes Discourage Ownership Increase Waste Inhibit Innovation Project A Project B Project C

11 Changing Will Not Be Easy

12 Agile Process Definition Project Process Evolving set of project specific practices Update Project Standards Group Evolving set of sub team practices Sub Team A Process Sub Team A Feedback Feedback Sub Team B Process Sub Team B Evolving set of sub team practices Evolving set of sub team practices Sub Team C Process Feedback Feedback Sub Team D Process Evolving set of sub team practices Sub Team C Sub Team D

13 Planning Negotiate Product Owner Council Pull Stakeholder Requests Populate Prioritize Stakeholders Story Map Story Map or prioritized list of stories Populate Tax Product Backlog Settlements Product Backlog Nominations Product Backlog Producer Services Product Backlog Tax Settlements Nominations Producer Services

14 Sub Team Structure Types Components Data Layer UI Layer Function Testing Engineering Tax Settlements Feature

15 A common Agile distributed model Deploy Good Build 8am EST/7:30pm IST Verify Fix 11am EST/10:30pm IST (11.5 hr lapse) Mean Time To Fix (MTTF): 38.5 hours Feature 1 Requirements Architecture Engineering Automated SIT Feature 2 Requirements Architecture Engineering Automated SIT Feature 1 Manual SIT Feature 2 Manual SIT Fix Verified 10:30pm EST/10am IST (11.5 hr lapse) Report Defect 11:30pm EST/11am IST (15.5 hr lapse) Based on Waterfall development

16 A better Agile distributed model Feature 1 Requirements Architecture Engineering Automated SIT Manual SIT Deploy Good build 8am Report Defect Noon Verify Fix 3pm Fix Verified 4pm Feature 2 Requirements Architecture Engineering Automated SIT Manual SIT Deploy Good build 8am Report Defect Noon Verify Fix 3pm Fix Verified 4pm MTTF: 7 hrs MTTF: 7 hrs Based on Agile development

17 Prioritization Code Quality Collaboration

18 Prioritization

19 Some Examples

20 Maximize Collaboration

21 Source:

22 Bake In Code Quality Jenkins Good Build Bad Build Continuous Integration Server Poll Repository Send Mainline Changes Mainline Houston, TX Deploy Good Build Model Office Server Manual SIT UAT Source Code Repository Santa Clara, CA Bucharest, Romania TDD, Unit Test, Local Integration Build TDD, Unit Test, Local Integration BuildTDD, Unit Test, Local Integration Build 2011 Seapine Software, Inc. All Rights Reserved

23 Agenda Scaling Defined The 3 Pillar Model Final Thoughts

24 Scaling Truths Fight the urge to be pure Agile Put Agile in industry context Put Agile in project bigness context Mute the zealots Focus on continuously improving the people, the process, and the tools

25 Give Feedback on the Sessions 1 Sign In: 2 Select Session Evaluate 3 Vote

26 Thank You! Award winning ALM solutions provider TestTrack Pro Issue and Defect Tracking TestTrack TCM Test Case Management TestTrack RM Requirements Management Surround SCM Source Code Management QA Wizard Pro Automated Functional & Load Testing Phone: