SAFe POPM study plan

Sequence the events of a single iteration (iteration planning, backlog refinement, system demo, Inspect & Adapt) and state each event's purpose, participants, and output

Differentiate which work belongs to the Product Owner at the team level versus the Product Manager at the strategy level

Write acceptance criteria for three sample stories using the behavior-driven, testable format

Explain how capacity, velocity, and story-point estimates combine to shape an iteration commitment

Refine a raw list of twelve backlog items into stories that are independent, negotiable, valuable, estimable, small, and testable

Calculate a weighted shortest job first ranking for ten backlog items and justify the ordering in writing

Assemble the inputs a Product Owner must bring to PI Planning: prioritized backlog, draft iteration goals, and dependencies

Identify which backlog items are too large to finish inside one iteration and split them

Draft a vision statement and a top-ten feature list with acceptance criteria that a team could plan against

Describe the preparation activities that occur before PI Planning for product management, the release train engineer, and the teams

Outline how draft PI objectives are written so they express business value rather than task lists

Prepare the planning context a leader must present in the business context briefing

Script the facilitation moves a leader uses across both days of PI Planning, including the confidence vote and management review

Classify five program risks as resolved, owned, accepted, or mitigated and assign an owner to each

Map how the program board reveals cross-team dependencies and where a leader intervenes when teams conflict

Distinguish the responsibilities of the Product Owner, Product Manager, and Business Owner across team, train, and portfolio levels

Build a responsibility matrix assigning product decisions to the Product Owner, Product Manager, and Business Owner at each level of the organization

Identify the product tasks where generative AI adds real leverage versus the tasks where it introduces risk

Write prompts that generate draft stories, acceptance criteria, and backlog summaries, then critique the outputs for factual and quality gaps

State the review and accountability rules that must apply before AI-generated product content is accepted

Run one real backlog through an AI drafting workflow, then score the output against story quality criteria

Describe the events that sustain a Program Increment after planning: the scrum of scrums or ART sync, system demo, and Inspect & Adapt

Explain how Inspect & Adapt turns a system demo and metrics into a prioritized improvement backlog

Differentiate the flow metrics and outcomes a Product Manager tracks during PI execution

Describe how problem-solving workshops convert root causes into actionable improvement items with owners

Trace how the ART backlog is built and how it competes for capacity against team backlogs

Explain continuous delivery practices and where the Product Owner influences release decisions

Rehearse the decisions a Product Owner owns when scope must change mid-PI

Re-test every domain against its exam weight and rank weak areas by the number of missed items

Complete a full-length timed practice set under exam conditions and log every incorrect answer with its root cause

Re-teach the three lowest-scoring topics in writing without reference material

Consolidate role differences, PI Planning inputs, and iteration event outputs into a single recall sheet