SAFe POPM flashcards
SAFe POPM · Build recall with a focused review session.
31 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Product Management content authority
- Product Management owns the ART's program backlog, defining and prioritizing the features that deliver the vision. It decides what the ART builds and why, and validates outcomes.
- Product Owner content authority
- The Product Owner owns the team backlog, decomposing features into stories with acceptance criteria, ordering the backlog, and accepting completed work from the team.
- PM versus PO focus
- Product Management faces outward toward customers, market, and ART stakeholders; the Product Owner faces inward toward the team, supporting iteration execution and day-to-day backlog decisions.
- Feature versus story
- A feature is an ART-level service meeting a stakeholder need, sized to be delivered within a PI; a story is a small team-level item completable in one iteration.
- Product Manager vision responsibility
- Product Management contributes to the solution vision and roadmap, then translates them into features and an ordered program backlog that the ART can plan against.
- PI Planning readiness checklist
- Before PI Planning, confirm features are prioritized with acceptance criteria, teams have capacity estimates, draft objectives exist, and planning-board logistics and tooling are ready.
- Draft PI objectives
- Preliminary team objectives prepared before PI Planning that describe intended business and technical outcomes for the PI; they are refined and committed during the event.
- WSJF before PI Planning
- Features are prioritized using Weighted Shortest Job First, cost of delay divided by job size, so the program backlog is ordered before teams plan.
- Team capacity estimation
- Teams compute available capacity for the PI from iteration count, member availability, and known absences, then load stories against that capacity during planning.
- Management business context
- The opening briefing of PI Planning where business owners and executives present the business context, the vision, and the top features for the PI.
- Confidence vote
- After the draft plan review, each team member votes one to five fingers; a team average below three signals risk requiring discussion and re-planning.
- ROAM risks
- A leadership technique for PI Planning risks: Resolved, Owned, Accepted, or Mitigated. Each significant risk receives one disposition and, where needed, an owner.
- Management review and problem-solving
- A PI Planning agenda step where leadership and teams adjust scope, resolve cross-team dependencies, and address risks raised during the draft plan review.
- Business value assignment
- Business owners assign business value from one to ten to each team's PI objectives, letting the ART compare planned value with value actually achieved.
- Iteration planning
- The team selects backlog items up to its capacity, agrees an iteration goal, and decomposes stories into tasks, committing to the iteration plan.
- Iteration goal
- A short statement of the business or technical outcome the team intends to achieve in the iteration; it guides story selection and daily decisions.
- Story acceptance criteria
- Conditions written by the Product Owner that a story must satisfy to be accepted; they define the story's boundaries and support testing.
- Velocity
- The average number of story points a team completes per iteration, used to forecast how much work fits in future iterations rather than to rate performance.
- Team sync
- A daily fifteen-minute event where team members coordinate progress toward the iteration goal, raise impediments, and adjust the day's plan.
- Backlog refinement
- Ongoing activity where the Product Owner and team clarify, split, estimate, and add acceptance criteria to upcoming stories so they are ready for iteration planning.
- System demo
- An event at the end of each iteration where teams demonstrate integrated work from all teams in the ART to stakeholders, who provide feedback.
- Innovation and Planning iteration
- An IP iteration follows each PI except the final one; it provides time for innovation, backlog refinement, and planning without committing to new stories.
- ART sync
- A weekly event combining the PO sync and the Scrum of Scrums so Product Management, Product Owners, and team representatives align on PI objective progress.
- PO sync
- A recurring meeting where Product Owners and Product Management review progress toward PI objectives, adjust the program backlog, and address scope changes.
- PI System Demo
- The final system demo of the PI, showing cumulative integrated value from all teams to stakeholders and providing input to the Inspect and Adapt event.
- Inspect and Adapt event
- A PI-end event combining the PI system demo, quantitative and qualitative measurement, and a problem-solving workshop where the ART identifies and addresses root causes.
- AI-assisted story drafting
- Generative AI can propose story descriptions, acceptance criteria, and test ideas from feature context; a Product Owner must review and correct every draft before use.
- Human accountability for AI
- The Product Owner or Product Manager remains accountable for all AI-assisted backlog content and decisions; AI output is treated as a draft requiring verification.
- AI feedback summarization
- AI models cluster and summarize large volumes of customer feedback, reviews, and support tickets, helping Product Management surface themes faster than manual review.
- AI data guardrails
- Rules restricting AI tools from receiving confidential, personal, or proprietary data unless the tool is formally approved, ensuring policy and privacy compliance.
- AI in prioritization
- AI can forecast demand, score sentiment, and estimate effort to inform WSJF inputs, but people make the final prioritization decisions and own the trade-offs.