PSPO I

Free PSPO I practice questions

10 questions from our PSPO I practice tests, each with the correct answer and a written explanation. Read them with the answers shown, or switch to quiz mode and answer first.

Back to the PSPO I practice exams

Question 1 of 10, Understanding and Applying the Scrum Framework

A newly appointed Product Owner asks what Scrum is founded on. According to the Scrum Guide, which two foundations does Scrum rest on?

  1. AServant leadership and team chartering
  2. BPhase-gate planning
  3. CIterative design and detailed upfront requirements analysis
  4. DEmpiricism and lean thinking Correct answer

Answer and explanation: The Scrum Guide states that Scrum is founded on empiricism (knowledge comes from experience and decisions based on what is observed) and lean thinking (reducing waste and focusing on essentials). Predictive planning with phase gates is the opposite of empirical control. Servant leadership describes how the Scrum Master serves, not the foundation of the framework, and detailed upfront requirements analysis contradicts the emergent nature of the Product Backlog.

Question 2 of 10, Understanding and Applying the Scrum Framework

A Product Owner hesitates to tell stakeholders that a much-requested feature showed no impact in an experiment and should be removed. Which Scrum value most directly supports sharing this news?

  1. AFocus, to keep attention on the Sprint's selected work
  2. BCommitment, to deliver every feature that was promised
  3. CCourage, to do the right thing on tough problems Correct answer
  4. DRespect, to honour the stakeholders' original request

Answer and explanation: The Scrum Guide describes courage as having the courage to do the right thing and to work on tough problems, which includes giving uncomfortable evidence-based news. Focus concerns attention on the work of the Sprint, not difficult conversations. Respect matters but does not mean protecting a request that the evidence contradicts, and commitment is about the team's goals and supporting each other, not delivering every promised feature regardless of value.

Question 3 of 10, Understanding and Applying the Scrum Framework

Besides inspecting the Increment, what should the Product Owner make sure is discussed with stakeholders at the Sprint Review?

  1. AThe detailed task breakdown the Developers used during the Sprint
  2. BProgress toward the Product Goal and what has changed in the environment Correct answer
  3. CWhether the Scrum Master followed the timeboxes for all of the events
  4. DEach Developer's individual contribution to the items completed in the Sprint

Answer and explanation: During the Sprint Review the Scrum Team presents results to key stakeholders, progress toward the Product Goal is discussed, and attendees review what has changed in their environment to decide what to do next. Individual contributions are not the focus because accountability is shared. The task breakdown is the Developers' internal plan, and timebox adherence is a topic for the Scrum Team's Retrospective rather than for stakeholders.

Question 4 of 10, Understanding and Applying the Scrum Framework

A Product Owner proposes merging two Scrum Teams into a single team of fifteen people to "reduce coordination". What guidance does the Scrum Guide offer?

  1. ALarger teams are always preferred, because more Developers increase the Increment's value in each Sprint
  2. BTeams are typically ten or fewer people; large teams should consider splitting into cohesive teams Correct answer
  3. CA team of fifteen is fine provided it has two Scrum Masters to share the facilitation of the events
  4. DThe Scrum Guide sets no guidance on team size, so the decision rests purely with the Product Owner

Answer and explanation: The guide states that the Scrum Team is typically ten or fewer people, small enough to remain nimble and large enough to complete significant work; teams that become too large should consider reorganizing into multiple cohesive Scrum Teams sharing the same Product Goal, Product Backlog and Product Owner. More people does not automatically mean more value, the guide does give size guidance, and a Scrum Team has one Scrum Master.

Question 5 of 10, Developing People and Teams

An organization wants to scale a product from one Scrum Team to four. Management proposes giving each team its own Product Owner and Product Backlog for one component. What should the Product Owner of the product advise?

  1. AGive each team its own Product Owner but share a single Definition of Done so that integration remains possible
  2. BCreate a chief Product Owner who approves the four separate Product Backlogs before each team's Sprint Planning
  3. CAccept the proposal but have the four Product Owners agree on a combined ordering at a monthly portfolio meeting
  4. DKeep one Product Owner, one Product Backlog and one Product Goal for the product, with all four teams working from it Correct answer

Answer and explanation: When multiple Scrum Teams work on the same product, the Scrum Guide says they share the same Product Goal, Product Backlog and Product Owner. Several Product Owners negotiating a combined order dilutes accountability for value. A shared Definition of Done is required but does not justify separate backlogs, and a chief approver over separate backlogs is still a committee approach that fragments the product.

Question 6 of 10, Product Vision, Value and Business Strategy

A sponsor asks the Product Owner to fix scope, budget and date for the next twelve months. The market is changing quickly. What is the most valuable approach for the Product Owner?

  1. AAgree on budget and timeframe, and keep scope flexible by reordering the Product Backlog as evidence emerges Correct answer
  2. BFix all three constraints, then report variance at every Sprint Review so the sponsor can approve change requests
  3. CRefuse to make any commitment until the Developers have estimated the complete Product Backlog in detail
  4. DFix scope and date, and let the Developers adjust quality where needed to keep the budget within the agreed limit

Answer and explanation: In complex, fast-changing markets the most valuable lever is scope: with time and cost fixed, the Product Owner maximizes value by continuously reordering based on evidence. Fixing all three turns the work into change-request management and reduces adaptability. Waiting for complete detailed estimates delays value and assumes predictability that does not exist, and trading quality is not acceptable because quality does not decrease in Scrum.

Question 7 of 10, Product Vision, Value and Business Strategy

A product's customer satisfaction is high, but new features take months to reach users because most of the Developers' capacity goes to defect fixing and manual regression testing. Which Evidence-Based Management Key Value Area is most clearly under threat?

  1. ACustomer Satisfaction Index
  2. BCurrent Value
  3. CUnrealized Value
  4. DAbility to Innovate Correct answer

Answer and explanation: Ability to Innovate measures how effectively the organization can deliver new capabilities; high defect load, technical debt and manual testing consume capacity that could go to innovation. Current Value is currently healthy given the high satisfaction. Unrealized Value is about the gap to potential value rather than the capability constraint, and a Customer Satisfaction Index is an example measure, not a Key Value Area.

Question 8 of 10, Product Backlog Management

A Product Owner orders the Product Backlog strictly by the business value each stakeholder assigns. The Developers point out that a risky technical item could invalidate many of the high-value items if it fails. What should the Product Owner do?

  1. ALet the Developers move the item to the top themselves, since technical items are outside the Product Owner's ordering
  2. BCreate a separate technical backlog managed by the Developers so that the Product Backlog itself stays value-only
  3. CKeep strict value ordering, because the Product Owner must never let technical concerns influence the Product Backlog
  4. DWeigh risk, dependencies and learning alongside value, and possibly order the risky item earlier to reduce uncertainty Correct answer

Answer and explanation: Ordering is the Product Owner's decision, and good ordering considers value together with risk, dependencies and the need to learn; reducing a risk early can protect a lot of value. Ignoring technical input leads to costly surprises. Developers can advise but the Product Owner remains accountable for ordering, and Scrum has a single Product Backlog for the product, so a separate technical backlog hides work and reduces transparency.

Question 9 of 10, Product Backlog Management. Choose 2.

A Product Owner wants to ensure the Product Backlog reflects both customer needs and the work required to keep the product healthy. Which items belong there? (Choose two.)

  1. AWork to reduce technical debt that slows delivery Correct answer
  2. BExperiments to validate a new customer hypothesis Correct answer
  3. CThe minutes of the last Sprint Retrospective
  4. DThe Developers' daily task list for the current Sprint
  5. EThe Scrum Team's working agreement on core hours

Answer and explanation: The Product Backlog contains everything needed to improve the product, which includes technical debt reduction and experiments as well as features and fixes. The daily task plan is part of the Sprint Backlog. Working agreements and Retrospective notes concern how the team works rather than product work, although specific improvements may be added to the Sprint Backlog.

Question 10 of 10, Stakeholders, Customers and Release Planning

A customer advisory group tells the Product Owner that a new reporting feature is confusing. What should the Product Owner do with this feedback?

  1. AStore it until the end of the year, when all customer feedback is analysed in one batch
  2. BPass it to the Developers and ask them to fix the feature immediately, skipping Sprint Planning
  3. CBring it into the Product Backlog and the Sprint Review so the team can adapt Correct answer
  4. DIgnore it, because only feedback from paying customers in the Sprint Review counts as evidence

Answer and explanation: Customer feedback is evidence that should shape the Product Backlog and the discussion at the Sprint Review so the Scrum Team can adapt. Holding feedback for a year delays learning. Pushing work directly to the Developers bypasses ordering and may endanger the Sprint Goal, and valuable feedback can come from any users, not only from paying customers at the review.