I85PREP
⌘ K
SAFe POPM study materials
SAFe POPM study resources

SAFe POPM practice questions

One question at a time. Build your SAFe POPM understanding.

First 50 of 197 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Who is accountable for the team backlog in a SAFe Agile Team?

  1. Product Owner Correct answer.
  2. System Architect
  3. Product Management
  4. Release Train Engineer

Explanation

In SAFe, the Product Owner is the content authority for the team backlog and works with the Agile team to define, refine, and accept stories. Product Management owns the program backlog rather than the team backlog. Other ART roles support flow and architecture but do not own the team backlog.

Question 2Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Which role owns and prioritizes the program backlog in SAFe?

  1. Product Owner
  2. Release Train Engineer
  3. Business Owner
  4. Product Management Correct answer.

Explanation

Product Management owns the program backlog and is responsible for defining, prioritizing, and maintaining features. Product Owners then work with teams to decompose those features into team backlog items. The RTE and Business Owners have different ART-level responsibilities.

Question 3Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Which role most directly represents the customer's voice to the Agile team during iteration execution?

  1. Product Owner Correct answer.
  2. System Architect
  3. Product Management
  4. Scrum Master

Explanation

The Product Owner acts as the customer proxy for the Agile team, clarifying needs and making backlog trade-off decisions during the iteration. Product Management works more broadly with customers and stakeholders at the program level. This team-level representation is a core SAFe Product Owner responsibility.

Question 4Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

What is Product Management primarily accountable for in SAFe?

  1. Facilitating team ceremonies
  2. Writing team stories and acceptance criteria
  3. Defining and prioritizing program features Correct answer.
  4. Accepting team stories each iteration

Explanation

Product Management is accountable for the program backlog, including defining and prioritizing features that deliver value. Product Owners handle team-level story definition, refinement, and acceptance. Ceremony facilitation and team process coaching belong to other roles.

Question 5Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Who accepts user stories as done at the end of an iteration?

  1. Scrum Master
  2. Release Train Engineer
  3. Product Management
  4. Product Owner Correct answer.

Explanation

The Product Owner accepts stories based on whether they meet the agreed acceptance criteria and deliver the intended value. Product Management focuses on feature-level acceptance and program priorities. This separation keeps team-level decisions close to the team.

Question 6Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

At PI Planning, which role presents the product vision and top features to the Agile Release Train?

  1. Release Train Engineer
  2. Product Management Correct answer.
  3. System Architect
  4. Product Owner

Explanation

Product Management presents the product vision, top features, and priorities that guide the ART during PI Planning. Product Owners then help teams understand and plan the work for their portions of the backlog. This flow aligns program intent with team execution.

Question 7Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Who typically decomposes features into user stories for the team backlog?

  1. System Architect
  2. Product Owner Correct answer.
  3. Release Train Engineer
  4. Product Management

Explanation

Product Owners decompose program features into user stories that the team can estimate and implement. Product Management defines the features but does not usually create the team-level stories. This decomposition supports team-level planning and delivery.

Question 8Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Which pair of roles must collaborate to align the team backlog with the program backlog?

  1. Product Owner and Scrum Master
  2. Product Management and Release Train Engineer
  3. System Architect and Business Owner
  4. Product Owner and Product Management Correct answer.

Explanation

Product Owners and Product Management collaborate continuously so that team backlog work reflects program feature priorities and emerging learning. Product Management sets feature priority, while the Product Owner sequences and clarifies the team's stories. This alignment is central to SAFe's dual product role.

Question 9Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

A Product Manager defines a new feature with clear acceptance criteria. What is the most appropriate next step for moving it into execution?

  1. Add the feature to the team backlog without any team discussion
  2. Work with the Product Owner to split it into stories Correct answer.
  3. Ask the Scrum Master to write the detailed user stories
  4. Assign the feature directly to an individual developer on the team

Explanation

Features become actionable for a team when the Product Owner collaborates with the team to decompose them into stories and refine the details. Direct assignment bypasses team planning and backlog ownership. The Product Owner, not the Scrum Master, owns team story definition.

Question 10Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

A Product Owner finds a story lacks enough detail for the team to estimate. What should the Product Owner do?

  1. Defer all questions until the system demo
  2. Cancel the story and remove it from the backlog
  3. Refine the story with the team before committing Correct answer.
  4. Ask Product Management to write the team story

Explanation

Backlog refinement is the Product Owner's opportunity to clarify intent, acceptance criteria, and examples with the team so the story can be estimated. Removing the story or escalating story writing to Product Management avoids the Product Owner's responsibility. Waiting until the system demo delays learning too far.

Question 11Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Mid-iteration, Product Management wants to add a new high-priority feature. What is the Product Owner's best action?

  1. Ignore the request until the next PI Planning event
  2. Immediately insert the feature into the current iteration
  3. Review impact with the team and Product Management Correct answer.
  4. Tell the team to stop all current work and start it

Explanation

The Product Owner should assess the impact on the iteration goal and committed work with the team and Product Management. This preserves transparency and allows a deliberate trade-off rather than an abrupt change. Ignoring the request or forcing an immediate switch undermines trust and flow.

Question 12Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

A Product Owner needs to know whether a feature depends on upcoming architectural work. Which role should be consulted?

  1. System Architect Correct answer.
  2. Scrum Master
  3. Business Owner
  4. Release Train Engineer

Explanation

The System Architect helps the ART understand architectural runway and technical dependencies that affect feature feasibility. Product Owners should involve this role when technical direction may constrain or enable backlog work. The Scrum Master and RTE focus on process and flow rather than architecture.

Question 13Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Product Management has several competing features. Which SAFe approach best supports prioritizing them economically?

  1. Apply Weighted Shortest Job First to the features Correct answer.
  2. Let the team choose the feature it prefers
  3. Prioritize the feature requested by the loudest stakeholder
  4. Sequence features by the date they were requested

Explanation

Weighted Shortest Job First provides an economic prioritization model based on value and job size. It helps Product Management compare competing features more objectively than opinion or request order. This supports better sequencing of program backlog items.

Question 14Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

A stakeholder asks a Product Owner to add a new story directly to the team. What should the Product Owner do?

  1. Refuse all stakeholder input to protect the team
  2. Evaluate it through the team backlog and PM alignment Correct answer.
  3. Add it immediately to preserve the stakeholder relationship
  4. Send the stakeholder to the Scrum Master for approval

Explanation

The Product Owner should evaluate the request against team backlog priorities and align with Product Management as needed. This maintains a single, visible flow of work while respecting stakeholder input. Immediate insertion or blanket refusal both undermine transparency.

Question 15Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Who is responsible for defining acceptance criteria for a feature, as opposed to a user story?

  1. Product Management Correct answer.
  2. Scrum Master
  3. Release Train Engineer
  4. Product Owner

Explanation

Product Management defines features and their acceptance criteria at the program level. The Product Owner then defines story-level acceptance criteria for the team. This distinction keeps feature intent and team-level detail appropriately separated.

Question 16Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

During PI Planning breakout sessions, what is the Product Owner's primary contribution?

  1. Presenting the ART vision and top features
  2. Facilitating the retrospective and confidence vote
  3. Managing the architectural runway discussion
  4. Clarifying stories and priorities for the team Correct answer.

Explanation

In breakout sessions, the Product Owner helps the team understand stories, clarify priorities, and shape a realistic team plan. Product Management presents the broader vision and feature priorities. The RTE and Scrum Master facilitate the planning process itself.

Question 17Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

When prioritizing the team backlog, which factors should a Product Owner weigh most?

  1. The number of story points already completed
  2. Value, risk, dependencies, and capacity Correct answer.
  3. Only the order in which stories were written
  4. Only the preferences of individual developers

Explanation

Team backlog priority should reflect customer value, risk, dependencies, and the team's capacity to deliver. These factors help the Product Owner sequence work for flow and learning. Request order, individual preference, or past story points alone are weak prioritization inputs.

Question 18Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Product Management wants to confirm that a feature remains desirable, feasible, and viable. Which collaboration is most relevant?

  1. Working with Product Owners, architects, and stakeholders Correct answer.
  2. Delegating the decision entirely to the Agile team
  3. Working only with the Release Train Engineer on timing
  4. Working only with the Scrum Master on process metrics

Explanation

Product Management validates desirability, feasibility, and viability by collaborating across customers, Product Owners, architects, and stakeholders. This cross-functional input balances market need, technical reality, and business sustainability. A single role or isolated metric cannot confirm all three dimensions.

Question 19Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

A Product Owner and Product Manager disagree about feature scope for the next iteration. What is the most constructive SAFe approach?

  1. Let the team decide which leader to follow
  2. Use objective data and ART priorities to reach alignment Correct answer.
  3. Defer the feature indefinitely to avoid conflict
  4. Escalate immediately to the Business Owner for a decision

Explanation

Product Owners and Product Management are expected to collaborate closely and resolve scope questions using data, customer feedback, and ART priorities. Immediate escalation or deferral avoids the shared accountability intended by the roles. The team should not be forced to arbitrate leadership disagreement.

Question 20Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

A team asks the Product Owner to add an unplanned story during an iteration. What should the Product Owner consider first?

  1. Whether the iteration goal remains achievable Correct answer.
  2. Whether the story has already been estimated
  3. Whether the story can be completed without any team discussion
  4. Whether the story is interesting to the developers

Explanation

The Product Owner should first consider whether the change preserves the iteration goal and committed work. This protects focus and transparency while allowing deliberate trade-offs. Interest level or prior estimation is not the primary decision criterion.

Question 21Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

In SAFe, how do the decision rights of Product Management and the Product Owner differ regarding backlogs?

  1. The Product Owner owns the program backlog; Product Management owns the team backlog
  2. The Release Train Engineer owns both backlogs and assigns story priority
  3. Product Management owns both backlogs; the Product Owner only writes stories
  4. Product Management owns the program backlog; the Product Owner owns team backlog Correct answer.

Explanation

SAFe separates content authority between the program and team levels: Product Management owns the program backlog, and the Product Owner owns the team backlog. The two roles collaborate so that features flow into team stories that deliver the intended value. This division keeps program strategy and team execution connected but distinct.

Question 22Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

A Product Manager is accountable for outcome viability across the product lifecycle. Which behavior best reflects that accountability in SAFe?

  1. Balancing customer needs, stakeholders, and ART priorities Correct answer.
  2. Approving all team retrospectives before actions are taken
  3. Writing every user story for the Agile teams
  4. Facilitating daily stand-ups for multiple teams

Explanation

Lifecycle viability requires Product Management to balance customer needs, stakeholder interests, and ART priorities over time. This is broader than producing team-level stories or facilitating team ceremonies. The role is accountable for product outcomes, not routine team process control.

Question 23Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

A feature meets its defined acceptance criteria but the Product Owner still has concerns about story-level behavior. What is the most accurate SAFe interpretation?

  1. Story acceptance and feature acceptance are identical decisions
  2. The Product Owner must accept the feature on behalf of Product Management
  3. Feature acceptance and story acceptance are distinct responsibilities Correct answer.
  4. The feature cannot be accepted until every story is rewritten

Explanation

Feature acceptance and story acceptance occur at different levels and involve different accountabilities. Product Management is associated with feature-level acceptance, while the Product Owner accepts stories. A concern at one level should be resolved through collaboration rather than by collapsing the two decisions.

Question 24Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

How should Product Management and Product Owners handle capacity allocation for enablers and features in SAFe?

  1. Product Management and Product Owners agree on a balanced allocation Correct answer.
  2. Capacity allocation is handled only by the Release Train Engineer
  3. Enablers are excluded from capacity allocation and backlog planning
  4. Product Owners set all capacity allocation without Product Management input

Explanation

Capacity allocation should balance new features with enablers and other work needed to sustain flow. Product Management and Product Owners collaborate to set that balance based on strategy, architecture needs, and delivery realities. Excluding enablers or assigning allocation to a single role undermines that balance.

Question 25Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

During a system demo and Inspect & Adapt, what is the Product Owner's most relevant responsibility?

  1. Present only the team's velocity metrics to Business Owners
  2. Approve the ART's budget for the next program increment
  3. Facilitate the problem-solving workshop for the entire ART
  4. Assess delivered value and feed backlog adjustments Correct answer.

Explanation

Product Owners assess delivered value in the system demo and use that learning to adjust team backlogs and priorities. This connects demonstrated outcomes to future work. Budget approval and full ART problem-solving facilitation are not their primary responsibilities.

Question 26Understanding Product Owner/Product Management Roles and Responsibilities (12-14%)

Several Agile Teams on an Agile Release Train are drifting from the PI plan, and cross-team dependencies between features are at risk. Product Management and the Product Owners need a recurring forum to review progress toward the PI objectives and adjust scope together. Which forum is intended for this purpose?

  1. PO Sync Correct answer.
  2. Daily Stand-up
  3. System Demo
  4. Inspect & Adapt

Explanation

The PO Sync is the recurring event where Product Management and the Product Owners align on progress toward the PI objectives, surface risks and dependencies, and adjust scope or priorities as needed. It is the main mechanism for keeping the program backlog and team backlogs synchronized during the PI. Team-level ceremonies and the end-of-PI events serve different purposes.

Question 27PI Planning Preparation (17-19%)

Which three dimensions are commonly used to assess readiness for a PI Planning event in SAFe?

  1. Financial readiness, staffing readiness, and vendor tooling readiness
  2. Team, vendor, and audit readiness
  3. Organizational, content, and logistics readiness Correct answer.
  4. Vision, budget, and compliance readiness

Explanation

SAFe assesses PI Planning readiness across organizational, content, and logistics dimensions. Organizational readiness covers alignment and people, content readiness covers vision, features, and architecture, and logistics readiness covers venue, tools, and communications.

Question 28PI Planning Preparation (17-19%)

Who typically presents the business context at the start of PI Planning?

  1. The team's Product Owner, who presents the team backlog
  2. The Business Owners or senior leadership Correct answer.
  3. The System Architect
  4. The Scrum Master

Explanation

Business Owners or senior leaders set the business context so teams understand the strategic drivers, current state, and priorities for the upcoming PI. This context frames all subsequent planning.

Question 29PI Planning Preparation (17-19%)

Which role is primarily accountable for ensuring content readiness before PI Planning, including a refined top 10 features list?

  1. Scrum Master
  2. Business Owners
  3. Release Train Engineer
  4. Product Management Correct answer.

Explanation

Product Management owns the ART backlog and prepares the vision, roadmap, and prioritized top 10 features before PI Planning. The RTE handles logistics and facilitation, while Business Owners provide context and value assignment.

Question 30PI Planning Preparation (17-19%)

What is the purpose of the 'top 10 features' presented at PI Planning?

  1. To list every user story the teams will complete in the PI
  2. To document all defects found in the prior PI
  3. To define the team's iteration goals for the first sprint
  4. To highlight the highest-priority features for planning Correct answer.

Explanation

The top 10 features communicate the highest-priority planned value for the PI and guide teams as they create their plans. They are not a complete story-level commitment.

Question 31PI Planning Preparation (17-19%)

During team breakouts at PI Planning, which set of outputs is expected from each team?

  1. A finalized budget, a staffing plan, and a vendor contract
  2. An updated product roadmap and a revised vision statement
  3. A draft plan, risks, dependencies, and draft PI objectives Correct answer.
  4. A signed release contract and a deployment schedule

Explanation

Team breakouts produce a draft team plan for the PI, along with identified risks, cross-team dependencies, and draft PI objectives. These outputs feed the draft plan review and problem solving.

Question 32PI Planning Preparation (17-19%)

After teams draft PI objectives, who assigns business value to them?

  1. The Release Train Engineer
  2. The team members by consensus
  3. The Business Owners Correct answer.
  4. The Scrum Master

Explanation

Business Owners assign business value to the PI objectives after teams draft them. This helps leadership understand the relative value of each team's commitments.

Question 33PI Planning Preparation (17-19%)

What is the purpose of the confidence vote at the end of PI Planning?

  1. To approve the ART's annual budget
  2. To confirm commitment and surface concerns Correct answer.
  3. To rank all features by their cost of delay and job size
  4. To select the next PI's Product Owner

Explanation

Each team uses a confidence vote, often a fist of five, to indicate how confident it is in its plan. Low confidence signals that the plan needs rework before commitment.

Question 34PI Planning Preparation (17-19%)

During PI Planning, how are risks typically handled after they are identified?

  1. They are logged and deferred to the Inspect and Adapt workshop
  2. They are ROAMed: resolved, owned, accepted, or mitigated Correct answer.
  3. They are escalated to the finance department for approval
  4. They are added to the team backlog as user stories

Explanation

Identified risks are addressed through ROAM: Resolved, Owned, Accepted, or Mitigated. This keeps risks visible and assigns clear accountability during planning.

Question 35PI Planning Preparation (17-19%)

What does the ART program board primarily visualize?

  1. The organization's financial forecast
  2. Individual team member assignments and vacation schedules
  3. Feature delivery timelines and cross-team dependencies Correct answer.
  4. Job descriptions and staffing gaps

Explanation

The program board shows feature delivery across iterations and highlights cross-team dependencies and milestones. It is a key planning artifact for managing flow across the ART.

Question 36PI Planning Preparation (17-19%)

What is the primary purpose of the Innovation and Planning (IP) iteration?

  1. To deliver the highest-priority features to production
  2. To conduct individual performance reviews and career planning sessions
  3. To provide buffer time for innovation, education, and the system demo Correct answer.
  4. To replace the need for PI Planning by using continuous planning

Explanation

The IP iteration provides a buffer for estimation error and creates time for innovation, education, and the PI system demo. It is built into the PI cadence rather than replacing planning.

Question 37PI Planning Preparation (17-19%)

How do teams typically estimate their capacity for the upcoming PI?

  1. By using historical velocity, adjusted for holidays and training Correct answer.
  2. By asking the Business Owners to allocate a percentage of the budget
  3. By copying the previous PI's commitments without changes
  4. By multiplying the number of team members by the number of days in the PI

Explanation

Capacity is estimated from historical velocity adjusted for known events such as holidays, training, and other absences. This produces a realistic basis for planning the PI.

Question 38PI Planning Preparation (17-19%)

Who typically presents the architectural vision and runway at PI Planning?

  1. The Product Owner
  2. The System Architect/Engineer Correct answer.
  3. The Business Owner
  4. The Scrum Master

Explanation

The System Architect or Engineer presents the architectural vision and runway so teams understand the technical direction and enablers needed for the PI.

Question 39PI Planning Preparation (17-19%)

Which role is responsible for facilitating the PI Planning event and ensuring it runs effectively?

  1. Business Owner
  2. Release Train Engineer Correct answer.
  3. System Architect
  4. Product Management

Explanation

The Release Train Engineer facilitates PI Planning and manages the event logistics and flow. Product Management, Business Owners, and architects contribute content rather than facilitation.

Question 40PI Planning Preparation (17-19%)

In a SAFe solution train, what is the main purpose of Pre-PI Planning?

  1. To assign business value to individual team PI objectives
  2. To finalize each team's iteration plan for the first sprint of the upcoming PI
  3. To align ARTs and suppliers on a shared solution plan before ART planning Correct answer.
  4. To conduct the system demo for the previous PI

Explanation

Pre-PI Planning aligns multiple ARTs and suppliers on a shared solution vision and plan before the individual ART PI Planning events. It coordinates dependencies and intent at the solution level.

Question 41PI Planning Preparation (17-19%)

What happens during the management review at PI Planning?

  1. The RTE assigns individual performance ratings and development goals for each team member
  2. Business Owners finalize the annual budget
  3. Teams present plans so leadership can resolve issues and adjust scope Correct answer.
  4. Teams vote on which features to remove from the roadmap

Explanation

In the management review, teams present their draft plans so leadership can resolve cross-team issues, adjust scope, and approve the plan. This keeps the plan aligned with business priorities.

Question 42PI Planning Preparation (17-19%)

Which item is part of the planning context presented to teams at PI Planning?

  1. Individual employee development plans
  2. The company's stock price forecast
  3. The detailed sprint backlog for each team
  4. Known constraints and relevant business context Correct answer.

Explanation

Planning context includes known constraints, assumptions, and relevant business information that shape how teams plan. It helps teams make informed trade-offs during breakouts.

Question 43PI Planning Preparation (17-19%)

Which of the following is an example of logistics readiness for PI Planning?

  1. A prioritized top 10 features list
  2. A completed architectural runway assessment and design review
  3. Draft PI objectives from each team
  4. A venue, collaboration tools, and communication plan Correct answer.

Explanation

Logistics readiness covers the practical arrangements for the event, including the venue, collaboration tools, and communication plan. Content items such as features and architecture belong to content readiness.

Question 44PI Planning Preparation (17-19%)

Which sequence best reflects the typical Day 1 agenda of PI Planning?

  1. Business context, vision, planning context, team breakouts, draft review Correct answer.
  2. Confidence vote, problem solving, team breakouts, vision presentation
  3. A system demo, Inspect and Adapt, team breakouts, management review
  4. Team breakouts, business context, final plan review, confidence vote

Explanation

Day 1 typically opens with business context and the product and architectural vision, followed by planning context and team breakouts. Teams then present draft plans for review and problem solving.

Question 45PI Planning Preparation (17-19%)

Which set of inputs is most important for teams to plan effectively at PI Planning?

  1. Annual budget, sales targets, and marketing campaign plans
  2. Individual performance goals and HR policies
  3. Vendor contracts and procurement schedules
  4. Vision, roadmap, top features, and architectural runway Correct answer.

Explanation

Teams need the product vision, roadmap, prioritized features, and architectural runway to create meaningful plans. These inputs define the intended value and technical direction for the PI.

Question 46PI Planning Preparation (17-19%)

How do PI objectives differ from features on the ART backlog?

  1. PI objectives are technical tasks, while features are business capabilities
  2. PI objectives are written by Business Owners, while features are written by teams
  3. PI objectives are optional, while features are mandatory
  4. PI objectives state a team's goals for the PI; features are planned value items Correct answer.

Explanation

PI objectives summarize the business and technical goals a team commits to for the PI. Features describe planned value that teams break down into stories for delivery.

Question 47PI Planning Preparation (17-19%)

In a standard SAFe configuration, how many development iterations are typically in a PI?

  1. One to two
  2. Four to five, plus an IP iteration Correct answer.
  3. Ten to twelve
  4. Exactly three

Explanation

A PI usually contains four or five development iterations followed by an Innovation and Planning iteration. This cadence balances delivery with innovation and buffer time.

Question 48PI Planning Preparation (17-19%)

What should Business Owners do to prepare for PI Planning?

  1. Understand the vision and top features and be ready to give feedback Correct answer.
  2. Facilitate the team breakouts
  3. Write all the user stories for the teams and estimate each story in points
  4. Finalize the program board before the event

Explanation

Business Owners prepare by understanding the vision and top features so they can provide context, assign business value, and give feedback on team plans. They do not write stories or facilitate breakouts.

Question 49PI Planning Preparation (17-19%)

When should teams draft their PI objectives during PI Planning?

  1. During team breakouts, after the vision and planning context Correct answer.
  2. Only after the confidence vote is completed
  3. During the Inspect and Adapt workshop
  4. Before the event, and they are not changed during planning

Explanation

Teams draft PI objectives during team breakouts after receiving the vision and planning context. This ensures the objectives reflect the shared direction and the team's own plan.

Question 50PI Planning Preparation (17-19%)

How does Product Management typically prioritize the top features for PI Planning?

  1. By the seniority of the requesting stakeholder
  2. By alphabetical order of feature names
  3. By using Weighted Shortest Job First (WSJF) Correct answer.
  4. By the number of story points estimated by teams

Explanation

Product Management uses Weighted Shortest Job First to prioritize features based on cost of delay and job size. This produces an economically sequenced top features list for planning.