Skip to main content
Planview Customer Success Center

Agile Program Planning - Lean

Definition

Agile Program Planning provides a structure to carry out quarterly planning, providing teams with a way to visualize, plan, and coordinate organizational initiatives quickly, effectively, and with clear insight into the value delivered.

Business Outcomes - Lean

Portfolio Backlog Management​

  • We can visualize all planned and unplanned epics on a portfolio kanban board.​

  • We can customize kanban boards to reflect the existing portfolio processes.​

  • We can add epics to the portfolio backlog and estimate size and complexity as appropriate.​

  • We can analyze and sequence epics in the context of size, value, and team capacity/velocity considerations.​

  • We can create aligned autonomy by associating work on team and program boards to the portfolio kanban board.​

Portfolio Capacity Planning​

  • We can carry out high-level, visual capacity planning at the portfolio level by utilizing work-in-progress limits on the portfolio kanban board​

  • We have a systematic way of tracking how efficiently teams can deliver work within a fixed period of time (e.g., a Program Increment) and can use this data to inform future capacity planning and management.​

Program Backlog Management​

  • We can visualize all planned and unplanned features on a program kanban board.​

  • We can customize kanban boards to reflect the existing program processes.​

  • We can break down epics into features, adding them to the program backlog and estimating size/value/complexity as appropriate.​

  • We can dynamically prioritize and sequence features in the context of size, value and team capacity/velocity considerations.​

  • We can easily and effectively carry out both in-person or virtual quarterly planning. We can use the visualization of the kanban boards to balance priorities, sequence work, and communicate realistic delivery timelines.​

Program Capacity Planning​

  • We can carry out visual capacity planning at the program level by utilizing work-in-progress limits on the program kanban board.​

  • We have a systematic way of tracking how efficiently teams can deliver work within a fixed period of time (e.g., a Program Increment) and can use this data to inform future capacity planning and management.​

Program OKRs​

  • We can create program objectives, aligned with portfolio-level objectives, and associate the relevant key results for tracking.​

  • We can measure the progress of program OKRs by capturing associated metrics for the key result score and rolling up the objective.​

  • We can track the activity history for the key result progress changes for auditability.​

  • We can align work activities with program OKRs by connecting key results to LeanKit cards.​

Process Flow

Coming soon.

Best Practices

Coming soon.