Skip to main content

 

Language Selector

  1. Other Languages

    (machine translation)

Planview Customer Success Center

Agile Program Delivery - Agile

  1. Last updated
  2. Save as PDF

Definition

Agile Program Delivery provides a structure within which Agile teams of teams can deliver on their program plan.

Business Outcomes

Cross-Program Coordination

  • We can easily visualize connections between and across programs to understand dependencies, proactively anticipate issues, and mitigate risks.​

Program Execution​

  • We can understand if planned features are tracking to completion goals and see the impact of any unplanned features, including the likelihood of achieving planned delivery dates.​

  • We can foster continuous improvement with insights and analytics into delivery trends across the team of teams.

  • We can measure effectiveness, identify (and remove) bottlenecks, predict potential future issues, and adapt program workflow to optimize performance.​

Process Flow

           

Click a process step shape inside a light blue area for more information; hover for a quick view of the definition

           

Agile_Program_Delivery_process_flow.pngDeliver features through underlying stories Deliver cross-program dependencies Epic Portfolio Planning > Portfolio Backlog Management Agile Team Planning > Team Backlog Management Agile Program Planning

           

Program Execution Process Steps and Best Practices

The following table describes the Program Execution process steps, all of which take place Planview LeanKit.

Process Step Description
Deliver features from completed stories Agile teams develop and complete user stories for the features to deliver business value. Features are complete when all underlying stories are finished.

Program Execution Best Practices

  • As the Agile teams create stories for each feature, link the story cards as children of the feature card.
  • Use periodic feature demonstrations and retrospectives to implement feedback loops for continuous improvement.

           

           

Cross-Program Coordination Process Steps and Best Practices

The following table describes the Cross-Program Coordination process steps, all of which take place Planview LeanKit.

Process Step Description
Deliver cross-program dependencies Coordinate with other teams during program planning to see if there are any dependencies, redundancies, or obstacles that could affect the completion of the features for all teams.

Cross-Program Coordination Best Practices

  • During program planning, include a review of dependencies across teams.
  • To reflect dependencies between teams, link feature cards that have cross-program dependencies to related cards on other teams' program boards. It is important to coordinate across different teams' epic/program/team boards.

           

           

Outputs, Reports, and Analytics

Coming soon.