Scaled Agile · Free Practice Questions · Last reviewed May 2026
30real exam-style questions organised by domain, each with the correct answer highlighted and a plain-English explanation of why it's right — and why the others are wrong.
During an Iteration, the team realizes a high-priority story is larger than expected and cannot be completed by the deadline. What is the most effective way for the Product Owner to handle this?
Instruct the team to work overtime to complete the story as originally planned.
Keep the story in the iteration and mark it as 'in progress' at the end of the iteration.
Collaborate with the team to split the story into smaller, manageable increments and reprioritize.
Splitting stories is the standard approach to manage scope and ensure incremental value delivery. By focusing on smaller, independent pieces of functionality, the PO ensures the team can still demonstrate progress and value, adhering to the principle of iterative delivery while maintaining the ability to pivot if necessary.
Remove the story from the iteration and add it to the bottom of the Product Backlog.
Refer to the exhibit. As a PO, what does this pattern primarily suggest about the team's current iteration execution?
The team has excellent velocity and is effectively managing technical debt.
The team is successfully utilizing the 'stretch goal' mechanism to maximize value.
The iteration is suffering from scope creep and a lack of focus on completion.
Adding work mid-iteration is a clear indicator of scope creep. When combined with stagnant burndown, it reveals that the team is distracted and unable to finalize their committed stories. The PO must intervene to protect the iteration and stop the practice of adding new work mid-cycle.
The team's velocity is intentionally throttled to accommodate architectural runway.
How should a Product Owner balance the need for quality with the pressure to deliver new features during the iteration?
Prioritize new features first and address quality in the next iteration.
Ensure the Definition of Done includes quality standards and maintain that standard.
The Definition of Done is the fundamental agreement that quality is built-in. By holding the team to these standards, the PO prevents the accumulation of technical debt. This ensures that new features are robust, maintainable, and do not break existing functionality, which is critical for consistent long-term delivery.
Use the Innovation and Planning iteration to resolve all quality issues.
Reduce the scope of the iteration to allow for more testing time.
Which THREE of the following represent effective ways for the PO to support the team during Iteration Execution? (Choose three)
Shielding the team from stakeholders who want to add new work mid-iteration.
Protecting the iteration is vital for maintaining the team's commitment and velocity. The PO acts as a filter, pushing back on mid-iteration requests and helping stakeholders understand the cost of context switching. This ensures the team can maintain focus on the goals they committed to during Iteration Planning.
Attending every daily stand-up to direct the work of the team.
Providing timely feedback on story progress to enable course correction.
Feedback loops are essential in Agile. By reviewing progress early and often, the PO helps the team pivot if the implementation is diverging from the desired outcome. This reduces waste, prevents rework, and ensures that the final deliverable at the end of the iteration aligns with stakeholders' expectations.
Managing the team's task board to ensure all tasks are assigned.
Working with other POs to resolve cross-team dependencies.
Dependencies are common in large systems. The PO must collaborate with peers to resolve blockers that lie outside their team's control. By proactively addressing these issues, the PO removes impediments to flow, ensuring that the team can deliver their commitments without being stalled by external constraints or teams.
What is the primary purpose of the Iteration Review in SAFe?
To identify process improvements for the next iteration.
To demonstrate the progress made and gather stakeholder feedback.
The Review is specifically designed for demonstrating the increment to stakeholders to gather feedback. This validates that the value delivered matches expectations and provides the PO with necessary information to adjust the backlog priorities for the next iteration, ensuring the team stays aligned with the overall PI objectives.
To sign off on the velocity achieved in the current iteration.
To re-plan the entire remaining PI based on the team's performance.
Refer to the exhibit. How should the PO interpret this drop in velocity for future planning?
Permanently lower the team's capacity for all future iterations.
Ignore the I4 data as an anomaly and use the average of I1-I3.
Discuss the impact with the team and adjust the capacity plan accordingly.
The PO must involve the team in understanding the root cause of the velocity dip. This collaborative approach allows for an informed decision on capacity planning for the next PI, acknowledging the transition while preparing for a return to higher productivity as the team integrates new members.
Request the Scrum Master to force the team to return to a velocity of 30.
Want more Iteration Execution practice?
Practice this domainA Product Owner notices the team is consistently failing to meet their Sprint Goals because stakeholders introduce new, urgent requirements mid-sprint. How should the Product Owner address this?
Accept the changes to maintain stakeholder satisfaction.
Ask the Scrum Master to force the stakeholders to stop.
Decline the new requests and discuss adding them to the backlog for the next sprint.
Protecting the team's focus during the sprint is a primary PO responsibility. By deferring requests, the PO ensures the team completes their current commitments, which builds trust and maintains focus. This disciplined approach facilitates better planning and allows the team to deliver high-quality, stable software increments without constant, unplanned context switching.
Split the sprint into two mini-sprints to accommodate the changes.
Based on the exhibit, which item should the Product Owner prioritize first to maximize economic value?
Feature Y because it is smaller and finishes faster.
Feature X because it has a higher Cost of Delay.
Prioritizing by Cost of Delay ensures that the most impactful work is completed first. With a CoD of 20 per sprint, failing to deliver Feature X early results in significant economic loss. This approach aligns with the SAFe principle of delivering value in the shortest sustainable lead time by prioritizing economic outcomes.
Both features simultaneously to distribute team capacity.
Neither feature, until more capacity is added to the ART.
Which primary responsibility does a Product Owner hold during PI Planning?
Writing the system architecture documentation.
Defining the team's PI Objectives and technical tasks.
Prioritizing the Team Backlog and collaborating on PI Objectives.
The PO is responsible for the Team Backlog, ensuring it is prioritized based on business value and stakeholder needs. During PI Planning, they must collaborate with the team to set realistic, achievable PI Objectives. This synchronization is essential for the ART to deliver value incrementally and predictably throughout the Program Increment period.
Managing the overall budget for the entire ART.
A Product Manager is creating the Program Backlog. Which input should they primarily use to derive the features?
Direct requests from individual developers.
Strategic themes and the current product vision.
Strategic themes provide the context for all development work, and the product vision defines the future state. Using these as primary inputs ensures that all features align with company strategy. This approach keeps the ART focused on delivering high-value outcomes that move the product closer to its long-term goals.
The latest industry news and current competitor marketing.
Bug reports from the support team.
Which TWO of the following are responsibilities of Product Management in SAFe?
Managing the daily stand-up meetings for the ART.
Defining the product vision and roadmap.
Defining the product vision and roadmap is a core competency of Product Management. It provides the necessary direction for the entire ART. Without a clear vision and roadmap, the team lacks the context needed to make informed prioritization decisions, leading to a disconnected and less effective development process over time.
Prioritizing the Program Backlog.
Product Management owns the Program Backlog and is responsible for its prioritization. This ensures that the work flowing into the ART is aligned with business needs and strategic goals. Proper prioritization allows the ART to focus its limited capacity on the features that will deliver the most significant business value.
Writing user stories for the team backlog.
Approving technical designs for all features.
When should the Product Owner refine the team backlog?
Only during the final day of the iteration.
Continuously throughout the iteration.
Continuous refinement allows the team to digest requirements over time. It promotes collaboration between the PO and the team, ensuring that user stories are clear, valuable, and testable before the next planning cycle. This consistent cadence minimizes surprises and helps the team maintain a high level of preparedness for future sprints.
Only during Sprint Planning.
Whenever the Scrum Master requests it.
Want more Product Owner and Product Management Roles practice?
Practice this domainDuring PI Planning, a Business Owner expresses concern that the proposed PI Objectives do not align with the strategic intent for the next quarter. What is the most effective leadership action to resolve this?
Instruct the teams to continue planning and address the strategic alignment concerns during the first System Demo.
Direct the Release Train Engineer to unilaterally modify the team objectives to match the Business Owner's vision.
Facilitate a discussion between the Business Owner and the teams to adjust objectives based on realistic capacity and value.
Facilitating direct communication allows Business Owners to clarify strategic intent while teams provide feedback on technical constraints and capacity. This collaborative negotiation ensures that final objectives are both strategically aligned and realistically achievable, fostering a shared commitment to the goals defined for the Program Increment.
Ask the System Architect to rewrite the objectives to ensure they meet the technical standards of the enterprise.
Which TWO of the following leadership behaviors effectively support the PI Planning process? (Choose two)
Dictate the specific task-level assignments for each team member to ensure maximum resource utilization.
Provide clear strategic intent and allow teams to determine the best approach to achieve business objectives.
Providing strategic context empowers teams to make local decisions that align with the broader organizational goals. When leaders focus on the 'what' and 'why' rather than the 'how,' teams utilize their technical expertise to develop more innovative and effective solutions, leading to higher-quality outcomes and increased engagement.
Minimize the interaction between Business Owners and teams to ensure the planning stays on schedule.
Actively identify and help remove impediments that arise during the planning process.
Servant leaders must be present and available during PI Planning to help resolve cross-team dependencies and resource constraints. By proactively addressing these blockers, leaders demonstrate support for the teams and ensure that planning can proceed efficiently, preventing teams from becoming discouraged by issues outside their control.
Insist that every team plan for 100% of their capacity to guarantee maximum throughput.
Refer to the exhibit. Given the high number of blockers and low resolution rate, what is the primary responsibility of Leadership during PI Planning to address this?
Extend the PI Planning event by two days to allow teams more time to resolve the dependencies themselves.
Facilitate cross-team negotiations to re-prioritize or remove the conflicting dependencies.
Leadership has the authority to make decisions regarding scope and priority that transcend team boundaries. By facilitating these negotiations, they can help resolve blockers that teams are unable to solve, ensuring that the Program Board reflects a realistic plan that teams can actually commit to completing.
Ignore the blockers and proceed with the confidence vote, as teams are responsible for their own success.
Report the lack of progress to the PMO to initiate corrective action after the PI Planning event.
A team has identified a major dependency on an external supplier that is not committed to the PI plan. How should the Release Train Engineer (RTE) or leader address this?
Ask the team to remove the dependency from the plan and work around it independently.
Escalate the dependency to the necessary management levels to negotiate a firm commitment.
Escalation is a core leadership function when teams are blocked by external factors. By involving management, the RTE can leverage organizational relationships to secure the necessary commitment from the supplier, ensuring the team's plan is grounded in reality rather than wishful thinking regarding external resource availability.
Instruct the team to mark the objective as 'at risk' and continue planning as if the supplier will deliver.
Cancel the planned feature to maintain the team's velocity and focus on internal work.
What is the main goal of the Management Review and Problem Solving session during PI Planning?
To finalize the release dates for the next three years of the product roadmap.
To adjust the program scope, people, and resources to ensure the PI plan is achievable.
The session allows leaders to make the necessary structural adjustments to ensure success. By addressing capacity and resource gaps or refining scope, leadership ensures the plan is realistic, which is essential for maintaining the commitment and morale of the teams who will execute the work.
To celebrate the team's progress and distribute rewards for the previous PI's performance.
To conduct the confidence vote for all teams on the Agile Release Train.
A Business Owner is consistently pushing teams to commit to more features than their calculated capacity allows. What is the best way to handle this situation?
Agree to the extra features but plan for mandatory overtime throughout the entire PI.
Use capacity and velocity data to show the Business Owner that the plan is unrealistic.
Data-driven conversations are the most effective way to manage expectations. By showing the Business Owner clear evidence that the team cannot deliver the requested amount based on past performance, the leader can facilitate a discussion about which items should be prioritized and which should be deferred.
Let the teams decide if they want to accept the extra features or not.
Ignore the capacity planning and hope the team's productivity increases during the PI.
Want more Leadership for PI Planning practice?
Practice this domainDuring PI execution, a team realizes their current velocity will not allow them to complete all committed features. What is the most appropriate action for the Product Owner?
Ask the team to work overtime to ensure all features are finished as originally committed.
Increase the story points for all remaining items to make the velocity look better.
Reprioritize the remaining backlog with the team to focus on the highest-value features.
Collaborating with the team to re-evaluate the backlog allows for scope adjustment based on current capacity. By focusing on the highest-value items, the PO ensures that the most critical business needs are met, even if lower-priority items are deferred. This transparent approach maintains alignment with stakeholder expectations during the execution phase.
Instruct the team to stop updating the Kanban board so the progress appears complete.
Which TWO of the following are primary responsibilities of the Product Owner during PI Execution to ensure synchronization?
Attend the ART Sync and Coach Sync meetings to address cross-team dependencies.
The ART Sync is essential for alignment and identifying cross-team dependencies that could impact delivery. POs play a vital role here by communicating their team's progress and flagging potential blockers. This proactive communication ensures that the entire program remains synchronized and that issues are resolved before they become major impediments.
Rewrite all user stories for the next PI during the current sprint.
Manage the Team Backlog and ensure stories are ready for implementation.
The PO is solely responsible for managing the team backlog and ensuring that stories meet the Definition of Ready. By keeping stories well-defined and prioritized, the PO enables the team to maintain a steady flow of work. This ensures that the team can focus on execution without being stalled by requirements.
Directly manage the daily stand-up and assign tasks to developers.
Decide the architectural runway for the entire Program Increment.
Refer to the exhibit. The system log indicates a dependency blocker for 'Team_Alpha_API_Integration'. What is the most effective way for the PO to handle this blocker?
Wait until the next PI Planning to discuss this blocker with the other team.
Escalate the issue through the ART Sync to get cross-team support.
The ART Sync provides the forum for POs and Scrum Masters to escalate blockers that cannot be resolved within the team. Raising the issue here ensures visibility and accountability across the entire Agile Release Train. It is the appropriate venue for cross-team coordination to remove impediments that hinder PI objectives.
Tell the developers to ignore the API and build a temporary mock service.
Contact the Team Alpha PO directly to demand a fix.
During a System Demo, stakeholders provide feedback that a feature does not meet current market needs. How should the Product Manager respond?
Defend the original feature requirements as they were agreed upon at the start of the PI.
Acknowledge the feedback and work with the team to reprioritize the backlog accordingly.
Reprioritizing the backlog based on stakeholder feedback is the definition of agility. The PM's role is to ensure the product delivered provides the most value, which requires constant re-evaluation against market needs. This ensures that the team's future work is aligned with the most current understanding of customer requirements.
Ignore the feedback because the team has already spent too much effort on the feature.
Ask the stakeholders to wait until the final PI demo to see the completed feature.
What is the primary purpose of the System Demo during PI Execution?
To review individual team progress and hold them accountable for their velocity.
To demonstrate the progress of the integrated solution to stakeholders and gather feedback.
The System Demo is the key event for stakeholders to see the integrated work and provide feedback. This feedback loop is essential for confirming that the team is building the right thing. It allows for adjustments to the vision or backlog based on what the stakeholders observe in the working system.
To approve the final release of the software to the production environment.
To celebrate the team's accomplishments and provide recognition to developers.
If a team's velocity is consistently lower than planned, what should the Product Owner do first?
Reduce the scope of the remaining PI features.
Work with the team to identify root causes and potential improvements.
Understanding the root cause is the necessary first step to solving performance issues. Whether the issue is technical, process-related, or environmental, the PO and the team need a clear picture to address it effectively. This collaborative approach fosters transparency and empowers the team to own their process and performance improvements.
Report the team to leadership for not meeting their commitments.
Increase the team's capacity by hiring more developers.
Want more PI Execution practice?
Practice this domainA Product Manager is preparing for PI Planning and notices that the Vision is not yet finalized. What is the most effective approach to ensure PI Planning success?
Proceed with planning using the previous PI's Vision to avoid delaying the event.
Delay PI Planning until the executive leadership completes the strategic theme definition.
Collaborate with stakeholders to synthesize the current Vision before the event starts.
Synthesizing the Vision ensures that all teams understand the future state of the solution before planning begins. This collaborative effort aligns Product Management and stakeholders, providing a solid foundation for the Program Backlog. Having a clear Vision allows teams to draft meaningful PI Objectives that reflect the enterprise's goals.
Ask the Release Train Engineer to create the Vision on behalf of the Product team.
Which TWO of the following activities are essential for the Product Manager during the preparation phase for PI Planning?
Defining and refining the top Program Backlog features.
Refining top features is critical because teams need actionable items to plan their capacity. By ensuring features are ready and prioritized, the Product Manager minimizes wasted time during the event. High-quality features allow for accurate estimation and dependency identification, which are core components of successful Program Increment planning.
Selecting the specific technical tasks for every team.
Ensuring the Vision and Roadmap are updated.
An updated Vision and Roadmap provide the necessary context for the ART to prioritize work effectively. These documents serve as the foundation for the entire planning process, guiding teams in creating objectives that align with the enterprise's long-term goals. Without them, planning lacks the strategic focus required for success.
Assigning story points to every feature in the backlog.
Conducting all team-level sprint demos.
Which role is primarily responsible for the management and prioritization of the Program Backlog prior to PI Planning?
Scrum Master
Release Train Engineer
Product Manager
Product Managers own the Program Backlog and are responsible for its content and prioritization. They ensure that the features align with the vision and strategic themes. By managing the backlog, they provide the necessary direction for the teams, ensuring that the work delivered during the PI adds significant business value.
System Architect
What is the primary purpose of the 'Draft Plan' review during the first day of PI Planning?
To finalize the exact technical implementation details for every team.
To identify dependencies and get feedback from stakeholders.
This review session is intended to surface dependencies between teams and allow Business Owners to weigh in on the proposed scope. Feedback at this stage is essential for correcting the course and ensuring that the final plan is aligned with the organizational strategy and feasible given the existing constraints.
To formally sign off on the team's final PI commitment.
To re-prioritize the entire Program Backlog for the next two increments.
During PI Planning preparation, a Product Manager realizes that several features lack clear acceptance criteria. What is the best course of action?
Proceed with planning and let the teams define criteria during the first iteration.
Work with the teams and stakeholders to define the criteria before the event.
Collaboration ensures that everyone has a shared understanding of what constitutes a successfully completed feature. Defining these criteria before PI Planning allows teams to plan with confidence and reduces the likelihood of misunderstandings during development. It is a proactive step that significantly improves the quality of the planning output.
Use the previous PI's criteria for these features to save time.
Remove the features from the backlog until criteria are established.
Which document is most important for the Product Manager to provide to the ART to ensure alignment during PI Planning?
The team's velocity report.
The detailed unit test plans.
The Vision document.
The Vision document is the primary tool for aligning the ART on the strategic direction. It helps teams understand the value they are delivering and how their work contributes to the bigger picture. Without a clear vision, teams may optimize for their own goals rather than the success of the program.
The meeting minutes from the last stakeholder review.
Want more PI Planning Preparation practice?
Practice this domainThe POPM exam has 60–90 questions and must be completed in 120 minutes. The passing score is 700/1000.
Scenario-based questions covering exam objectives with detailed answer explanations.
The exam covers 5 domains: Iteration Execution, Product Owner and Product Management Roles, Leadership for PI Planning, PI Execution, PI Planning Preparation. Questions are weighted by domain — higher-weight domains appear more on your actual exam.
No. These are original exam-style practice questions written against the official Scaled Agile POPM exam objectives. They are not copied from the real exam. Courseiva focuses on genuine understanding, not memorisation of braindumps.
Courseiva tracks your accuracy per domain and routes you toward weak areas automatically. Free, no account required.