A@S: Program Management Practices (3)

Team is still co-located, but has more than 10 team members on core team

Modify Agile Management Practices

Iteration planning for I0 o Create a program team o Core team size <= ~15 people o Product Owner for the overall program o Team Lead for the overall program o Team Leads for initial sub teams on program team from start o Generalizing specialists: Analyst, Architect, Developer, Tester Iteration planning for I1, I2, etc o 1st draft of program level assets completed o Initial sub teams staffed, started and collaborating on program assets o Program team remains in place until program ends o Each subteam core team <= ~10 people o Some program team members work on sub teams as well o Program team membership may change, but always has a product owner, team lead and generalizing specialists Whole team o Create a roll up view of all sub team information radiators (wall, calendars, iteration and story burndown charts, etc) o Sub teams: add program stand up to team calendar, attend rotationally Agile Portfolio Management o Treat programs sub projects as a portfolio (sub project funding, sub project staffing, etc) Release Planning o Create a roll up view of sub team release plans o Sub teams: add program level logical releases to sub team release plan Risk-Value Lifecycle o Create roll up view of vision, architectural and general risks o Sub teams: escalate risks to program team Iterative Development o Sub teams: contribute to program level definition of done o Allocate program team requirements to sub projects iteration backlog o Sub teams: participate in program level demo o Sub teams: participate in program level retrospective o Create a roll up view of end of iteration metrics Team Change Management

o Use Project Change Requests (PCRs) to request changes to other projects o Ensure all sub teams can access each others assets o Create cross sub team integration spaces for collaboration on assets

Modify Engineering Practices

Shared Vision o Sub Projects: read, update and support the program vision o Sub Projects: reference the program vision where possible o Program Vision: Key elements are the sub programs o Program Vision: Key functionality at the total program level Project Value Measures o Reference program level measures where possible User Story Driven Development o Allocate entire stories or epics to teams to ensure demonstrable work Requires teams to be cross functional Breaks down silos Ensures useful demos at the program level o Create an epic/stories to skill needs map o Update team skill needs based on allocated stories and skill needs map Execute Architectural Proof of Concepts o Allocate prototypes to sub teams o Ensure prototypes align with risk-value lifecycle Envision the Architecture o Define architecture at the program and sub project levels o Assign mechanisms to specialized teams o Create an epic/story to mechanism map o Demo mechanisms solutions to impacted teams o Drive reuse across sub teams Refine the Architecture no change Evolutionary Design o Create sequences and classes at the program level o Allow subteams to volunteer for classes Continuous Integration o Create cross team integration spaces as well Test Driven Development no change Test Management o Create program level test mission, ideas, etc o Sub teams: conform to program left test mission, ideas, etc as appropriate

Concurrent Testing o Create test cases, scripts, and run tests at the program level Defect Prevention no change Evolutionary Deployment o Plan program level deployment o Sub projects: contribute to program level deployment plan

Consider New Practices

Consider automation to increase communication o Create an Electronic Wall with status of tasks and notification of change and automated information radiators o Automate Requirements with Traceability and History o Implement a change management solution with branching and merging capabilities o Capture risks and progress in an easily accessible tool