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

EXIN Agile Scrum Master practice questions

One question at a time. Build your EXIN Agile Scrum Master 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 1Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

In Scrum, which statement best describes the purpose of the Daily Scrum?

  1. It is a short daily event where Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog. Correct answer.
  2. It is a planning session where the Product Owner reprioritises the Product Backlog.
  3. It is a formal review in which stakeholders accept or reject completed work.
  4. It is a status report that the Scrum Master compiles for senior management.

Explanation

The Daily Scrum is an event reserved for the Developers, lasting about fifteen minutes, in which they inspect progress toward the Sprint Goal and adjust their plan for the coming day. It is not a management status meeting, a stakeholder review, or a backlog refinement session.

Question 2Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A Scrum Team consists of which three accountabilities?

  1. Product Owner, Business Analyst, Developers
  2. Scrum Master, Stakeholders, Quality Assurance
  3. Product Owner, Project Manager, Development Team
  4. Scrum Master, Product Owner, Developers Correct answer.

Explanation

Scrum defines three accountabilities within one Scrum Team: the Product Owner, the Scrum Master, and the Developers. There is no Project Manager or Business Analyst accountability in Scrum, and stakeholders sit outside the Scrum Team.

Question 3Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

What is the primary purpose of the Sprint Retrospective?

  1. To inspect how the last Sprint went regarding individuals, interactions, processes, tools and Definition of Done, and to plan improvements. Correct answer.
  2. To demonstrate the Increment to stakeholders and collect feedback.
  3. To refine and estimate the highest-priority Product Backlog items.
  4. To plan which Product Backlog items will be delivered in the next Sprint.

Explanation

The Retrospective closes the Sprint by letting the Scrum Team inspect how it worked and identify the most helpful changes to improve effectiveness. Demonstrating the Increment belongs to the Sprint Review, and selecting future work belongs to Sprint Planning.

Question 4Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Which artefact is described as an emergent, ordered list of what is needed to improve the product?

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

Explanation

The Product Backlog is the single source of work for the Scrum Team: an emergent, ordered list of what is needed to improve the product. It is the only artefact whose ordering is owned by the Product Owner.

Question 5Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

How long is a Sprint in Scrum?

  1. Exactly two weeks, always.
  2. As long as needed to complete all committed items.
  3. One month or less, with a consistent duration. Correct answer.
  4. Determined individually for each Sprint by the Scrum Master.

Explanation

Sprints are fixed-length events of one month or less, and a new Sprint starts immediately after the previous one ends. Keeping a consistent duration supports predictability and limits risk to the cost of one Sprint.

Question 6Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Who is accountable for maximising the value of the product resulting from the Scrum Team's work?

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

Explanation

The Product Owner is accountable for maximising product value and for effective Product Backlog management, including ordering and transparency. This accountability cannot be delegated to a committee or to the Developers.

Question 7Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

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

  1. A list of every task the Developers must perform in each Sprint.
  2. A shared understanding of the quality measures required for the Increment to be considered complete. Correct answer.
  3. A contractual scope baseline agreed with the customer before the project starts.
  4. A record of which team member completed each Product Backlog item.

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. It creates shared understanding and, once adopted, is used to verify whether work is complete.

Question 8Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

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

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

Explanation

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint, and the event is shorter for shorter Sprints. The Scrum Team decides the topics and structure of the discussion within that timebox.

Question 9Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

During a Sprint, the Product Owner asks the Developers to add a new high-value item that was not in the Sprint Backlog. What does Scrum say?

  1. The scope of the Sprint may be clarified and renegotiated with the Product Owner as more is learned, while the Sprint Goal remains unchanged. Correct answer.
  2. The Scrum Master must approve any change before it enters the Sprint.
  3. No change of any kind may be made once the Sprint has started.
  4. The Developers must accept it because the Product Owner controls all work.

Explanation

Sprint scope may be clarified and renegotiated with the Product Owner as more is learned, but the Sprint Goal and the quality target of the Definition of Done stay fixed. If the goal becomes obsolete, the Product Owner may cancel the Sprint.

Question 10Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Which statement about the Increment is correct?

  1. It is the sum of the completed, usable work that meets the Definition of Done and adds value. Correct answer.
  2. It is a document listing all unfinished Product Backlog items.
  3. It must be released to production at the end of every Sprint.
  4. It is produced only at the end of the final Sprint before release.

Explanation

An Increment is a concrete stepping stone toward the product goal: the sum of completed work that meets the Definition of Done and provides value. Multiple Increments may be produced within a single Sprint, and release is a business decision rather than a Scrum requirement.

Question 11Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A team's Sprint Review turns into a one-way slide presentation with no stakeholder discussion. Which correction best aligns with Scrum?

  1. Restrict attendance to the Developers so feedback is not disruptive.
  2. Extend the Sprint Review to a full day so every slide can be covered.
  3. Invite stakeholders to inspect the Increment together and discuss what to do next, using the working product as the focus. Correct answer.
  4. Cancel the Sprint Review and replace it with a written status report to management.

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. It should focus on the actual product and adapt the Product Backlog, not on reporting progress through slides.

Question 12Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

What are the two questions Sprint Planning addresses?

  1. Why is this Sprint valuable, and what can be done this Sprint? Correct answer.
  2. Who will do each task, and how long will each task take?
  3. What did we do last Sprint, and what went wrong?
  4. Which risks exist, and who owns each risk?

Explanation

Sprint Planning covers why the Sprint is valuable by defining the Sprint Goal, and what can be done by selecting items from the Product Backlog. The Developers then decide how the chosen work will be done.

Question 13Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Which behaviour is most consistent with the Scrum value of courage?

  1. The Scrum Master avoids raising uncomfortable impediments to protect the team's morale.
  2. The Developers accept all requests from stakeholders to keep everyone happy.
  3. The Product Owner hides disappointing metrics from stakeholders to avoid conflict.
  4. The Developers say no to work that cannot be completed within the Definition of Done. Correct answer.

Explanation

Courage means doing the right thing and working on tough problems, which includes being honest about what can be completed to the Definition of Done. Scrum values are only meaningful when they shape daily behaviour and decisions.

Question 14Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

How does the Scrum Master serve the wider organisation?

  1. By personally writing the Product Backlog for teams that lack a Product Owner.
  2. By acting as the line manager who appraises the Developers' performance.
  3. By leading, training and coaching the organisation in its Scrum adoption and helping remove barriers between stakeholders and Scrum Teams. Correct answer.
  4. By approving every release before it reaches production.

Explanation

The Scrum Master serves the organisation by leading and coaching its Scrum adoption, planning and advising on implementation, and helping remove barriers between stakeholders and Scrum Teams. The role is one of coaching and facilitation rather than managerial control.

Question 15Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

What distinguishes the Product Backlog from the Sprint Backlog?

  1. The Product Backlog contains only bugs, while the Sprint Backlog contains only new features.
  2. The Product Backlog is owned by the Scrum Master, while the Sprint Backlog is owned by the Product Owner.
  3. The Product Backlog is frozen after release planning, while the Sprint Backlog changes daily.
  4. The Product Backlog is a long-lived, emergent list of everything needed for the product, while the Sprint Backlog is the subset selected for one Sprint plus a plan. Correct answer.

Explanation

The Product Backlog is the emergent, ordered source of all work needed to improve the product; the Sprint Backlog is the set of items selected for a Sprint together with the Developers' plan for delivering the Sprint Goal. Ownership of the Sprint Backlog belongs to the Developers.

Question 16Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

The Developers estimate that selected Product Backlog items will take longer than the Sprint. What is the appropriate action in Sprint Planning?

  1. Negotiate the Sprint Goal and select a smaller, coherent set of items that the Developers forecast they can complete. Correct answer.
  2. Commit to all items anyway and rely on overtime to finish.
  3. Extend the Sprint length for this one Sprint so everything fits.
  4. Ask the Scrum Master to add more Developers to the team before the Sprint starts.

Explanation

The Developers forecast what they can deliver and collaborate with the Product Owner to shape a Sprint Goal that fits within the timebox. Overcommitment is avoided because the Sprint length is fixed and the forecast must be realistic.

Question 17Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Which pairing of artefact and commitment is correct?

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

Explanation

Each Scrum artefact carries a commitment: the Product Backlog has the Product Goal, the Sprint Backlog has the Sprint Goal, and the Increment has the Definition of Done. These commitments reinforce transparency and focus.

Question 18Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A Scrum Master notices that a manager keeps assigning tasks directly to individual Developers during the Sprint. What is the most appropriate response?

  1. Take over the Developers' task assignment so there is a single authority.
  2. Instruct the Developers to ignore the manager and say nothing further.
  3. Escalate the manager to human resources as a disciplinary matter.
  4. Coach the manager on self-management and help the Scrum Team and organisation understand how Scrum changes the way work is directed. Correct answer.

Explanation

The Scrum Master serves the organisation by coaching it on Scrum and helping remove barriers between stakeholders and the Scrum Team. Direct task assignment undermines the Developers' self-management, so the fix is education and facilitation rather than confrontation or centralised control.

Question 19Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Which statement best captures empiricism as used in Scrum?

  1. Knowledge comes from experience, and decisions are made on what is observed through transparency, inspection and adaptation. Correct answer.
  2. Decisions are based on forecasts produced by detailed upfront planning documents.
  3. Knowledge is derived from following a prescribed process without deviation.
  4. Decisions are made by the most experienced senior manager in the organisation.

Explanation

Empiricism holds that knowledge comes from experience and that decisions should be based on observation. Scrum implements this through transparency, inspection and adaptation, which let the team respond to what actually happens rather than to assumptions.

Question 20Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

The Product Owner wants to add a new item to the top of the Product Backlog mid-Sprint because of a competitor announcement. What is the Scrum-consistent course of action?

  1. Insert the item into the current Sprint Backlog immediately and require the Developers to deliver it.
  2. The Scrum Master must reject the change until the next quarterly planning cycle.
  3. The Product Owner may reorder the Product Backlog at any time, and the Developers negotiate whether and how it affects the current Sprint. Correct answer.
  4. The item must wait until the current Sprint ends and cannot influence the Product Backlog until then.

Explanation

The Product Owner orders the Product Backlog and may change it at any time, while the Developers own the Sprint Backlog and negotiate scope with the Product Owner during the Sprint. The Sprint Goal, once set, remains the fixed target unless the Sprint is cancelled.

Question 21Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

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

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

Explanation

The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint and is shorter for shorter Sprints. The event includes inspecting the Increment and adapting the Product Backlog with stakeholders.

Question 22Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A Scrum Team is distributed across time zones and struggles to hold a daily synchronous meeting. Which approach is most consistent with Scrum?

  1. Replace the Daily Scrum with a weekly written report from each Developer.
  2. Keep the Daily Scrum as a short daily event, adjusting format and timing (for example an asynchronous or rotating-time call) to fit the distributed context. Correct answer.
  3. Let each Developer hold a private daily check-in and share nothing with the team.
  4. Move the Daily Scrum to the end of the Sprint so all days can be discussed at once.

Explanation

Scrum requires the Daily Scrum to occur daily, but the format is flexible and can be adapted to context as long as the Developers inspect progress toward the Sprint Goal. Removing the event or making it private breaks the inspection and adaptation it exists for.

Question 23Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

The Scrum Master is also the Product Owner for the same Scrum Team. Which statement best evaluates this arrangement?

  1. It conflicts with Scrum because the accountabilities require different focuses, and combining them weakens the checks between value ordering and facilitation. Correct answer.
  2. It is required in small teams where fewer than five people are involved.
  3. It is ideal because it reduces communication overhead between the two accountabilities.
  4. It is acceptable only if the Scrum Master delegates the Daily Scrum to a Developer.

Explanation

Scrum defines the Product Owner, Scrum Master and Developers as distinct accountabilities, and combining the Product Owner and Scrum Master roles blurs the separation between value ordering and facilitation. Small teams may combine Developer and Scrum Master work more easily, but the Product Owner role should remain distinct.

Question 24Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Midway through a Sprint, the Sprint Goal becomes obsolete because of a major regulatory change. Who may cancel the Sprint, and what happens next?

  1. The Scrum Master may cancel it after consulting stakeholders, and all work is restarted from scratch.
  2. Only the Product Owner may cancel the Sprint; completed and releasable work is reviewed, and unfinished items return to the Product Backlog. Correct answer.
  3. The Developers may cancel it by majority vote, and the Increment is discarded entirely.
  4. No one may cancel a Sprint once it has started under any circumstances.

Explanation

A Sprint can be cancelled only by the Product Owner, typically when the Sprint Goal becomes obsolete. On cancellation, completed and releasable items are reviewed for release, and unfinished items return to the Product Backlog for reordering.

Question 25Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A team claims to be agile but delivers only at the end of a six-month release cycle, has a manager assigning tasks, and holds no Retrospectives. Which analysis best fits Scrum principles?

  1. The team is practising Scrum correctly because it uses Sprints internally.
  2. The team only needs to add a Daily Scrum to become fully compliant with Scrum.
  3. The team is agile because release cadence is a technical decision unrelated to Scrum.
  4. The team has adopted some Scrum vocabulary but lacks the empirical loop of short increments, self-management and regular inspection and adaptation. Correct answer.

Explanation

Scrum relies on short, releasable Increments, self-managing Developers, and regular inspection and adaptation through events such as the Retrospective. A long release cycle, externally assigned tasks and missing Retrospectives break that empirical loop, so the label alone does not make the team agile.

Question 26Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

In Scrum, which three accountabilities together make up the Scrum Team?

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

Explanation

Scrum defines a single team containing exactly three accountabilities: the Product Owner, the Scrum Master and the Developers. There is no project manager or separate quality role inside the Scrum Team, and stakeholders sit outside it.

Question 27Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Which statement describes the Developers accountability in Scrum?

  1. They approve changes to the product vision before the Product Owner may act
  2. They self-manage to turn selected Product Backlog items into a usable Increment each Sprint Correct answer.
  3. They coordinate the Scrum events on behalf of the Scrum Master
  4. They decide how much work the Product Owner may add during a Sprint

Explanation

The Developers are the people in the Scrum Team who create the Increment and self-manage their own work. They decide how to do the work, not whether the Product Owner may change the backlog, and event facilitation belongs to the Scrum Master.

Question 28Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

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

  1. Commitment Correct answer.
  2. Efficiency
  3. Competitiveness
  4. Scalability

Explanation

The five Scrum values are commitment, focus, openness, respect and courage. Efficiency, competitiveness and scalability are general business terms that Scrum does not list as values.

Question 29Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

How long is the Daily Scrum timebox for a team whose Sprint lasts two weeks?

  1. It scales with the Sprint length
  2. Fifteen minutes Correct answer.
  3. One hour
  4. Thirty minutes

Explanation

The Daily Scrum is timeboxed to fifteen minutes regardless of Sprint length or team size. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog, so it is kept short and focused.

Question 30Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A Scrum Team has never produced a usable Increment during its first four Sprints because testing is deferred to a later phase. Which Scrum principle does this most directly violate?

  1. The team should deliver a potentially releasable Increment every Sprint Correct answer.
  2. The team should extend the Sprint length until testing fits
  3. The team should appoint a separate test phase owner
  4. The team should hold a hardening Sprint before every release

Explanation

Scrum requires the team to create a usable Increment that meets the Definition of Done every Sprint, which means all quality work happens inside the Sprint. Deferring testing to a later phase breaks that expectation and hides undone work.

Question 31Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

During Sprint Retrospective, a team identifies that its code review step is slowing delivery. Who decides what action to take?

  1. The Product Owner alone, because the backlog must reflect the change
  2. The Scrum Team, which inspects itself and chooses improvements to act on Correct answer.
  3. The Scrum Master alone, because process improvement is their accountability
  4. The stakeholders, who vote on improvements at the next Sprint Review

Explanation

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and identify the most helpful improvements, which are then addressed as soon as possible. The Scrum Master facilitates the event but does not dictate the outcome.

Question 32Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

What is the primary purpose of the Sprint Review?

  1. To decide which Developers will work on which items next Sprint
  2. To inspect the outcome of the Sprint and determine future adaptations with stakeholders Correct answer.
  3. To approve or reject the work the Developers completed during the Sprint
  4. To estimate the effort needed for the next Sprint's backlog items

Explanation

The Sprint Review is a working session where the Scrum Team and stakeholders inspect the Increment and the Product Backlog and collaborate on what to do next. It is not a sign-off gate, and detailed estimation happens during Sprint Planning.

Question 33Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Which statement correctly describes the relationship between the Product Backlog and the Sprint Goal?

  1. The Sprint Goal is a commitment of the Sprint Backlog, chosen during Sprint Planning Correct answer.
  2. The Sprint Goal is created by stakeholders at the Sprint Review
  3. The Sprint Goal is a commitment of the Product Backlog, set once per release
  4. The Sprint Goal is optional when the team is experienced

Explanation

The Sprint Goal is the single objective for the Sprint and serves as the commitment attached to the Sprint Backlog. It is crafted collaboratively during Sprint Planning and gives the Developers a shared focus.

Question 34Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A Scrum Master observes that Developers are waiting for the Product Owner to assign them individual tasks each morning. What is the most appropriate response?

  1. Coach the team so that the Developers self-manage the Sprint Backlog Correct answer.
  2. Introduce a team lead who assigns tasks to keep the Daily Scrum short
  3. Ask the Product Owner to publish a daily task list before the Daily Scrum
  4. Escalate to management so that task assignment becomes formal

Explanation

Self-management means the Developers decide among themselves how to turn selected items into an Increment, including who does what. The Scrum Master's service is to coach the team toward that behaviour rather than to install new command structures.

Question 35Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

Which artefact is described as a commitment for the Product Backlog?

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

Explanation

Each Scrum artefact has a commitment attached to it: the Product Goal for the Product Backlog, the Sprint Goal for the Sprint Backlog and the Definition of Done for the Increment. These commitments bring transparency and focus to the artefacts.

Question 36Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A team completes all selected items but the Product Owner wants to release immediately. What determines whether the work may be described as finished?

  1. The number of story points completed in the Sprint
  2. The Definition of Done agreed by the Scrum Team Correct answer.
  3. The Scrum Master's verbal confirmation at the Daily Scrum
  4. The stakeholders' informal approval at the Sprint Review

Explanation

The Definition of Done is the formal description of the state of the Increment when it meets the quality measures required for the product. Work is only finished when it meets that definition, which is why it governs releasability.

Question 37Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A Scrum Master is told that a manager wants weekly written status reports from each Developer. How should the Scrum Master interpret this against Scrum?

  1. Redirect the request toward transparency already provided by the artefacts and events Correct answer.
  2. Ask the Developers to produce the reports after hours
  3. Refuse all contact between the team and management
  4. Comply, because management reporting always overrides Scrum events

Explanation

Scrum favours transparency through its artefacts and events rather than individual reporting lines. The Scrum Master can help the organisation understand that the Product Backlog, Sprint Backlog and Increment already expose progress and impediments.

Question 38Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A Product Owner wants to forecast delivery but the Developers have never estimated any items. Which action is most consistent with Scrum?

  1. Have the Product Owner estimate alone to save team time
  2. Commit to fixed dates before any sizing occurs
  3. Replace estimation with a promise to work faster
  4. Have the Developers size items collaboratively and refine the backlog regularly Correct answer.

Explanation

Estimation in Scrum is a Developer responsibility and is done collaboratively, often through backlog refinement, so the Product Backlog gains enough transparency to support forecasting. The Product Owner uses those sizes to plan but does not size alone.

Question 39Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A Scrum Team argues that its Sprint Review should be skipped because no stakeholder ever attends. Which analysis is most sound?

  1. Skipping is fine as long as the Retrospective still happens
  2. Skipping is fine because the Review adds no value without attendees
  3. Skipping is acceptable if the Daily Scrum is extended
  4. Skipping removes the inspection point and should be replaced by efforts to engage stakeholders Correct answer.

Explanation

The Sprint Review is a required Scrum event and is the main opportunity to inspect the Increment with stakeholders and adapt the Product Backlog. When attendance is poor, the correct response is to make the Review more inviting and relevant, not to cancel it.

Question 40Agile and Scrum fundamentals (concepts, principles, roles, artefacts and events)

A Scrum Team claims to be agile but holds one release per quarter, has a manager assigning tasks, and treats the Daily Scrum as a status report to that manager. Which conclusion is best supported?

  1. The team needs only a longer Sprint to become compliant
  2. The team has adopted Scrum events but not the underlying principles of self-management and incremental delivery Correct answer.
  3. The team is agile because releases happen regularly
  4. The team follows Scrum because it holds a daily meeting

Explanation

Practising the ceremonies without self-management, frequent usable Increments and genuine empiricism is mechanical Scrum rather than agile working. The evidence points to missing principles, not to a missing event or a wrong Sprint length.

Question 41Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

In Scrum, which role is accountable for maximizing the value of the product resulting from the work of the Scrum Team?

  1. The stakeholders who fund the product
  2. The Development Team
  3. The Scrum Master
  4. The Product Owner Correct answer.

Explanation

The Product Owner is accountable for maximizing product value, primarily by managing and ordering the Product Backlog effectively. This accountability is defined by the Scrum Guide and cannot be delegated to the Scrum Master or the developers, although the Product Owner may seek input from others.

Question 42Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

A Scrum Team is self-managing. What does this most accurately mean for the Development Team?

  1. They can change the Sprint length without consulting the Product Owner
  2. They decide internally who does what, when, and how to accomplish their work Correct answer.
  3. They report progress only when the Scrum Master requests it
  4. They may ignore the Definition of Done if the Sprint Goal is still met

Explanation

Self-managing means the team internally decides who does what, when, and how. It does not license bypassing the Definition of Done, altering Sprint cadence unilaterally, or hiding progress from stakeholders.

Question 43Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

Which statement best describes the Scrum Master's authority over the Development Team?

  1. The Scrum Master approves or rejects the team's technical design decisions
  2. The Scrum Master assigns daily tasks to each developer to ensure the Sprint Goal is met
  3. The Scrum Master decides which developers attend the Daily Scrum
  4. The Scrum Master serves the team by coaching and removing impediments rather than directing its work Correct answer.

Explanation

The Scrum Master is a servant-leader who coaches the team and helps remove impediments, not a line manager who assigns tasks. Task assignment, technical decisions, and Daily Scrum attendance belong to the self-managing developers.

Question 44Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

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

  1. The most senior developer
  2. The whole Scrum Team by majority vote
  3. The Scrum Master
  4. The Product Owner Correct answer.

Explanation

Ordering the Product Backlog is a Product Owner accountability; the owner may be influenced by the team and stakeholders but retains the decision. Ordering by seniority or majority vote is not a Scrum practice.

Question 45Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

A Scrum Team consists of which combination of roles?

  1. One Product Owner, one project manager, and technical architects
  2. One Product Owner, one Scrum Master, and the developers Correct answer.
  3. One Scrum Master, one test manager, and the developers
  4. A product manager, a team lead, and business analysts

Explanation

A Scrum Team is made up of one Product Owner, one Scrum Master, and the developers. Project managers, team leads, and test managers are not Scrum roles, even if similar responsibilities exist informally.

Question 46Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

Which activity is clearly within the Product Owner's responsibilities?

  1. Removing impediments reported by developers
  2. Coaching the team on cross-functionality
  3. Developing and explicitly communicating the Product Goal Correct answer.
  4. Facilitating Scrum events as needed

Explanation

The Product Owner develops and communicates the Product Goal and manages the Product Backlog. Facilitating events, coaching on cross-functionality, and removing impediments are Scrum Master services.

Question 47Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

During the Sprint, who decides how much work the Development Team takes on from the Product Backlog?

  1. The Scrum Master, who balances workload across members
  2. The stakeholders, who prioritize by business value
  3. The Product Owner, who assigns items to individuals
  4. The developers, who forecast what they can complete Correct answer.

Explanation

The developers forecast how much they can complete during Sprint Planning and self-manage the work. The Product Owner clarifies value and ordering but does not assign work, and stakeholders do not size the team's capacity.

Question 48Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

What is the primary way the Scrum Master serves the Product Owner?

  1. Deciding which backlog items deliver the most value
  2. Writing the acceptance criteria for backlog items
  3. Helping find techniques for effective Product Goal definition and Product Backlog management Correct answer.
  4. Approving the release plan before it is shared

Explanation

The Scrum Master serves the Product Owner by helping establish effective techniques for Product Goal definition and backlog management. Writing criteria, prioritizing value, and approving releases remain Product Owner responsibilities.

Question 49Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

A stakeholder repeatedly bypasses the Product Owner and asks developers to add features mid-Sprint. Which action best reflects the Scrum Master's role?

  1. Escalate to senior management to have the stakeholder removed from the project
  2. Allow the developers to add the features if they have spare capacity
  3. Coach the stakeholder and team on Scrum rules so requests flow through the Product Owner and backlog Correct answer.
  4. Instruct the developers to silently ignore all stakeholder requests

Explanation

The Scrum Master coaches the organization and stakeholders on Scrum, protecting the Sprint from unmediated scope changes. Requests should be routed through the Product Owner into the Product Backlog rather than injected directly.

Question 50Scrum roles and responsibilities (Product Owner, Scrum Master, Development Team)

The Product Owner wants to attend the Daily Scrum to check on progress. What is the most appropriate guidance?

  1. The Product Owner must be excluded because only developers may ever be present
  2. The Product Owner may attend, but the event is for the developers to inspect and plan their day Correct answer.
  3. The Product Owner should replace the Daily Scrum with a written status report
  4. The Product Owner should chair the meeting and assign each developer a task

Explanation

The Daily Scrum is for the developers to inspect progress toward the Sprint Goal and adapt their plan. The Product Owner is not required to attend but is not forbidden; if present, the developers still own the event.