Agile Program Management provides a structure to carry out quarterly planning. It provides teams and teams of teams with a way to visualize, plan, and coordinate organizational initiatives quickly, effectively, and with clarity into the value delivered.
Program Backlog Management
- 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.
- 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.
Click a process step shape inside a light blue area for more information; hover for a quick view of the definition
Program Backlog Management Process Steps and Best Practices
The following table describes the Program Backlog Management process steps, all of which take place Planview LeanKit.
Program Backlog Management Best Practices
- Use the board's backlog lane to help manage your timeboxes (such as program increments) and track the progress of features.
- Regularly review your backlog and replenish your input queue with items from the backlog as work gets completed.
- Periodically evaluate the age of cards in your backlog and decide if those items are still relevant; these cards may not be of high-enough priority to enter your process flow.
- To prioritize the story backlog, you can use the Weighted Shortest Job First (WSJF) model, which ranks each story by dividing the cost of delaying work by the size of the work. Then schedule the stories that can deliver the most value in the least amount of time first.
Program Capacity Planning Process Steps and Best Practices
The following table describes the Program Capacity Planning process steps, all of which take place Planview LeanKit.
Program Capacity Planning Best Practices
- As the Agile teams create stories for each feature, link the story cards as children of the feature card.
- Ensure that total time needed to complete the features does not overload the capacity of the assigned teams.
Program OKRs Process Steps and Best Practices
The following table provides information for Program OKRs, information for which is viewable in Planview LeanKit.
Program OKRs Best Practices
- Track progress towards OKRs using early indicators, such as website traffic, app usage, and in-app feedback.
- Use direct customer feedback through social media engagement, focus groups, and other channels to assess the progress of any given initiative.
- Objectives can be long-lived (a year or longer), while key results evolve as the work progresses.
Kanban Best Practices
- After using the program board for a few months, it is typical—and even expected—to refine your process and board design to improve the flow of work.
Outputs, Reports, and Analytics