8/12/2019 Agile Program Management Practices
2/3
o Use Project Change Requests (PCRs) to request changes to
otherprojects
o Ensure all sub teams can access each others assetso Create
cross sub team integration spaces for collaboration on assets
Modify Engineering Practices Shared Vision
o Sub Projects: read, update and support the program visiono Sub
Projects: reference the program vision where possibleo Program
Vision: Key elements are the sub programso Program Vision: Key
functionality at the total program level
Project Value Measureso Reference program level measures where
possible
User Story Driven Developmento 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 mapo Update team skill
needs based on allocated stories and skill needs map
Execute Architectural Proof of Conceptso Allocate prototypes to
sub teamso Ensure prototypes align with risk-value lifecycle
Envision the Architectureo Define architecture at the program
and sub project levelso Assign mechanisms to specialized teamso
Create an epic/story to mechanism mapo Demo mechanisms solutions to
impacted teamso Drive reuse across sub teams
Refine the Architectureno change Evolutionary Design
o Create sequences and classes at the program levelo Allow
subteams to volunteer for classes
Continuous Integrationo Create cross team integration spaces as
well
Test Driven Developmentno change Test Management
o Create program level test mission, ideas, etco Sub teams:
conform to program left test mission, ideas, etc as
appropriate
8/12/2019 Agile Program Management Practices
3/3
Concurrent Testingo Create test cases, scripts, and run tests at
the program level
Defect Preventionno change Evolutionary Deployment
o Plan program level deploymento 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 ofchange and automated information radiators
o Automate Requirements with Traceability and Historyo Implement
a change management solution with branching and merging
capabilities
o Capture risks and progress in an easily accessible tool
