I85PREP
⌘ K
EXIN Agile Scrum Foundation study materials
EXIN Agile Scrum Foundation study resources

EXIN Agile Scrum Foundation practice questions

One question at a time. Build your EXIN Agile Scrum Foundation understanding.

First 50 of 200 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 1Agile and Scrum fundamentals

In Scrum, what is the primary purpose of the Daily Scrum?

  1. To refine backlog items with stakeholders before the next Sprint
  2. To demonstrate completed work to the Product Owner for acceptance
  3. To inspect progress toward the Sprint Goal and adapt the Sprint Backlog Correct answer.
  4. To report individual status to the Scrum Master for tracking

Explanation

The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adjust their plan for the next 24 hours. It is not a status report to a manager, and backlog refinement and Sprint Review happen in other events. Its output is an adapted Sprint Backlog, not documentation.

Question 2Agile and Scrum fundamentals

Which statement best describes the Scrum Master's accountability?

  1. Approving the Sprint Goal on behalf of the stakeholders
  2. Owning and ordering the Product Backlog to maximize value
  3. Deciding which Developers work on which tasks each day
  4. Establishing Scrum as defined in the Scrum Guide and removing impediments to the team's effectiveness Correct answer.

Explanation

The Scrum Master is accountable for the Scrum Team's effectiveness, coaching the team in Scrum practices and helping remove impediments. Ordering the Product Backlog belongs to the Product Owner, and task assignment is self-managed by the Developers. The Sprint Goal is created collaboratively by the whole Scrum Team.

Question 3Agile and Scrum fundamentals

What does the Product Owner order in the Product Backlog?

  1. Items by the estimated effort so the largest items are done first
  2. Items by value, risk, dependencies, and stakeholder needs to maximize product value Correct answer.
  3. Items alphabetically so that stakeholders can locate them quickly
  4. Items by the date they were requested to guarantee fairness

Explanation

The Product Owner is accountable for maximizing product value and orders backlog items using factors such as value, risk, dependencies, and stakeholder needs. Ordering is a value judgment, not a mechanical rule. Alphabetical, effort-based, or request-date ordering does not reflect value maximization.

Question 4Agile and Scrum fundamentals

A Scrum Team finishes all forecasted items early on day six of a ten-day Sprint. What is the most appropriate action?

  1. Start working on items planned for the next Sprint without informing anyone
  2. Collaborate with the Product Owner to select more backlog items that support the Sprint Goal Correct answer.
  3. End the Sprint early and begin Sprint Planning immediately
  4. Ask the Scrum Master to extend the Sprint by two days

Explanation

The Sprint's timebox is fixed, but its scope may be clarified and renegotiated with the Product Owner as more is learned. The team can pull in additional backlog items provided they stay consistent with the Sprint Goal. Ending early or extending the timebox violates the fixed-length Sprint rule.

Question 5Agile and Scrum fundamentals

Which of the following is a characteristic of the Sprint Review?

  1. It is a formal gate where stakeholders sign off before the Increment is released
  2. It is a meeting where the Scrum Master presents the team's velocity charts
  3. It is an informal working session inspecting the Increment and adapting the Product Backlog Correct answer.
  4. It is a retrospective focused on improving team processes

Explanation

The Sprint Review is a working session in which the Scrum Team and stakeholders inspect the Increment and collaborate on what to do next, adapting the Product Backlog. It is explicitly not a sign-off gate or a process retrospective. Its focus is the product, not team metrics presented by the Scrum Master.

Question 6Agile and Scrum fundamentals

What is the main purpose of the Sprint Retrospective?

  1. To review the Product Backlog with stakeholders and update priorities
  2. To estimate the effort of backlog items for the coming Sprint
  3. To plan ways to increase quality and effectiveness by inspecting how the last Sprint went Correct answer.
  4. To verify that the Increment meets the Definition of Done

Explanation

The Retrospective inspects how the last Sprint went regarding individuals, interactions, processes, tools, and the Definition of Done, and identifies improvements. Backlog prioritization is a Product Owner activity, and verification against the Definition of Done occurs during the Sprint as work is completed.

Question 7Agile and Scrum fundamentals

What is the role of the Definition of Done in Scrum?

  1. It is a list of acceptance tests written only by the Product Owner for each backlog item
  2. It is a formal description of the state of the Increment when it meets the quality measures required for the product Correct answer.
  3. It is a checklist the Scrum Master uses to audit each Developer's daily output
  4. It is a contract negotiated with the customer that fixes the scope of each Sprint

Explanation

The Definition of Done is a formal description of the quality state the Increment must reach for the product to be considered complete. It creates shared understanding of what work must be done and is used by the team, not as a management audit tool. It is not a fixed customer contract nor solely the Product Owner's acceptance tests.

Question 8Agile and Scrum fundamentals

A Product Owner wants to add a new high-value feature in the middle of a Sprint. What does Scrum prescribe?

  1. Instruct the Developers to work overtime so both the original scope and the new feature are delivered
  2. Reject all changes until the Sprint ends, because scope is frozen once Sprint Planning finishes
  3. Negotiate the change with the Developers, who may adjust the Sprint Backlog as long as the Sprint Goal is not endangered Correct answer.
  4. Cancel the Sprint immediately and start a new one to accommodate the feature

Explanation

Scope may be clarified and renegotiated with the Product Owner as more is learned during a Sprint, provided the Sprint Goal is not endangered. The Sprint Goal provides stability while the Sprint Backlog can flex. Cancelling the Sprint or mandating overtime is not the prescribed response to a single new request.

Question 9Agile and Scrum fundamentals

Who is accountable for the Product Backlog's content, availability, and ordering?

  1. The Scrum Master
  2. The Developers as a collective
  3. The Product Owner Correct answer.
  4. The key stakeholders who fund the product

Explanation

The Product Owner is accountable for the Product Backlog, including its content, availability, and ordering. The Scrum Master coaches on process, and the Developers help refine and estimate items but do not own the ordering. Stakeholders provide input but do not own the backlog.

Question 10Agile and Scrum fundamentals

Which statement correctly describes the Scrum Team's structure?

  1. It consists of a separate business team, a development team, and a quality assurance team
  2. It is a small, cross-functional team of one Scrum Master, one Product Owner, and Developers, with no sub-teams or hierarchies Correct answer.
  3. It is a temporary group formed for each Sprint and disbanded at the end of it
  4. It includes the Scrum Master, the Product Owner, and managers who assign work to Developers

Explanation

The Scrum Team is a small, cross-functional, self-managing unit made of one Scrum Master, one Product Owner, and Developers. It has no sub-teams or hierarchies and remains together across Sprints. Managers and separate functional sub-teams are not part of its structure.

Question 11Agile and Scrum fundamentals

During Sprint Planning, the Scrum Team formulates the Sprint Goal. When should this goal be finalized?

  1. At the Sprint Review, after stakeholders approve the Increment
  2. By the end of Sprint Planning, as part of the event's output Correct answer.
  3. At the Sprint Retrospective, based on the previous Sprint's metrics
  4. During the Daily Scrum on the first day of the Sprint

Explanation

Sprint Planning addresses why the Sprint is valuable, what can be done, and how the work will be done, producing the Sprint Goal and the Sprint Backlog by the end of the event. The goal is not deferred to the Daily Scrum, Review, or Retrospective. It gives the Sprint a shared objective from day one.

Question 12Agile and Scrum fundamentals

What is a key characteristic of the Increment in Scrum?

  1. It is a prototype that may be shown to stakeholders but is not usable
  2. It is the sum of all unfinished backlog items carried into the next Sprint
  3. It is a document summarizing the work completed during the Sprint
  4. It is a concrete, usable step toward the Product Goal that must meet the Definition of Done Correct answer.

Explanation

An Increment is a concrete, usable step toward the Product Goal, and each Increment is additive to prior ones and must meet the Definition of Done. It is working product, not a report or a non-usable prototype. Unfinished items are not an Increment.

Question 13Agile and Scrum fundamentals

Which is the correct description of the three pillars of empirical process control in Scrum?

  1. Estimation, commitment, and delivery
  2. Planning, execution, and control
  3. Vision, value, and velocity
  4. Transparency, inspection, and adaptation Correct answer.

Explanation

Scrum is founded on empiricism, whose three pillars are transparency, inspection, and adaptation. Transparency makes the process visible, inspection checks progress toward goals, and adaptation adjusts the process when deviations are found. The other triples are not Scrum's empirical pillars.

Question 14Agile and Scrum fundamentals

A team's Sprint Review has become a one-way slide presentation with no stakeholder discussion. What is the most Scrum-aligned improvement?

  1. Invite more senior managers to watch the presentation and approve the release
  2. Replace the review with a written status report sent to stakeholders
  3. Move the presentation to the Retrospective so the review can be shortened
  4. Reframe the event around a hands-on inspection of the Increment so stakeholders can give feedback that shapes the Product Backlog Correct answer.

Explanation

The Sprint Review is a working session where the Scrum Team and stakeholders inspect the Increment and collaborate on what to do next. A slide show without interaction defeats that purpose, so the fix is to make the Increment inspectable and use feedback to adapt the Product Backlog. Approval gates, status reports, and merging the review into the Retrospective all undermine the event's intent.

Question 15Agile and Scrum fundamentals

How should a Scrum Team treat technical debt discovered during a Sprint?

  1. Ignore it until a dedicated hardening phase after several releases
  2. Assign it to the Scrum Master to fix between Sprints
  3. Document it and defer it indefinitely so velocity stays high
  4. Make it transparent and address it through backlog items or the Definition of Done so quality is not eroded Correct answer.

Explanation

Technical debt should be made transparent and managed through the Product Backlog and a strong Definition of Done so that quality remains sustainable. Deferring it to a later hardening phase or hiding it undermines transparency and long-term value. The Scrum Master is not responsible for fixing technical work.

Question 16Agile and Scrum fundamentals

Which statement about the Sprint Backlog is correct?

  1. It is a fixed list of tasks that cannot change once Sprint Planning ends
  2. It is a plan by and for the Developers, composed of the Sprint Goal, selected Product Backlog items, and an actionable plan for delivering the Increment Correct answer.
  3. It is a reporting artifact that managers use to measure individual productivity
  4. It is owned by the Product Owner and updated at each Daily Scrum

Explanation

The Sprint Backlog is a plan by and for the Developers consisting of the Sprint Goal, the selected items, and the plan for delivering the Increment. It is updated throughout the Sprint as more is learned. It is not a fixed task list, does not belong to the Product Owner, and is not a management productivity report.

Question 17Agile and Scrum fundamentals

What does the Product Goal provide to the Scrum Team?

  1. A long-term target the team plans against, giving the Product Backlog focus Correct answer.
  2. A fixed deadline by which all backlog items must be delivered
  3. A financial target set by the organization's executives
  4. A per-Sprint commitment that replaces the Sprint Goal

Explanation

The Product Goal describes a future state of the product and serves as a long-term target for the Scrum Team to plan against, giving the Product Backlog focus. It is not a fixed deadline or a financial target, and it complements rather than replaces the Sprint Goal.

Question 18Agile and Scrum fundamentals

A new Scrum Master notices the Developers wait for the Product Owner to assign each task. What should the Scrum Master do?

  1. Coach the Developers toward self-management so they select their own work within the Sprint Goal Correct answer.
  2. Ask the Product Owner to write detailed task instructions for every item
  3. Escalate to line managers so they can assign tasks based on skills
  4. Take over task assignment to keep the Sprint moving efficiently

Explanation

The Scrum Master serves the team by coaching it in self-management and cross-functionality. Developers are expected to decide how to turn selected backlog items into value themselves. Taking over assignment, having the Product Owner micromanage tasks, or escalating to managers all reinforce the dependency instead of removing it.

Question 19Agile and Scrum fundamentals

Which of these best explains why Scrum uses timeboxes such as the Sprint?

  1. They guarantee that every planned item is delivered on the exact date promised
  2. They allow managers to compare individual Developers' output fairly
  3. They create a regular cadence for inspection and adaptation, limiting risk and enabling empiricism Correct answer.
  4. They remove the need for a Definition of Done because time is fixed

Explanation

Timeboxes create a predictable cadence for inspection and adaptation, which limits risk and supports empirical control. They do not guarantee delivery of all planned items, are not for comparing individuals, and do not replace quality standards like the Definition of Done.

Question 20Agile and Scrum fundamentals

What is the recommended maximum duration of a Sprint in Scrum?

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

Explanation

Sprints are fixed-length events of one month or less that keep risk and complexity manageable. Shorter Sprints are common and often preferred, but the maximum is one month. Fixed alternatives like exactly two weeks or longer periods such as three or six weeks exceed or misstate the rule.

Question 21Agile and Scrum fundamentals

In Scrum, what does 'cross-functional' mean for the Developers?

  1. Each Developer is required to be able to perform every task in the team
  2. Developers rotate roles with the Product Owner and Scrum Master each Sprint
  3. The team includes members from every department of the organization
  4. They collectively have all the skills needed to create value each Sprint Correct answer.

Explanation

Cross-functional means the Developers collectively possess all the skills necessary to create value each Sprint, not that every individual can do every task. It does not require representation from every department, and roles are not rotated among the accountabilities.

Question 22Agile and Scrum fundamentals

A stakeholder asks the Scrum Master to provide a detailed Gantt chart of all future Sprint work. What is the most appropriate response?

  1. Refuse to share any planning information until the project is finished
  2. Ask the Developers to commit to fixed dates for all backlog items
  3. Produce the Gantt chart by predicting every future Sprint in detail
  4. Explain that Scrum favors empirical planning with a Product Goal and Sprint Goals, and offer the Product Backlog and current Sprint plan as transparency tools Correct answer.

Explanation

Scrum plans empirically, using the Product Goal and Sprint Goals with a refined Product Backlog rather than a detailed multi-Sprint schedule. The Scrum Master should explain this and offer the backlog and Sprint plan to provide transparency. Fabricating a detailed Gantt chart or blanket refusal both damage trust, and forcing fixed commitments contradicts empiricism.

Question 23Agile and Scrum fundamentals

Which event is described as the heart of Scrum because it delivers value and creates inspectable Increments?

  1. The Sprint Correct answer.
  2. Backlog refinement
  3. The Sprint Retrospective
  4. The Daily Scrum

Explanation

The Sprint is the container for all other events and is often described as the heart of Scrum, where ideas are turned into value and an inspectable Increment is produced. The Daily Scrum, Retrospective, and refinement are supporting activities within or around the Sprint.

Question 24Agile and Scrum fundamentals

How does the Scrum Team handle a Sprint Goal that becomes obsolete mid-Sprint?

  1. The team waits until the Sprint Review to discuss it with stakeholders
  2. The Scrum Master unilaterally extends the Sprint to find a new goal
  3. The Developers must continue the Sprint regardless of the goal's relevance
  4. The Product Owner may cancel the Sprint, and the team reviews what happened and replans Correct answer.

Explanation

If the Sprint Goal becomes obsolete, the Sprint may be cancelled, and only the Product Owner has the authority to do so, often after consulting the team. Cancellation triggers a review of what happened and replanning. Continuing regardless, unilateral extension, or waiting for the Review ignores the obsolescence.

Question 25Agile and Scrum fundamentals

Which statement correctly distinguishes the Product Backlog from the Sprint Backlog?

  1. The Product Backlog is an emergent, ordered list of what is needed to improve the product, while the Sprint Backlog is the Developers' plan for one Sprint Correct answer.
  2. Both are identical lists maintained by the same person for reporting purposes
  3. The Product Backlog is owned by the Scrum Master, while the Sprint Backlog is owned by the Product Owner
  4. The Product Backlog is frozen at project start, while the Sprint Backlog changes daily

Explanation

The Product Backlog is an emergent, ordered list of what is needed to improve the product and is owned by the Product Owner. The Sprint Backlog is the Developers' plan for a single Sprint. The two differ in ownership, scope, and lifespan, and neither is a frozen list or a shared reporting document.

Question 26Agile and Scrum fundamentals

Which Scrum value is most directly demonstrated when Developers share honest progress updates in the Daily Scrum even when the work is behind schedule?

  1. Courage
  2. Respect
  3. Transparency Correct answer.
  4. Focus

Explanation

Transparency means making the true state of the work visible to everyone inspecting it, including uncomfortable news. Sharing accurate status rather than hiding delays is the practical expression of that value within the Daily Scrum.

Question 27Agile and Scrum fundamentals

In Scrum, what is the primary accountability of the Scrum Master?

  1. Owning and ordering the Product Backlog
  2. Establishing Scrum as described in the Scrum Guide Correct answer.
  3. Maximizing the value delivered by the Developers
  4. Deciding which items enter the Sprint Backlog

Explanation

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, by coaching the team and the organization and removing impediments. Value maximization belongs to the Product Owner, and backlog ordering is also the Product Owner's accountability.

Question 28Agile and Scrum fundamentals

Which statement best describes the Daily Scrum?

  1. It is a status meeting in which each Developer reports to the Scrum Master.
  2. It is a daily checkpoint where the Product Owner reprioritizes the Product Backlog.
  3. It is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Correct answer.
  4. It is a problem-solving session that may replace the Sprint Review.

Explanation

The Daily Scrum is a 15-minute event for the Developers, held at the same time and place each working day, to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a reporting meeting to the Scrum Master and does not involve Product Backlog ordering.

Question 29Agile and Scrum fundamentals

A Scrum Team has decided to adopt Scrum. Which combination of accountabilities forms the Scrum Team?

  1. Product Owner, Scrum Master, and line managers
  2. Project Manager, Product Owner, and Developers
  3. Product Owner, Scrum Master, and Developers Correct answer.
  4. Scrum Master, Developers, and stakeholders

Explanation

The Scrum Team consists of one Scrum Master, one Product Owner, and the Developers. There are no sub-teams or hierarchies, and managers or stakeholders are outside this structure.

Question 30Agile and Scrum fundamentals

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

  1. Two hours
  2. One day
  3. Eight hours Correct answer.
  4. Four hours

Explanation

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint, and shorter for shorter Sprints. The event ends earlier once the team has agreed on the Sprint Goal and the work needed to achieve it.

Question 31Agile and Scrum fundamentals

Which statement characterizes the Sprint Review?

  1. It is a meeting where only the Scrum Team may speak.
  2. It is a formal gate where the Product Owner accepts or rejects each Developer's work.
  3. It is the event where the Definition of Done is written for the first time.
  4. It is an informal working session to inspect the Increment and adapt the Product Backlog. Correct answer.

Explanation

The Sprint Review is an informal working session in which the Scrum Team and stakeholders inspect the Increment and collaborate on what to do next, adapting the Product Backlog. It is not a sign-off gate, and stakeholders are welcome to contribute.

Question 32Agile and Scrum fundamentals

A Developer repeatedly takes on more tasks than the team agreed, leaving other Developers without work. Which Scrum value does this behavior most directly undermine?

  1. Courage
  2. Respect Correct answer.
  3. Commitment
  4. Openness

Explanation

Respect involves treating colleagues as capable professionals and honoring shared agreements about how the team works. Taking more than the agreed share of work disregards teammates and their contribution.

Question 33Agile and Scrum fundamentals

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

  1. Two hours
  2. Four hours
  3. One hour
  4. Three hours Correct answer.

Explanation

The Sprint Retrospective is timeboxed to a maximum of three hours for a one-month Sprint, and it is shorter for shorter Sprints. Its purpose is to plan ways to increase quality and effectiveness.

Question 34Agile and Scrum fundamentals

A Product Owner is unavailable for two weeks, and the Developers need clarification on backlog items to finish the Sprint. What is the most appropriate Scrum-aligned response?

  1. The Developers make the best decision they can and note the assumption for later confirmation. Correct answer.
  2. The Scrum Master takes over ordering the Product Backlog in the Product Owner's absence.
  3. The Developers ask a stakeholder to formally approve the backlog changes.
  4. The Developers wait until the Product Owner returns before continuing any work.

Explanation

The Developers are self-managing and decide how to do their work, so they can proceed with reasonable assumptions and validate them later with the Product Owner. Scrum does not transfer Product Owner authority to the Scrum Master or to stakeholders.

Question 35Agile and Scrum fundamentals

Which pairing correctly matches a Scrum event with its primary purpose?

  1. Sprint Planning - inspecting the Increment with stakeholders
  2. Sprint Retrospective - defining the Sprint Goal for the next Sprint
  3. Sprint Review - adapting the Product Backlog based on the Increment Correct answer.
  4. Daily Scrum - updating the Product Owner on remaining work

Explanation

The Sprint Review inspects the Increment and its impact, then adapts the Product Backlog accordingly. Each other pairing links an event to a purpose that belongs to a different event or role.

Question 36Agile and Scrum fundamentals

How does Scrum describe the relationship between the Product Owner and the Developers regarding the Product Backlog?

  1. The Product Owner orders the backlog, and the Developers contribute items and refinement input. Correct answer.
  2. The Developers order the backlog, and the Product Owner approves it.
  3. The Scrum Master mediates all backlog discussions between them.
  4. Stakeholders order the backlog, and the Product Owner executes their decisions.

Explanation

The Product Owner is accountable for the Product Backlog and its ordering, while the Developers contribute new items and help refine it. This keeps decision authority clear while using the team's technical insight.

Question 37Agile and Scrum fundamentals

A Scrum Team's Sprint Goal is to 'reduce checkout errors by 50 percent.' Midway through the Sprint the Developers discover a simpler technical approach that still meets the goal but changes several planned tasks. What should happen?

  1. The Developers adjust the Sprint Backlog while keeping the Sprint Goal intact. Correct answer.
  2. The Product Owner must cancel the Sprint and start a new one.
  3. The Scrum Master must approve the change before work continues.
  4. The team should finish the original tasks first and apply the new approach next Sprint.

Explanation

The Sprint Goal gives the team flexibility on the 'how,' so the Developers may renegotiate and adjust Sprint Backlog tasks as long as the goal remains achievable. Cancelling a Sprint is reserved for when the Sprint Goal becomes obsolete.

Question 38Agile and Scrum fundamentals

Which statement best explains why the Sprint has a fixed length rather than a variable one?

  1. It allows the Product Owner to change the Sprint length for each iteration based on workload.
  2. It creates a consistent cadence that supports inspection and limits risk to a predictable horizon. Correct answer.
  3. It guarantees that every Product Backlog item will be completed within the Sprint.
  4. It removes the need for a Definition of Done.

Explanation

A consistent Sprint length establishes a rhythm for inspection and adaptation and caps the risk of going in the wrong direction to a predictable period. It does not guarantee completion of all items and does not replace the Definition of Done.

Question 39Agile and Scrum fundamentals

During a Sprint Retrospective, the Developers propose a change that requires support from people outside the Scrum Team. What is the most appropriate action?

  1. The team abandons the improvement because it lies outside their control.
  2. The Product Owner is required to implement the change personally.
  3. The team defers the improvement to the next Sprint Review.
  4. The Scrum Master helps the team identify and pursue ways to gain that outside support. Correct answer.

Explanation

The Retrospective ends with concrete improvements, and the Scrum Master's accountability includes helping the team and organization remove impediments, including those involving outside parties. Abandoning a valid improvement because it needs external help is not consistent with continuous improvement.

Question 40Agile and Scrum fundamentals

A stakeholder complains that the Developers are 'not specialized enough' because each person works across multiple skills. How should the Scrum Master respond?

  1. Explain that cross-functionality is intentional so the team has all skills needed to create value each Sprint. Correct answer.
  2. Suggest that each Developer be assigned permanently to one component.
  3. Agree and propose splitting the team into specialized sub-teams.
  4. Recommend hiring a coordinator to route work between specialists.

Explanation

Scrum Teams are cross-functional, meaning they collectively possess all the skills necessary to create value each Sprint. Specialized sub-teams or coordinators reintroduce handoffs and dependencies that Scrum seeks to reduce.

Question 41Agile and Scrum fundamentals

Which statement accurately describes the relationship between the Definition of Done and the Increment?

  1. Each Developer may apply a personal Definition of Done to their own portion.
  2. The Definition of Done applies only to the final release, not to each Increment.
  3. The Increment is considered done only when it meets the Definition of Done. Correct answer.
  4. The Increment is produced first, and the Definition of Done is written afterward to describe it.

Explanation

Work cannot be considered part of an Increment unless it meets the Definition of Done, which is a formal description of the state of the Increment when it meets the quality measures required for the product. The definition is shared and applies to every Increment.

Question 42Agile and Scrum fundamentals

A Scrum Team is refining a large Product Backlog item that cannot fit in one Sprint. What is the most appropriate Scrum practice?

  1. Keep it as one item and let it span multiple Sprints.
  2. Ask the Scrum Master to estimate it on the Developers' behalf.
  3. Move it to a separate 'future' backlog outside the Product Backlog.
  4. Split the item into smaller items that can each be completed within a Sprint. Correct answer.

Explanation

Product Backlog items are refined into smaller, more precise items so they can be completed within a Sprint and meet the Definition of Done. Splitting preserves the ability to deliver a usable Increment each Sprint.

Question 43Agile and Scrum fundamentals

Which statement correctly describes the Scrum Team's size guidance?

  1. Exactly seven Developers plus the Product Owner and Scrum Master.
  2. Size is irrelevant as long as the team is cross-functional.
  3. Typically ten or fewer people in total, small enough to remain nimble and large enough to complete significant work. Correct answer.
  4. At least fifteen people to ensure sufficient specialization.

Explanation

The Scrum Guide suggests a Scrum Team is typically ten or fewer people, balancing nimbleness with the ability to complete significant work within a Sprint. Larger groups increase complexity and communication overhead.

Question 44Agile and Scrum fundamentals

A Scrum Master notices that the team treats the Daily Scrum as a lengthy problem-solving session that regularly runs 45 minutes. What is the most appropriate action?

  1. Invite the Product Owner to chair the meeting and enforce time.
  2. Cancel the Daily Scrum so the team can focus on development.
  3. Extend the timebox to match the team's discussion needs.
  4. Coach the Developers to keep the Daily Scrum within 15 minutes and take deeper discussions offline. Correct answer.

Explanation

The Daily Scrum is timeboxed to 15 minutes; detailed problem-solving belongs in follow-up conversations among the relevant Developers. The Scrum Master coaches the team on the event's purpose and timebox rather than changing or cancelling it.

Question 45Agile and Scrum fundamentals

Which statement best captures the meaning of empiricism as applied in Scrum?

  1. Plans are fixed at the start and only changed at project closure.
  2. Progress is measured primarily by the percentage of planned tasks completed.
  3. All requirements must be fully specified before development begins.
  4. Decisions are based on observation, experience, and experimentation rather than on detailed up-front prediction. Correct answer.

Explanation

Empiricism holds that knowledge comes from experience and decisions are made on what is observed, which is why Scrum relies on frequent inspection and adaptation. It contrasts with fully predictive, plan-driven approaches.

Question 46Agile and Scrum fundamentals

A Product Owner wants to forecast delivery for the next quarter. Which approach is most consistent with Scrum?

  1. Commit to a fixed scope and date derived from a detailed work breakdown structure.
  2. Delay all forecasting until the Product Backlog is fully refined and frozen.
  3. Use the ordered Product Backlog and observed team throughput to forecast, and revise as new information emerges. Correct answer.
  4. Ask each Developer to guarantee completion dates for assigned backlog items.

Explanation

Forecasting in Scrum is based on empirical data such as ordered backlog items and observed throughput, and forecasts are revised as more is learned. Fixed commitments derived from detailed plans contradict the adaptive nature of Scrum.

Question 47Agile and Scrum fundamentals

A Scrum Team delivers a potentially releasable Increment every Sprint, but the organization releases to production only twice a year. Which analysis is most accurate from a Scrum perspective?

  1. The Scrum Master should take over the release process to align it with Sprints.
  2. The team is not doing Scrum because Scrum requires releasing every Sprint.
  3. The team is satisfying Scrum; the release cadence is an organizational decision that can be improved separately. Correct answer.
  4. The team should stop creating Increments until a release date is confirmed.

Explanation

Scrum requires a usable Increment each Sprint, but it does not mandate releasing to production every Sprint; that is a separate business and organizational decision. The gap between capability and release cadence is a legitimate improvement topic, not a Scrum violation by the team.

Question 48Agile and Scrum fundamentals

During Sprint Planning the Developers realize the selected Product Backlog items exceed what they can finish. What is the most appropriate action?

  1. Reduce the Definition of Done so all items can be counted as complete.
  2. Negotiate scope with the Product Owner while preserving a coherent Sprint Goal. Correct answer.
  3. Commit to the full scope and rely on overtime to close the gap.
  4. Ask the Scrum Master to add more Developers to the team immediately.

Explanation

The Developers forecast what they can complete, and scope is negotiated with the Product Owner so the Sprint Goal remains achievable. Weakening quality standards or relying on sustained overtime undermines transparency and sustainable pace.

Question 49Agile and Scrum fundamentals

A manager asks the Scrum Master to report each Developer's individual velocity so performance bonuses can be assigned. What is the most appropriate response?

  1. Ask the Developers to self-report individual velocity in the Daily Scrum.
  2. Replace velocity with individual story-point totals per Developer.
  3. Provide the individual numbers because managers have a right to all team data.
  4. Explain that velocity is a team-level planning aid and individual performance metrics conflict with Scrum's team accountability. Correct answer.

Explanation

Velocity is a forecasting aid for the Scrum Team as a whole and is not designed to measure individuals. Using it for individual bonuses encourages gaming and undermines the collective accountability Scrum depends on.

Question 50Agile and Scrum fundamentals

A Scrum Team's stakeholders rarely attend the Sprint Review, so feedback arrives late and rework increases. Which action best addresses the root cause while remaining consistent with Scrum?

  1. Have the Scrum Master send written status reports in place of the Review.
  2. Move stakeholder feedback into the Retrospective instead.
  3. Lengthen the Sprint so there are fewer Reviews to organize.
  4. Work with the Product Owner to make the Sprint Review compelling and invite the right stakeholders to inspect the Increment. Correct answer.

Explanation

The Sprint Review exists so stakeholders can inspect the Increment and provide feedback that shapes the Product Backlog; low attendance is addressed by making the session relevant and inviting the right participants. Substituting reports or shifting feedback to the Retrospective removes the essential inspection of the product.