This module introduces program increment (PI) planning, the event where many agile teams plan the next 8 to 12 weeks of work together. You will explore why plans kept in separate spreadsheets break down, how a two-day planning event moves from vision to commitment, and how a program board shows teams, sprints and capacity in one view. You will also see how to calculate team capacity, schedule stories into sprints without overloading them, and decide what to do when the work does not fit. These skills help you contribute to a plan that teams can realistically keep.

This module introduces how to make cross-team dependencies and delivery risks visible before they break a plan. You will explore why unrecorded dependencies and unowned risks often cause missed commitments, how a dependency moves from identified to delivered, and how the ROAM model (resolved, owned, accepted, mitigated) gives every risk a clear decision. You will also see how to link and check a dependency in Jira, track risks on a board, and practise negotiating with another team in a role play. These skills help you spot problems early and resolve them through conversation before escalation is needed.

This module introduces program increment (PI) objectives, the short business-focused statements that summarize what a team or program intends to achieve within a planning increment. You will explore why feature lists rarely work for executives, how to test an objective against the SMART criteria, when to label an objective as committed or stretch, and how business value scoring helps leaders compare outcomes. You will also review common weak objectives and see how to rewrite them. These skills help you present a plan in terms that leadership can understand and evaluate.

This module introduces live, data-driven roadmaps as an alternative to roadmaps maintained on slides. You will explore why manually drawn roadmaps quickly go out of date, how Jira Align roadmaps use backlog data to show now, next and later time horizons, and how one roadmap can be adjusted for delivery teams and for executives. You will also learn how to label items by confidence, prepare a customer-facing version and set a regular update cadence. These skills help you share plans that people can trust and communicate changes without losing credibility.

This module introduces how to track progress during a planning increment using data drawn from the teams’ own work rather than self-reported status. You will explore the Jira Align Program Room and three core signals: burndown, load versus capacity, and objective progress. You will also see how to read rolled-up progress and build a simple progress dashboard in Jira, recognize common burndown patterns, and agree on thresholds that trigger action. These skills help you spot problems early and keep status conversations focused on decisions.