I85PREP
⌘ K
CSPO study materials
CSPO study resources

CSPO practice questions

One question at a time. Build your CSPO understanding.

First 50 of 199 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 1Scrum Foundations

In Scrum, what is the primary purpose of a Sprint Retrospective?

  1. To decide which Product Backlog items will be built in the next Sprint
  2. To refine and reorder the Product Backlog before the next Sprint
  3. To inspect how the last Sprint went and identify improvements for the next one Correct answer.
  4. To demonstrate completed work to stakeholders and gather feedback

Explanation

The Sprint Retrospective is the event where the Scrum Team inspects how the last Sprint went regarding individuals, interactions, processes, tools, and their Definition of Done. The team then identifies the most helpful changes to improve its effectiveness. Its focus is on the team's way of working, not on product demonstration or backlog selection.

Question 2Scrum Foundations

Which statement best describes the Scrum Team's structure?

  1. It is led by a project manager who assigns tasks to individual developers
  2. It is split into a separate testing team and a separate development team
  3. It reports to a steering committee that approves each Sprint's scope
  4. It is cross-functional and self-managing, with no sub-teams or hierarchy Correct answer.

Explanation

The Scrum Team is a small, cross-functional, self-managing group of people who collectively have all skills needed to create value each Sprint. It contains one Scrum Master, one Product Owner, and Developers, and has no sub-teams or hierarchies. This structure concentrates accountability in one cohesive unit rather than distributing it across separate roles or committees.

Question 3Scrum Foundations

What is the timebox for Sprint Planning in a one-month Sprint?

  1. A maximum of two hours
  2. A maximum of one hour
  3. A maximum of eight hours Correct answer.
  4. A maximum of four hours

Explanation

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints the event is usually shorter, scaling proportionally. The timebox ensures the team commits sufficient time to plan without letting planning consume the whole Sprint.

Question 4Scrum Foundations

What does the Definition of Done provide for the Scrum Team?

  1. A contractual agreement with the customer about delivery dates
  2. A shared description of the state the Increment must reach to be considered complete Correct answer.
  3. A schedule of code reviews assigned by the Scrum Master
  4. A list of every task each Developer must finish before the Sprint ends

Explanation

The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. Work cannot be considered part of an Increment unless it meets this definition. It creates a shared understanding of completeness across the whole Scrum Team.

Question 5Scrum Foundations

Who is accountable for maximizing the value of the product resulting from the work of the Scrum Team?

  1. The Scrum Master
  2. The Developers
  3. The Product Owner Correct answer.
  4. The stakeholders

Explanation

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. This accountability is carried out by managing the Product Backlog effectively. It is a single-person accountability rather than a shared committee responsibility.

Question 6Scrum Foundations

What is the maximum duration of the Daily Scrum?

  1. One hour
  2. Fifteen minutes Correct answer.
  3. Two hours
  4. Thirty minutes

Explanation

The Daily Scrum is timeboxed to fifteen minutes for every Sprint, regardless of Sprint length. It is a short, focused event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Keeping it to fifteen minutes protects the team's focus and time.

Question 7Scrum Foundations

Which of the following is one of the five Scrum values?

  1. Escalation
  2. Velocity
  3. Documentation
  4. Commitment Correct answer.

Explanation

The five Scrum values are commitment, focus, openness, respect, and courage. Commitment means the team dedicates itself to achieving its goals and supporting one another. The other listed items are not Scrum values and are not part of the value framework.

Question 8Scrum Foundations

What are the three artifacts defined by Scrum?

  1. Product Backlog, Sprint Backlog, and Increment Correct answer.
  2. Product Backlog, Increment, and Release Plan
  3. Product Backlog, Sprint Backlog, and Burndown Chart
  4. Sprint Backlog, Increment, and Definition of Done

Explanation

Scrum defines three artifacts: the Product Backlog, the Sprint Backlog, and the Increment. Each artifact represents work or value and has a commitment attached to it. Other charts, plans, and documents teams use are not Scrum artifacts.

Question 9Scrum Foundations

During the Sprint Review, the Scrum Team and stakeholders collaborate to do what?

  1. Approve the budget for the next quarter's development
  2. Negotiate individual salaries and performance ratings
  3. Inspect the Increment and adapt the Product Backlog to maximize value Correct answer.
  4. Finalize the Definition of Done for the organization

Explanation

The Sprint Review is a working session where the Scrum Team presents the results of its work to key stakeholders and progress toward the Product Goal is discussed. Participants inspect the Increment and collaborate on what to do next, adapting the Product Backlog. It is about inspecting product progress and deciding future direction.

Question 10Scrum Foundations

A team is midway through a Sprint and discovers it cannot meet the Sprint Goal. What does Scrum recommend?

  1. The Developers and Product Owner collaborate to adjust the Sprint Backlog scope while preserving the Sprint Goal Correct answer.
  2. The Product Owner adds new high-priority items to compensate for the shortfall
  3. The Scrum Master cancels the Sprint immediately without consulting anyone
  4. The Developers work overtime to force completion of all original items

Explanation

If the work turns out to be different than expected, the Developers collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint. The Sprint Goal is preserved and scope is clarified and renegotiated as more is learned. Only the Product Owner has the authority to cancel a Sprint, and only if the Sprint Goal becomes obsolete.

Question 11Scrum Foundations

What is the commitment associated with the Product Backlog?

  1. The Definition of Done
  2. The Increment Goal
  3. The Sprint Goal
  4. The Product Goal Correct answer.

Explanation

The Product Goal describes a future state of the product that serves as a target for the Scrum Team to plan against, and it is the commitment for the Product Backlog. The Sprint Goal is the commitment for the Sprint Backlog, and the Definition of Done is the commitment for the Increment. Each artifact has exactly one commitment attached to it.

Question 12Scrum Foundations

Why is the Daily Scrum held at the same time and place every working day?

  1. To replace the need for Sprint Planning entirely
  2. To allow managers to monitor attendance each morning
  3. To reduce complexity and eliminate the need for additional meetings Correct answer.
  4. To satisfy a legal requirement for daily team standups

Explanation

The Daily Scrum is held at the same time and place every working day of the Sprint to reduce complexity. This consistency removes the overhead of coordinating when and where to meet each day. It is a simplification practice, not a legal or managerial requirement.

Question 13Scrum Foundations

Who is responsible for ordering the items in the Product Backlog?

  1. The Product Owner Correct answer.
  2. The Developers as a group
  3. The Scrum Master
  4. The most senior stakeholder

Explanation

The Product Owner is accountable for effective Product Backlog management, which includes developing and explicitly communicating the Product Goal and ordering Product Backlog items. The Product Owner may delegate the work but remains accountable. Ordering is a single-accountability decision to keep priorities coherent.

Question 14Scrum Foundations

What best characterizes the Sprint Backlog?

  1. A document maintained exclusively by the Product Owner
  2. A list of all product features scheduled for the next release
  3. A plan by and for the Developers consisting of the Sprint Goal, selected items, and a plan for delivering them Correct answer.
  4. A fixed contract of tasks that cannot change once the Sprint begins

Explanation

The Sprint Backlog is composed of the Sprint Goal, the Product Backlog items selected for the Sprint, and the actionable plan for delivering them. It is a highly visible, real-time picture of the work the Developers plan to accomplish. It is created by and for the Developers and is updated throughout the Sprint as more is learned.

Question 15Scrum Foundations

A Scrum Team wants to improve its effectiveness. Which action aligns with the Scrum Master's accountability?

  1. Coaching the team in self-management and helping it focus on creating high-value Increments Correct answer.
  2. Setting the team's velocity target for the next Sprint
  3. Assigning individual tasks to each Developer at the start of the Sprint
  4. Approving or rejecting Product Backlog items before they enter the Sprint

Explanation

The Scrum Master serves the Scrum Team by coaching the members in self-management and cross-functionality and by helping them focus on creating high-value Increments. The Scrum Master is a true leader who serves the team and the organization. The role does not include assigning tasks or owning product decisions.

Question 16Scrum Foundations

What happens to the Increment at the end of each Sprint?

  1. The Increment is discarded and rebuilt in the next Sprint
  2. A usable Increment that meets the Definition of Done must be produced Correct answer.
  3. The Increment is held back until several Sprints are complete
  4. The Increment is released only after a formal change board approves it

Explanation

At the end of a Sprint, a usable Increment must be produced, and it must meet the Definition of Done. If the Definition of Done is not met, the work cannot be released as an Increment. Multiple Increments may be produced within a Sprint, and the Increment is additive to prior increments.

Question 17Scrum Foundations

Which statement accurately reflects the relationship between the Sprint Goal and the Sprint Backlog?

  1. The Sprint Backlog must contain only items that are unrelated to the Sprint Goal
  2. The Sprint Goal is set by stakeholders after the Sprint begins
  3. The Sprint Goal is the commitment for the Sprint Backlog and gives the Developers flexibility on the exact work Correct answer.
  4. The Sprint Goal is optional and may be skipped when the team is busy

Explanation

The Sprint Goal is the single objective for the Sprint and is the commitment attached to the Sprint Backlog. It provides flexibility by allowing the Developers to negotiate the exact scope of work while keeping the objective fixed. The Sprint Goal is created during Sprint Planning and is not optional.

Question 18Scrum Foundations

How does Scrum describe the Product Owner's authority over the Product Backlog?

  1. The Product Owner must obtain unanimous stakeholder approval for every ordering decision
  2. The Product Owner shares ordering authority equally with the Scrum Master
  3. The Product Owner is the sole person accountable, though the work may be delegated to others Correct answer.
  4. The Product Owner may only reorder items during the Sprint Review

Explanation

The Product Owner is accountable for effective Product Backlog management and is the sole person accountable for it. The Product Owner may delegate the work to others but remains accountable for the outcome. This preserves a single point of decision-making for product value.

Question 19Scrum Foundations

What is the primary focus of the Sprint Review in relation to the Product Goal?

  1. Discussing progress toward the Product Goal and adapting the Product Backlog accordingly Correct answer.
  2. Confirming that each Developer met their individual performance targets
  3. Auditing whether the team followed every Scrum rule exactly
  4. Reviewing the Scrum Master's facilitation performance

Explanation

The Sprint Review is used to inspect the outcome of the Sprint and determine future adaptations, including discussing progress toward the Product Goal. The Scrum Team presents results to stakeholders and the Product Backlog may be adjusted based on new information. The focus is on product progress and future direction, not individual performance or rule auditing.

Question 20Scrum Foundations

A newly formed Scrum Team asks which Scrum events are mandatory. What is the correct guidance?

  1. All five events are required: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective Correct answer.
  2. Events are optional and used only when the team feels they add value
  3. Only Sprint Planning and the Daily Scrum are required; the others are optional
  4. The Sprint Review and Retrospective may be combined and skipped in short Sprints

Explanation

Scrum defines five events that are used to create regularity and minimize the need for meetings not defined in Scrum: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Each event serves a specific purpose and is required. Teams may adapt how they run events but cannot simply drop them.

Question 21Scrum Foundations

Which statement best captures the concept of empiricism in Scrum?

  1. Progress should be measured mainly by hours worked
  2. Plans should be fixed at the start and followed regardless of new evidence
  3. Decisions should rely on the most senior person's opinion
  4. Knowledge comes from experience and decisions are based on what is observed Correct answer.

Explanation

Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Scrum employs an iterative, incremental approach to optimize predictability and control risk. The three pillars of empiricism are transparency, inspection, and adaptation.

Question 22Scrum Foundations

A Product Owner wants to add a high-value item to the Product Backlog in the middle of a Sprint. What does Scrum permit?

  1. The Scrum Master must approve any Product Backlog change before it is recorded
  2. The Product Backlog may be updated at any time, but the current Sprint's scope is negotiated with the Developers Correct answer.
  3. The item must be added to the current Sprint Backlog automatically
  4. The Product Backlog is frozen during a Sprint and cannot be changed until the next Sprint

Explanation

The Product Backlog is an emergent, ever-evolving list, and the Product Owner may update it at any time. However, changes that affect the current Sprint require negotiation with the Developers, since they own the Sprint Backlog and the Sprint Goal provides focus. The backlog is not frozen, but the current Sprint's commitment is protected through collaboration.

Question 23Scrum Foundations

How do the three pillars of empiricism relate to the Scrum artifacts?

  1. Artifacts are inspected only once, at the end of the project
  2. Artifacts must be transparent so that inspection is meaningful and enables adaptation Correct answer.
  3. Artifacts must be kept private so competitors cannot inspect them
  4. Artifacts replace the need for the Scrum events

Explanation

Scrum relies on transparency, inspection, and adaptation. The artifacts must be transparent so that those inspecting them have a shared understanding, which makes inspection meaningful and allows adaptation toward the goals. Without transparency, inspection can lead to flawed decisions.

Question 24Scrum Foundations

Which statement best explains why the Sprint itself is considered a container event?

  1. It is a fixed-length meeting dedicated solely to estimating backlog items
  2. It is the only event where the Product Owner speaks to stakeholders
  3. It contains all other Scrum events and holds the work needed to achieve the Product Goal Correct answer.
  4. It replaces the need for the Daily Scrum when the team is distributed

Explanation

The Sprint is a container for all other events, and each of them takes place within it. It is a fixed-length period during which the Scrum Team turns ideas into value, and it holds all the work needed to achieve the Product Goal. Sprints are the heartbeat of Scrum.

Question 25Scrum Foundations

A Scrum Team's Definition of Done differs from the organization's mandatory standard. What does Scrum require?

  1. The Scrum Master decides which standard applies for each Sprint
  2. The team's Definition of Done replaces the organizational standard entirely
  3. The team may ignore the organizational standard if it slows delivery
  4. The team's Definition of Done must include the organization's standard as a minimum Correct answer.

Explanation

If the organization has a mandatory Definition of Done, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. Teams may add stricter criteria but cannot fall below the organizational minimum.

Question 26Scrum Foundations

In Scrum, what does the term timebox mean for an event such as the Sprint Planning?

  1. A fixed maximum duration that the event cannot exceed Correct answer.
  2. A minimum duration the team must fill with discussion
  3. A calendar restriction that limits who may attend
  4. A deadline set by the Product Owner for each backlog item

Explanation

A timebox is a fixed upper limit on the duration of a Scrum event; the event ends when the timebox is reached even if work remains. It caps the amount of time spent so that inspection and adaptation happen at predictable intervals rather than stretching indefinitely.

Question 27Scrum Foundations

Which description best matches the role of the Scrum Master?

  1. A proxy who makes product decisions when the Product Owner is unavailable
  2. A servant leader who helps the team and organization apply Scrum effectively Correct answer.
  3. A project manager who assigns tasks and reports status to stakeholders
  4. A technical lead who approves the architecture and design decisions

Explanation

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, which includes coaching the team, the Product Owner, and the organization. The role is one of facilitation and removing impediments rather than command and control.

Question 28Scrum Foundations

A Scrum Team consists of which three accountabilities?

  1. Stakeholders, sponsors, and customers
  2. Analysts, testers, and project managers
  3. Architects, designers, and quality assurance
  4. Developers, Product Owner, and Scrum Master Correct answer.

Explanation

The Scrum Team is a small team of people with three distinct accountabilities: Developers, Product Owner, and Scrum Master. Together they are self-managing and cross-functional, with no sub-teams or hierarchy within the team.

Question 29Scrum Foundations

What is the recommended size for a Scrum Team in the Scrum Guide?

  1. Ten or fewer people in total Correct answer.
  2. Between fifteen and twenty people
  3. As many as the budget allows
  4. Exactly five people

Explanation

Scrum recommends a team of ten or fewer people, small enough to remain nimble and large enough to complete significant work within a Sprint. If the team becomes too large, it should consider reorganizing into multiple cohesive Scrum Teams sharing the same Product Goal, backlog, and Product Owner.

Question 30Scrum Foundations

What does it mean that the Scrum Team is cross-functional?

  1. The team has all the skills needed to create value each Sprint Correct answer.
  2. The team shares members with other teams on a rotating basis
  3. Team members report to several functional managers at once
  4. Each member is trained in every discipline the team uses

Explanation

Cross-functional means the team collectively possesses the competencies required to deliver a valuable Increment each Sprint, so it does not depend on people outside the team. It does not require every individual to master every skill.

Question 31Scrum Foundations

Which statement describes the Product Goal?

  1. A document that records the decisions made during Sprint Retrospectives
  2. A list of features the Product Owner promises to deliver this quarter
  3. A long-term objective the Scrum Team plans against to guide the Product Backlog Correct answer.
  4. A metric the Scrum Master tracks to measure team velocity

Explanation

The Product Goal describes a future state of the product that serves as a target for the Scrum Team to plan against. It is the commitment associated with the Product Backlog, and the team must fulfill or abandon one objective before taking on the next.

Question 32Scrum Foundations

How does Scrum define the Increment?

  1. A concrete stepping stone toward the Product Goal that meets the Definition of Done Correct answer.
  2. A branch of code that has passed peer review but is not deployed
  3. A percentage of the Sprint Backlog completed by the end of the Sprint
  4. A report summarizing velocity trends across recent Sprints

Explanation

An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to prior increments and must meet the Definition of Done to be considered complete, regardless of whether it is released.

Question 33Scrum Foundations

What is the primary purpose of the Sprint Retrospective?

  1. To renegotiate the Product Goal with the Product Owner
  2. To demonstrate the finished Increment to stakeholders
  3. To plan ways to increase quality and effectiveness Correct answer.
  4. To estimate the effort for the next Sprint's backlog items

Explanation

The Sprint Retrospective concludes the Sprint and gives the team a chance to inspect how the last Sprint went regarding individuals, interactions, processes, tools, and the Definition of Done. The team then identifies the most helpful changes to improve its effectiveness.

Question 34Scrum Foundations

A Scrum Team is preparing for Sprint Planning. Which input is most essential for that event?

  1. A finalized Gantt chart covering the next three Sprints
  2. A complete design specification approved by an architect
  3. The ordered Product Backlog and the team's capacity for the Sprint Correct answer.
  4. A signed change request from the steering committee

Explanation

Sprint Planning addresses why the Sprint is valuable, what can be done, and how the work will get done. The ordered Product Backlog supplies candidate work, and the team's capacity and past performance inform how much it can take on.

Question 35Scrum Foundations

During Sprint Planning the Developers select backlog items they believe they can complete. What is the basis for this forecast?

  1. The number of items remaining in the Product Backlog
  2. A fixed quota of story points set by the organization
  3. Their capacity and past performance plus their understanding of the items Correct answer.
  4. The Product Owner's instruction about how many items to take

Explanation

Sprint Planning asks the Developers to forecast what they can deliver, informed by their capacity, their history, and their understanding of the selected items. The Product Owner may clarify value and ordering but does not dictate the amount of work.

Question 36Scrum Foundations

A team's Sprint is two weeks long. What is the maximum timebox for its Daily Scrum?

  1. One hour
  2. Fifteen minutes Correct answer.
  3. Ten minutes
  4. Thirty minutes

Explanation

The Daily Scrum is timeboxed to fifteen minutes regardless of Sprint length, keeping it a brief inspection of progress toward the Sprint Goal. Longer discussions belong in separate conversations after the event.

Question 37Scrum Foundations

How does the Scrum Guide describe the relationship between the Sprint Review and the Product Backlog?

  1. The Review requires the backlog to be fully refined before it starts
  2. The Review may lead to the Product Backlog being adapted to reflect new insights Correct answer.
  3. The Review transfers ownership of the backlog to the stakeholders
  4. The Review freezes the Product Backlog until the next Sprint begins

Explanation

The Sprint Review is a working session where the team and stakeholders inspect the outcome of the Sprint and determine what to do next. That discussion frequently results in adjustments to the Product Backlog, which is one of the intended outputs of the event.

Question 38Scrum Foundations

A Scrum Team wants to shorten its feedback loop so it can adapt more often. Which change best aligns with Scrum?

  1. Extend the Sprint to absorb unexpected work without replanning
  2. Choose a shorter Sprint duration so inspection and adaptation occur more frequently Correct answer.
  3. Eliminate the Sprint Review so the team can start the next Sprint sooner
  4. Run the Daily Scrum twice a day to double the inspection points

Explanation

Sprint length is chosen to balance the need for frequent feedback against the cost of running the events. A shorter Sprint increases the frequency of inspection and adaptation, which is exactly the feedback loop the team wants to tighten.

Question 39Scrum Foundations

What is the maximum timebox for a Sprint when the duration is not otherwise constrained?

  1. One month Correct answer.
  2. Six weeks
  3. Two weeks
  4. Three months

Explanation

Sprints are fixed-length events of one month or less; one month is the maximum. Shorter Sprints generate more learning cycles and limit risk to the cost of one Sprint, while the fixed length provides a consistent cadence.

Question 40Scrum Foundations

A stakeholder asks the Product Owner to insert a new feature request that is clearly valuable. How should the Product Owner handle it?

  1. Add it to the Product Backlog and order it against existing items for future consideration Correct answer.
  2. Reject it because the Product Backlog is closed once the Sprint starts
  3. Hand it directly to a developer to build alongside current Sprint work
  4. Schedule a special meeting to vote on whether the request is allowed

Explanation

The Product Backlog is the single source of work and evolves continuously; the Product Owner orders items by value. New requests are added and ordered, and whether they enter the current Sprint is decided by the Developers in collaboration with the Product Owner, not by freezing the backlog.

Question 41Scrum Foundations

Which of the following best describes the Definition of Done?

  1. A checklist the Scrum Master maintains to audit team compliance
  2. A contract that fixes the scope of each release
  3. A list of tasks the Developers plan to finish during the Sprint
  4. A formal description of the state of the Increment when it meets the quality measures required for the product Correct answer.

Explanation

The Definition of Done is a formal description of the quality state the Increment must reach for the work to be considered complete. It creates transparency by giving everyone a shared understanding of what done means, and the team creates it if the organization does not provide one.

Question 42Scrum Foundations

A team finishes all planned work early on day six of a ten-day Sprint. What is the most Scrum-aligned response?

  1. Collaborate with the Product Owner to refine the Sprint Backlog and consider pulling in more work toward the Sprint Goal Correct answer.
  2. End the Sprint immediately and begin the next one
  3. Idle until the Sprint ends so the cadence is preserved
  4. Start work on items from the next Sprint without telling anyone

Explanation

Scope may be clarified and renegotiated with the Product Owner as more is learned, and the Sprint Backlog is updated throughout the Sprint. The team can pull additional work that serves the Sprint Goal rather than waiting idly or jumping ahead.

Question 43Scrum Foundations

Which statement best explains why the Sprint is described as a container for the other events?

  1. All other Scrum events occur within the Sprint and serve its purpose Correct answer.
  2. The Sprint is the only event that requires stakeholder attendance
  3. The Sprint contains the Product Backlog and Definition of Done
  4. The Sprint is optional while the other events are mandatory

Explanation

The Sprint is a container event because Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective all happen inside it, and each exists to support the Sprint's goal. The Sprint provides the fixed cadence in which the other events make sense.

Question 44Scrum Foundations

A team argues that because the Daily Scrum is for Developers, the Scrum Master must never attend. How should this be understood?

  1. The Scrum Master is forbidden from attending any Daily Scrum under all circumstances
  2. The Product Owner must attend to prioritize the work discussed each day
  3. The Scrum Master must always run the Daily Scrum and record each member's answers
  4. The Daily Scrum is for the Developers, but the Scrum Master may attend to coach if it helps the team Correct answer.

Explanation

The Daily Scrum is owned by the Developers, who choose its structure and content, but the Scrum Master may attend to coach the team and help it stay within the timebox and focus. The event is for the Developers' planning, not for status reporting to others.

Question 45Scrum Foundations

An organization insists that every team use the same tool for tracking work and that the tool's workflow defines when work is complete. How does this interact with Scrum?

  1. Completion is irrelevant as long as the tool shows items as closed
  2. The team's Definition of Done governs completion; tools should support it rather than define it Correct answer.
  3. The tool's workflow automatically becomes the Definition of Done for all teams
  4. The Scrum Master must reject the tool and forbid its use by the team

Explanation

The Definition of Done is a quality standard owned by the team, and if the organization has one it is the minimum the team must apply. Tools are instruments that should reflect the team's Definition of Done, not replace or override it.

Question 46Scrum Foundations

A Product Owner is frequently unavailable, and Developers begin making product ordering decisions themselves. What does Scrum say about this situation?

  1. The Developers may permanently assume the Product Owner's ordering accountability
  2. The Product Owner remains accountable for maximizing value and must be available to the team Correct answer.
  3. The Scrum Master should take over ordering until a new Product Owner is hired
  4. The team should pause all Sprints until the Product Owner returns

Explanation

The Product Owner is accountable for the Product Backlog and for maximizing the value of the product, which requires availability to the team. When that accountability is not met, the Scrum Master coaches and helps remove the impediment rather than reassigning the accountability.

Question 47Scrum Foundations

Two Scrum Teams work on the same product and each maintains its own Product Backlog and Product Owner. Which statement reflects Scrum guidance?

  1. Each team should keep separate backlogs to preserve autonomy
  2. The Scrum Masters should merge the backlogs quarterly
  3. Multiple teams on one product should share one Product Backlog and one Product Owner Correct answer.
  4. Separate backlogs are fine if the teams use the same Definition of Done

Explanation

When several Scrum Teams work on the same product, they share the same Product Goal, Product Backlog, and Product Owner. This keeps ordering coherent and prevents conflicting priorities across teams.

Question 48Scrum Foundations

A team claims it is applying empiricism but plans every detail of the next six Sprints in advance and refuses to change the plan. What is the core problem?

  1. The team is holding Sprints that are too short
  2. The team has too many stakeholders involved in planning
  3. The plan is treated as fixed truth rather than a forecast adjusted as evidence arrives Correct answer.
  4. The team is not using enough estimation techniques

Explanation

Empiricism rests on transparency, inspection, and adaptation, meaning plans are forecasts that change as more is learned. Committing to a rigid multi-Sprint plan and refusing adjustment removes the adaptation that empiricism requires.

Question 49Scrum Foundations

A Scrum Team completes every planned item but repeatedly delivers increments that stakeholders say miss the intent. Which adjustment best reflects Scrum's emphasis on value?

  1. Add a second Sprint Review so stakeholders can give feedback twice
  2. Use the Sprint Review to inspect the Increment with stakeholders and adapt the Product Backlog toward the Product Goal Correct answer.
  3. Ask the Scrum Master to approve the Increment before release
  4. Increase the team's velocity target so more items are completed each Sprint

Explanation

Delivering the wrong thing faster does not create value; the Sprint Review exists so the team and stakeholders can inspect the outcome and adapt the Product Backlog. Focusing on that feedback loop aligns delivery with the Product Goal rather than with output volume.

Question 50Scrum Foundations

Which pairing of artifact and commitment is correct in Scrum?

  1. Increment and Product Goal
  2. Sprint Backlog and Product Goal
  3. Product Backlog and Definition of Done
  4. Sprint Backlog and Sprint Goal Correct answer.

Explanation

Each artifact has a commitment that reinforces transparency: the Product Backlog has the Product Goal, the Sprint Backlog has the Sprint Goal, and the Increment has the Definition of Done. Matching the Sprint Backlog with the Sprint Goal is therefore the correct pairing.