Courseiva

CCNA Scrum Events Questions

49 questions · Scrum Events · All types, answers revealed

Practice these questionsDomain overviewAll questions
1
MCQhard

A newly formed Scrum Team is struggling to finish their Sprint Backlog items by the end of the time-boxed Sprint. The Product Owner demands that the Sprint duration be doubled to four weeks to accommodate their slow velocity. How should the Scrum Master respond?

A.Support the Product Owner by extending the Sprint duration to four weeks to provide immediate relief.
B.Facilitate a discussion with the team to investigate root causes of incomplete work and improve refinement.
C.Advise the team to work through weekends to finish the items so the Sprint length can remain unchanged.
D.Transfer the unfinished items back to the Product Backlog and cancel the remaining days of the Sprint.
AnswerB

Addressing root causes directly targets the delivery process bottlenecks rather than altering the rhythm of the framework. Fixing estimation, backlog refinement, and WIP limits empowers the team to meet goals within the established two-week or shorter time-box.

Why this answer

The Scrum Master should advise against extending the Sprint length, as fixed time-boxes limit risk and provide a predictable cadence for inspection and adaptation. Instead, the team should focus on improving estimation, refining backlog items, and reducing work in progress. Extending the Sprint reduces the frequency of feedback loops, directly undermining the empirical nature of Scrum and masking underlying delivery dysfunctions.

Exam trap

Candidates frequently fall into the trap of agreeing to extend Sprint durations to accommodate slow velocity, failing to recognize that this destroys rapid empirical feedback loops.

Practice this question →
2
MCQhard

A Scrum Team's Sprint Retrospective has become a recurring complaint session about the same issues, and no improvement actions are ever carried out. The Scrum Master wants the event to produce real change. What is the most appropriate approach?

A.Have the Scrum Master document all complaints and present them to management so they can assign owners for each action.
B.Shorten the Retrospective to 15 minutes so the team spends less time complaining and more time working.
C.Replace the Retrospective with a monthly all-hands meeting so leadership can drive the improvement priorities directly.
D.Help the team focus on one or two high-impact improvements and add them to the Sprint Backlog for the next Sprint.
AnswerD

The Sprint Retrospective exists to inspect how the last Sprint went and identify the most helpful changes to improve effectiveness. The most impactful changes should be addressed as soon as possible and may even be added to the next Sprint Backlog. Focusing on a small number of concrete actions gives the team a realistic chance to implement them and see results.

Why this answer

The Sprint Retrospective is where the Scrum Team inspects its way of working and identifies the most helpful changes. To produce real change, the team should select a small number of high-impact improvements and incorporate them into the next Sprint's work. This converts retrospective insight into concrete action and builds a habit of continuous improvement rather than repeated venting.

Exam trap

The trap here is assuming the Retrospective's value comes from listing many issues, when its real value comes from selecting a few improvements and acting on them.

Practice this question →
3
MCQmedium

A Scrum Team's Daily Scrum consistently runs 25 minutes because team members dive into technical problem-solving and design debates. The Scrum Master wants to keep the event within its 15-minute timebox while still enabling the Developers to adapt their plan. What is the most appropriate action?

A.Ask the Scrum Master to facilitate the Daily Scrum strictly, cutting off any developer who raises a technical concern.
B.Convert the Daily Scrum into a written status update in a chat channel so no meeting time is consumed by discussions.
C.Extend the Daily Scrum to 30 minutes permanently so the team has enough time to resolve all technical issues that arise.
D.End the Daily Scrum at 15 minutes and invite anyone with unresolved technical topics to stay for an optional follow-up discussion.
AnswerD

The Daily Scrum is timeboxed to 15 minutes regardless of team size, and the Developers own the event. Closing on time and offering an optional after-event for deeper technical conversations preserves the inspect-and-adapt purpose while preventing the daily event from becoming a design workshop. This keeps the cadence predictable and lets the team self-manage the extra discussion.

Why this answer

The Daily Scrum exists to inspect progress toward the Sprint Goal and adapt the Sprint Backlog, and it is timeboxed to 15 minutes. When technical debates consume the timebox, the Developers should end the event on schedule and continue detailed discussions afterward. This preserves both the timebox and the event's purpose without suppressing necessary technical collaboration.

Exam trap

The trap here is assuming that because the technical discussion is valuable, the Daily Scrum itself may be extended beyond its 15-minute timebox.

Practice this question →
4
MCQeasy

What is the primary purpose of the Daily Scrum for the Development Team?

A.To report individual task completion percentages directly to the Scrum Master and functional managers.
B.To inspect progress toward the Sprint Goal and create an actionable plan for the next 24 hours.
C.To negotiate new requirements and change requests directly with attending stakeholders and customers.
D.To perform comprehensive code reviews and architectural design planning for complex features.
AnswerB

Inspecting progress toward the goal and synchronizing the day's work are the core objectives defined in the Scrum Guide. This focused synchronization enables developers to adjust their tactics dynamically without losing sight of the overarching Sprint objective.

Why this answer

The Daily Scrum is a 15-minute time-boxed event for the Development Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a status report for management, but a tactical coordination meeting allowing developers to synchronize activities and plan their next 24 hours.

Exam trap

Many candidates treat the Daily Scrum as a status reporting meeting where developers justify their work to the Scrum Master or manager, rather than a planning session for the team's internal synchronization.

Practice this question →
5
MCQmedium

Halfway through a two-week Sprint, key market conditions shift drastically, rendering the current Sprint Goal completely obsolete. What is the most appropriate course of action?

A.The Development Team should continue executing the current Sprint Backlog until the two-week time-box expires.
B.The Product Owner has the authority to cancel the Sprint and start a new Sprint Planning event.
C.The Scrum Master must unilaterally decide whether to continue or terminate the current Sprint cycle.
D.Developers should privately split their time between the old Sprint Backlog and the new market requirements.
AnswerB

Only the Product Owner may cancel a Sprint, and doing so is warranted when the Sprint Goal becomes obsolete. Cancelling ends the Sprint, and the team then holds a new Sprint Planning event to select work aligned with the shifted market conditions.

Why this answer

When a Sprint Goal loses its meaning due to drastic external changes, continuing the Sprint is pointless because the resulting work will not deliver value. The Product Owner holds the unique authority to cancel the Sprint and immediately initiate a new planning cycle based on updated priorities.

Exam trap

Candidates mistakenly believe that only management or the entire team can cancel a Sprint, or that a Sprint must never be interrupted once started regardless of external circumstances.

Practice this question →
6
MCQhard

A team finds that the Sprint Review often turns into a status report meeting where the Developers read through their Jira boards. How should the Scrum Master intervene?

A.Advise the team to use a project management tool that generates automated reports.
B.Enforce a strict format where the team only talks about the Sprint Goal.
C.Coach the team to focus the event on demonstrating the increment and feedback.
D.Invite management to ensure the team feels pressured to show progress.
AnswerC

The primary purpose of the Sprint Review is the inspection of the increment and adaptation of the Product Backlog. By shifting the focus to a live demo and collaborative discussion, the team transforms the event from a boring status update into a valuable session that directly influences the product strategy.

Why this answer

The Sprint Review is a collaborative event focused on the product increment and feedback, not a status report. If the team is just reading boards, they miss the opportunity to demonstrate value and gather meaningful feedback. The Scrum Master must pivot the team's focus toward demonstrating the actual product increment and facilitating a conversation with stakeholders to ensure the product's direction remains aligned with user needs.

Exam trap

Test-takers often choose passive monitoring or cancelling the event altogether, failing to recognize the Scrum Master's active coaching duty to pivot the team toward value demonstrations and stakeholder feedback.

Practice this question →
7
Multi-Selectmedium

A Scrum Team is about to hold its Sprint Retrospective at the end of a challenging Sprint. Which TWO statements accurately describe the purpose and format of the Sprint Retrospective according to the Scrum Guide? (Choose two.)

Select 2 answers
A.The Sprint Retrospective concludes the Sprint and is timeboxed to a maximum of three hours for a one-month Sprint.
B.The Sprint Retrospective is optional if the team met its Sprint Goal and had no impediments during the Sprint.
C.The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
D.The Sprint Retrospective is attended only by the Scrum Master and Product Owner, who then report findings to the Developers.
E.The primary output of the Sprint Retrospective is an updated Product Backlog with newly prioritized items for the next Sprint.
AnswersA, C

The Scrum Guide states that the Sprint Retrospective concludes the Sprint and is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, it is usually shorter. This timebox allows the team to reflect and plan improvements without overrunning, and it formally closes the Sprint before the next one begins.

Why this answer

The Sprint Retrospective is a required event that concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint and is attended by the entire Scrum Team. Its purpose is to inspect the last Sprint and create a plan for improvements to be enacted during the next Sprint, often including adjustments to the Definition of Done.

Exam trap

The trap here is treating the Sprint Retrospective as an optional or leadership-only meeting rather than a required, whole-team inspect-and-adapt event.

Practice this question →
8
MCQmedium

A Scrum Team's Sprint Review consistently runs over its four-hour timebox for a one-month Sprint, with stakeholders engaging in lengthy debates about future features. The Scrum Master wants to improve the event. What should the Scrum Master do?

A.Coach the team and stakeholders on the purpose of the Sprint Review, which is to inspect the Increment and adapt the Product Backlog, and help them keep the event within its timebox.
B.Cancel the Sprint Review and replace it with a written status report distributed to stakeholders, since the meeting is too long.
C.Extend the Sprint Review timebox to six hours to allow all stakeholders to fully express their opinions and reach consensus on future features.
D.Limit attendance at the Sprint Review to only the Product Owner and Developers so that stakeholder debates can be avoided entirely.
AnswerA

The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. Its purpose is to inspect the Increment and adapt the Product Backlog, not to conduct lengthy feature debates. The Scrum Master should coach participants on this purpose and help them manage the discussion so the event stays within its timebox and remains productive.

Why this answer

The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. Its purpose is for the Scrum Team and stakeholders to inspect the Increment and adapt the Product Backlog. When discussions become lengthy and unfocused, the Scrum Master should coach participants on the event's purpose and help them manage the timebox, ensuring the event remains productive and within its limit.

Exam trap

The trap here is believing that the Sprint Review's timebox can be extended to accommodate extensive stakeholder debate rather than coaching participants to use the time effectively.

Practice this question →
9
Multi-Selecthard

A Scrum Team is distributed across three time zones. The Scrum Master wants to ensure the Daily Scrum remains effective and within its time-box. Which TWO actions are appropriate? (Choose two.)

Select 2 answers
A.Extend the time-box to thirty minutes when participants are joining remotely to accommodate connection delays.
B.Keep the Daily Scrum at the same time and place every working day to reduce complexity.
C.Allow the Developers to choose the structure and techniques they use, provided the event stays focused on progress toward the Sprint Goal.
D.Have the Scrum Master collect written status updates from each Developer beforehand and read them aloud during the event.
E.Require every Developer to answer the three classic questions in strict order to guarantee consistent information flow.
AnswersB, C

Scrum prescribes that the Daily Scrum is held at the same time and place every working day to reduce complexity. This consistency helps a distributed team build a reliable habit, minimizes scheduling confusion across time zones, and keeps the event focused on inspecting progress toward the Sprint Goal within its fifteen-minute time-box.

Why this answer

The Daily Scrum is owned by the Developers, who may choose any structure or technique that keeps the event focused on progress toward the Sprint Goal and within fifteen minutes. Holding it at the same time and place each working day reduces complexity and supports a reliable habit, which is especially valuable for distributed teams. Neither extending the time-box nor converting the event into a status report is consistent with Scrum.

Exam trap

The trap here is treating the three classic questions as a mandatory Scrum rule and extending the time-box for remote participants, when the framework only fixes the event's purpose, cadence, and fifteen-minute limit.

Practice this question →
10
Multi-Selecthard

Which TWO of the following statements are accurate regarding the Daily Scrum event? (Choose two.)

Select 2 answers
A.The event is strictly a 15-minute timeboxed status report delivered by the Developers to the Scrum Master and Product Owner.
B.The Developers can use any structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal.
C.If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they may participate as Developers in the event.
D.Management must attend to track individual task completion rates and update enterprise project management tools in real time.
E.Developers are strictly required to answer the three legacy questions regarding yesterday, today, and impediments every single day.
AnswersB, C

The Scrum Guide leaves the specific format of the Daily Scrum up to the Developers. As long as they inspect progress toward the Sprint Goal and adjust the upcoming work plan, any effective technique is completely acceptable.

Why this answer

The Daily Scrum is an internal inspection event for the Developers to synchronize activities and create a actionable plan for the next 24 hours. Because it belongs to them, external stakeholders do not dictate its agenda, and adherence to a strict rigid format is secondary to achieving synchronization and adaptation toward the Sprint Goal.

Exam trap

Many test-takers confuse the Daily Scrum with a status reporting meeting for management, or mistakenly believe the three traditional questions are legally mandated by the Scrum Guide.

Practice this question →
11
MCQmedium

During the Sprint Retrospective, the Scrum Team identifies a major systemic impediment involving company HR policies that is slowing down delivery. What should the Scrum Master do?

A.Instruct the team to ignore HR policies because Scrum rules supersede all standard corporate governance and compliance frameworks.
B.Take accountability for resolving the organizational impediment by collaborating with leadership to influence changes outside the team.
C.Discard the impediment from the Retrospective action plan because organizational culture changes are strictly impossible to achieve.
D.Mandate that the Product Owner rewrite the Product Backlog to include tasks specifically assigned to HR department personnel.
AnswerB

Organisational impediments spanning HR policy sit outside the team's authority, so the Scrum Master must own the resolution by engaging leadership and influencing change beyond the team boundary. This satisfies the retrospective's systemic impediment, which the team alone cannot remove.

Why this answer

The Scrum Master serves the organization by leading, training, and coaching in Scrum adoption, which includes helping remove organizational barriers. When impediments lie outside the team's immediate sphere of control, the Scrum Master must champion the issue upward, working with organizational leaders to enact structural changes that enable high performance.

Exam trap

Candidates often think the Scrum Master should tell the team to work around HR policies, ignoring the duty to address systemic organizational impediments.

Practice this question →
12
Multi-Selectmedium

Which TWO of the following are true regarding the Daily Scrum?

Select 2 answers
A.It is a mandatory event for the Product Owner to track task completion.
B.It is a 15-minute event for the Developers to inspect progress toward the Sprint Goal.
C.It is a forum for the Scrum Master to assign tasks to the Developers.
D.It is a planning session to adapt the Sprint Backlog for the next 24 hours.
E.It is used to update the stakeholder on the team's velocity and burndown charts.
AnswersB, D

The Daily Scrum is strictly timeboxed to 15 minutes. Its primary purpose is for the Developers to inspect their current progress toward the Sprint Goal and adapt their plan for the next 24 hours. This keeps the team aligned and ensures they are working on the most important tasks.

Why this answer

The Daily Scrum is a brief, 15-minute event for Developers to synchronize their work and adjust their plan for the next 24 hours. It is critical for transparency and immediate adaptation. Understanding these two truths—that it is for the Developers and that it is for planning, not status reporting—is essential for maintaining the autonomy and focus of the Scrum Team during the Sprint.

Exam trap

Many students select answers describing the Daily Scrum as a status report for management or a detailed multi-hour problem-solving session, confusing its true purpose as a short planning event for developers.

Practice this question →
13
MCQmedium

A Scrum Team is halfway through a two-week Sprint. The Scrum Master notices that the Developers have stopped holding the Daily Scrum because they say it interrupts their flow. What is the most appropriate action for the Scrum Master to take?

A.Coach the Developers on the purpose and structure of the Daily Scrum, and help them reinstate it as a daily event.
B.Replace the Daily Scrum with a weekly status meeting led by the Scrum Master to reduce disruption to the Developers' work.
C.Allow the Developers to skip the Daily Scrum if they demonstrate that they are self-managing and communicating continuously.
D.Escalate the issue to the Product Owner so that the Product Owner can require the Developers to attend the Daily Scrum.
AnswerA

The Daily Scrum is a required Scrum event that the Developers use to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. The Scrum Master serves the Scrum Team by coaching them on Scrum theory and practices. Reinstating the event through coaching aligns with the Scrum Master's accountability for the Scrum Team's effectiveness.

Why this answer

The Daily Scrum is a mandatory daily event owned by the Developers, used to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. When a team abandons it, the Scrum Master should coach them on its purpose and help them restore it. Allowing omission, escalating to the Product Owner, or substituting a weekly meeting all violate Scrum principles and fail to address the root cause.

Exam trap

The trap here is assuming that a self-managing team can simply drop a required Scrum event if they feel it disrupts their flow.

Practice this question →
14
MCQmedium

During the Sprint Planning event, the Development Team realizes they have pulled in significantly more Product Backlog items than their historical velocity supports. What is the most appropriate action according to Scrum principles?

A.Quietly work overtime throughout the upcoming Sprint to ensure all selected items are successfully completed.
B.Collaborate with the Product Owner to negotiate and remove items until the forecast matches their actual capacity.
C.Keep all items in the Sprint Backlog and allow the Scrum Master to assign tasks to individual developers.
D.Immediately cancel the entire Sprint and restart the Sprint Planning meeting with a brand new Product Owner.
AnswerB

Sprint Planning is a collaborative negotiation where the Development Team forecasts what can be delivered based on past performance and current capacity. Adjusting the scope early guarantees that the resulting Sprint Goal remains achievable and maintains team accountability.

Why this answer

Scrum relies on transparency and realistic forecasting to establish a sustainable cadence. The Development Team must collaborate immediately with the Product Owner to right-size the Sprint Backlog before finalizing the plan. This ensures the team commits only to work they can realistically complete, maintaining predictability and avoiding burnout.

Exam trap

Candidates often think the Development Team must work overtime or simply lower their quality standards to complete an overcommitted forecast, rather than negotiating capacity directly with the Product Owner.

Practice this question →
15
MCQmedium

A Scrum Team finishes Sprint Planning with a clear Sprint Goal and a set of selected Product Backlog items. Two days into the Sprint, a Developer identifies a better technical approach that would change the composition of the Sprint Backlog while still achieving the Sprint Goal. What should the team do?

A.Cancel the Sprint and start a new one so the revised plan can be properly planned and committed to from the beginning.
B.Update the Sprint Backlog to reflect the new approach, since the Sprint Backlog is owned by the Developers and may be adjusted as long as the Sprint Goal is not endangered.
C.Continue with the original Sprint Backlog unchanged to preserve the Sprint's original forecast and avoid scope churn.
D.Call an emergency Sprint Planning session with the Product Owner to formally re-baseline the Sprint Backlog before any work changes.
AnswerB

The Sprint Backlog is a plan by and for the Developers and is updated throughout the Sprint as more is learned. Because the Sprint Goal remains achievable, the Developers are empowered to change the plan without seeking outside permission, keeping the Sprint Goal as the fixed target.

Why this answer

The Sprint Backlog belongs to the Developers and is expected to change as they learn more during the Sprint. Because the Sprint Goal stays viable, the Developers can revise their plan without permission from the Product Owner or Scrum Master. Re-planning via a new Sprint Planning event or canceling the Sprint is unnecessary and not supported by Scrum.

Exam trap

The trap here is assuming the Sprint Backlog is a fixed commitment that requires Product Owner approval to change, when in fact only the Sprint Goal is fixed during the Sprint.

Practice this question →
16
MCQhard

A powerful stakeholder demands to attend the Daily Scrum to report on budget updates and track individual task progress. As the ScrumMaster, how should you address this request?

A.Permit the stakeholder to join silently provided they do not interrupt the team's individual status updates.
B.Welcome the stakeholder enthusiastically and allocate the first five minutes for them to present budget reports.
C.Explain the purpose of the event to the stakeholder, clarify that attendance is limited to the Development Team, and invite them to the Sprint Review instead.
D.Reschedule the Daily Scrum to a confidential room so that external stakeholders cannot locate the meeting.
AnswerC

Explaining the event's purpose and restricting attendance to the Development Team preserves the Daily Scrum as a focused inspection-and-adaptation event for the Developers. Redirecting the stakeholder to the Sprint Review satisfies their budget and progress interest through the appropriate inspect-and-adapt forum.

Why this answer

The Daily Scrum is an internal inspection and adaptation event solely for the Development Team to plan their next 24 hours. Allowing external stakeholders to hijack the event turns it into a status-reporting meeting, destroying its core purpose and psychological safety for the practitioners.

Exam trap

Test-takers frequently assume stakeholders should attend daily meetings for transparency, or they choose to let them stay quietly, violating the rule that the Daily Scrum is strictly an internal event for Developers.

Practice this question →
17
MCQhard

Refer to the exhibit. A newly appointed Scrum Master reviews this configuration summary for the Sprint Review event. Which element represents a violation of official Scrum principles?

A.Allowing external quality auditors and invited stakeholders to attend and provide direct feedback to the Scrum Team.
B.Restricting the primary activity solely to demonstrating the completed increment without collaborative discussion on backlog adaptation.
C.Allocating a 4-hour maximum timebox for a standard one-month Sprint duration as defined in the configuration.
D.Requiring the presence of both the Product Owner and the Developers alongside stakeholders during the review session.
AnswerB

The Sprint Review exists to inspect the increment and adapt the Product Backlog collaboratively with stakeholders. Limiting it to a demonstration with no discussion on backlog adaptation removes that empirical inspection and adaptation, violating Scrum's defined purpose for the event.

Why this answer

The Sprint Review is a collaborative working session where the Scrum Team and stakeholders inspect the outcome of the Sprint and discuss future adaptations. While the timebox of up to 4 hours for a 1-month sprint is correct and the attendee list is fully compliant, treating the event merely as a one-way demonstration rather than a collaborative working session violates its spirit.

Exam trap

Test-takers frequently miss the subtle distinction that the Sprint Review is an inspection and adaptation working session, not just a formal software demo for presentation.

Practice this question →
18
MCQeasy

Which statement best describes the primary purpose of the Sprint Retrospective?

A.To demonstrate the increment to stakeholders and gather feedback on the product.
B.To identify improvements to increase the quality and effectiveness of the team.
C.To plan the work for the upcoming Sprint and define the new Sprint Goal.
D.To provide a status update to management regarding the team's velocity.
AnswerB

The Retrospective is the Scrum event intended for the team to inspect their working processes and identify concrete ways to improve. This ensures the team continuously evolves its practices. By creating actionable items for the next Sprint, the team ensures that learning is translated into real-world efficiency and effectiveness.

Why this answer

The Sprint Retrospective is the event dedicated to process improvement. By inspecting how the last Sprint went regarding people, relationships, processes, and tools, the team identifies actionable improvements. This is a critical feedback loop for the team's professional growth and velocity improvement.

Without this dedicated time for self-reflection, teams are prone to repeating the same mistakes and failing to leverage their collective experience to become more efficient.

Exam trap

Candidates frequently confuse the Sprint Retrospective with the Sprint Review, selecting answers focused on inspecting product features or stakeholder feedback instead of internal process improvement.

Practice this question →
19
MCQhard

A Scrum Team's Sprint Review has evolved into a one-way presentation where the Developers demo completed work and stakeholders remain silent. The Product Owner wants the event to better fulfill its purpose. Which approach best aligns with Scrum?

A.Replace the Sprint Review with a written status report distributed to stakeholders, since stakeholders prefer not to attend meetings.
B.Have the Scrum Master lead the Sprint Review and present the Increment on behalf of the Developers to keep the session efficient.
C.Convert the Sprint Review into a collaborative working session where the Scrum Team and stakeholders inspect the Increment and discuss what to do next.
D.Extend the Sprint Review timebox so the Developers can present every completed Product Backlog item in full detail.
AnswerC

The Sprint Review is a working session, not a demonstration. Its purpose is to inspect the Increment and adapt the Product Backlog based on stakeholder feedback. Encouraging collaboration and discussion about what to do next directly supports empiricism and maximizes value, which is exactly what the Product Owner should facilitate.

Why this answer

The Sprint Review exists so the Scrum Team and stakeholders can inspect the Increment and collaborate on what to do next. Turning it into a one-way presentation defeats its purpose. The best remedy is to make it a working session with active stakeholder participation.

Extending the timebox, replacing it with a report, or having the Scrum Master present all undermine the event's empirical foundation and reduce its value.

Exam trap

The trap here is treating the Sprint Review as a formal demo or status report rather than a collaborative inspection and adaptation session.

Practice this question →
20
MCQmedium

At the Sprint Review, an important stakeholder expresses dissatisfaction with a core feature delivered by the Development Team, stating it does not solve their current business workflow. How should this feedback be handled?

A.Ignore the feedback because the Development Team strictly followed the requirements provided in the initial backlog.
B.Scold the Development Team for failing to understand the business needs during Sprint Planning.
C.Capture the stakeholder feedback as new items in the Product Backlog for the Product Owner to prioritize.
D.Suspend the release pipeline and force the team to rewrite the entire feature before leaving the room.
AnswerC

Feedback at the Sprint Review is not a change request to action immediately; it is new information. Logging it in the Product Backlog lets the Product Owner weigh it against other items and re-prioritise, preserving the team's sprint commitment and the Product Owner's sole authority over backlog ordering.

Why this answer

The Sprint Review is a working session designed to inspect the Increment and adapt the Product Backlog based on stakeholder feedback. Discontent from stakeholders indicates a shift in understanding or requirements, which the Product Owner must capture and incorporate into the Product Backlog as new items. This feedback loop validates the empirical nature of Scrum, ensuring the product evolves to meet real market needs.

Exam trap

Candidates often assume the disgruntled stakeholder can immediately rewrite the current Increment or force changes mid-Sprint, forgetting that all new work must go through the Product Owner for backlog prioritization.

Practice this question →
21
MCQmedium

During the Sprint Planning event, the Development Team realizes they have overcommitted by pulling in too many Product Backlog items. What is the most appropriate course of action according to Scrum principles?

A.Automatically extend the duration of the current Sprint to accommodate the remaining workload without changing the goal.
B.Collaborate with the Product Owner to negotiate and remove items from the Sprint Backlog until the forecast matches their actual capacity.
C.Work mandatory overtime hours throughout the Sprint to ensure all originally selected Product Backlog items are successfully completed.
D.Immediately cancel the Sprint and schedule a completely new Sprint Planning session for the following week.
AnswerB

Scrum expects the Development Team to forecast realistically and self-manage its Sprint Backlog. Collaborating with the Product Owner to remove items until the forecast matches actual capacity satisfies the stem's overcommitment scenario, preserving a sustainable pace and protecting Sprint Goal quality rather than silently dropping work.

Why this answer

Sprint Planning requires the team to forecast work they can realistically achieve based on historical capacity. When overcommitment becomes clear, collaboration with the Product Owner is essential to adjust the plan. This ensures sustainability, protects team morale, and maintains a transparent view of delivery expectations without compromising quality standards.

Exam trap

Examinees often mistakenly believe the team must work overtime to meet an overcommitted plan, or that the Scrum Master unilaterally removes items, rather than requiring collaborative negotiation between the Developers and Product Owner.

Practice this question →
22
MCQhard

During a Sprint Retrospective, the team identifies a major impediment involving company-wide HR policies that restrict cross-functional collaboration. The team feels helpless to change it. What should the Scrum Master do?

A.Tell the team to ignore the HR policies and work around them without seeking management support.
B.Take ownership of the impediment and collaborate with organizational leaders to drive systemic change.
C.Remove the impediment from the Retrospective action items because it falls outside the Scrum Team control.
D.Instruct the Product Owner to rewrite the Product Backlog items to avoid cross-functional dependencies.
AnswerB

Escalate the impediment beyond the team's authority by engaging organisational leadership, since HR policy sits outside the Scrum Team's control. The Scrum Master owns removing impediments, and systemic, company-wide constraints require influencing decision-makers rather than expecting the team to resolve what they cannot change.

Why this answer

The Scrum Master serves as a servant-leader who helps remove impediments that lie outside the team immediate sphere of influence. When systemic organizational roadblocks prevent agility, the Scrum Master must engage with broader leadership and HR to advocate for structural changes. Empowering the team means taking ownership of these macro impediments while coaching the organization toward agile maturity and removing systemic waste.

Exam trap

Candidates often choose passive answers like telling the team to just accept organizational rules, or incorrectly expect developers to resolve macro-level company policies themselves.

Practice this question →
23
MCQhard

A Scrum Team has experienced low stakeholder attendance at their Sprint Reviews for three consecutive iterations. The Developers suggest canceling the Sprint Review and instead sending a written progress report via email. How should the Scrum Master respond?

A.Approve the email report format temporarily, provided the stakeholders reply with their written feedback within forty-eight hours.
B.Facilitate a discussion with the Product Owner and team to discover why stakeholders are absent, coaching them to demonstrate tangible value.
C.Escalate the stakeholder absence to senior management and mandate their attendance at all future Sprint Reviews through company policy.
D.Agree to cancel the Sprint Review and allocate those four hours directly to the Developers for additional refactoring and technical debt reduction.
AnswerB

Low stakeholder attendance indicates a deeper problem regarding the perceived value of the event or poor stakeholder management. The Scrum Master must address the root cause by helping the Product Owner communicate the strategic importance of the inspect-and-adapt session.

Why this answer

The Sprint Review is a collaborative inspect-and-adapt event designed for active stakeholder engagement and feedback, not a status reporting meeting. Replacing it with an email destroys transparency and eliminates the empirical loop. The Scrum Master must coach the team and Product Owner on engaging stakeholders effectively rather than bypassing the core event.

Exam trap

Candidates often suggest replacing the event with documentation or email. This ignores the core Scrum principle of empiricism, which requires live inspection and adaptation with stakeholders to provide real value.

Practice this question →
24
MCQmedium

A Product Owner frequently introduces new high-priority requirements directly to the Development Team mid-Sprint, claiming urgent customer needs. The Development Team feels pressured and struggles to meet their Sprint Goal. Which Scrum event is specifically designed to prevent this anti-pattern?

A.The Daily Scrum provides a daily negotiation platform for the Product Owner to inject new backlog items.
B.Sprint Planning creates a fixed commitment for the Sprint, preventing unauthorized mid-Sprint scope changes.
C.The Sprint Review allows stakeholders to renegotiate the scope of the current ongoing iteration dynamically.
D.Backlog Refinement sessions allow the Product Owner to push urgent tasks directly into the active Sprint Backlog.
AnswerB

Sprint Planning establishes a binding agreement between the Product Owner and Development Team regarding the Sprint scope. This clear boundary protects the team from chaotic requirement churn and ensures stable focus on delivering working increments.

Why this answer

Sprint Planning establishes the Sprint Goal and the work needed to achieve it, creating a protective boundary around the team. Mid-Sprint scope injections violate this boundary, and the Scrum Master must coach the organization to utilize refinement and upcoming planning sessions for requirement adjustments.

Exam trap

Candidates often choose answers that suggest managing mid-Sprint requirements through backlog refinement or urgent negotiation, forgetting that Sprint Planning creates the initial protective boundary and commitment that prevents these unauthorized scope changes altogether.

Practice this question →
25
MCQeasy

A Scrum Team is new to Scrum and asks the Scrum Master to clarify the purpose of the Daily Scrum. Which statement best describes why the Developers hold this event every day?

A.To inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed.
B.To give the Product Owner a daily update on which Product Backlog items have been completed.
C.To report individual task status to the Scrum Master so that progress can be tracked and recorded.
D.To allow stakeholders to ask questions and provide feedback on the team's daily work.
AnswerA

The Daily Scrum exists so the Developers can inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is a short, daily opportunity to re-plan the next 24 hours of work. This focus on inspection and adaptation is what makes the event valuable and distinguishes it from a status report.

Why this answer

The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a status report to the Scrum Master, Product Owner, or stakeholders. Its value lies in daily inspection and adaptation that keeps the team focused on the Sprint Goal.

Exam trap

The trap here is confusing the Daily Scrum's inspect-and-adapt purpose with a status-reporting ritual directed at someone outside the Developers.

Practice this question →
26
MCQmedium

A Scrum Team's Daily Scrum has become a 30-minute problem-solving session where Developers dive into technical design debates. The Scrum Master wants to refocus the event on its intended purpose. What should the Scrum Master do?

A.Have the Scrum Master facilitate the Daily Scrum and assign each Developer a turn to report status to keep the meeting on track.
B.Teach the Developers that the Daily Scrum is a 15-minute event for inspecting progress toward the Sprint Goal and adapting the Sprint Backlog as needed.
C.Extend the Daily Scrum to 30 minutes to accommodate the technical discussions so the team does not lose valuable problem-solving time.
D.Cancel the Daily Scrum and replace it with a weekly technical design meeting, since the Developers already communicate continuously.
AnswerB

The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a problem-solving session. By coaching the team on this purpose and timebox, the Scrum Master helps them keep the event focused and use separate conversations for detailed technical discussions.

Why this answer

The Daily Scrum exists for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is timeboxed to 15 minutes and is not a status report or a design workshop. The Scrum Master serves the team by coaching them on this purpose, helping them keep the event focused, and encouraging detailed discussions to happen outside the timebox.

Exam trap

The trap here is confusing the Daily Scrum's inspect-and-adapt purpose with a general team meeting where any topic can be discussed at length.

Practice this question →
27
MCQhard

During a Sprint Review, a stakeholder asks the Developers to add a new high-priority feature to the current Sprint Backlog so it can be demonstrated at the next Sprint Review. The Product Owner is present. What is the most appropriate action for the Scrum Master to take?

A.Escalate the request to the Scrum Master's manager to decide whether the feature should be added to the current Sprint.
B.Remind the team that the Sprint Backlog is owned by the Developers and that new work should be negotiated with the Product Owner for future Sprints, while the current Sprint Goal remains protected.
C.Instruct the Developers to add the feature immediately, since the Sprint Review is the official inspect-and-adapt event where stakeholders provide input.
D.Tell the stakeholder that no changes can ever be made during a Sprint and that the feature must wait until the next Sprint Planning regardless of its priority.
AnswerB

The Sprint Backlog is owned by the Developers, and the Sprint Goal should not be jeopardized by adding scope mid-Sprint without careful consideration. The Product Owner manages the Product Backlog and can collaborate with the Developers to renegotiate scope if needed, but the Scrum Master should protect the Sprint Goal and ensure changes are handled transparently, not imposed by stakeholders during the Sprint Review.

Why this answer

The Sprint Backlog is owned by the Developers, and the Sprint Goal provides focus for the Sprint. While the Product Owner manages the Product Backlog and can collaborate with the Developers to renegotiate scope, stakeholders do not directly assign work during the Sprint Review. The Scrum Master should protect the Sprint Goal and ensure changes are handled through the appropriate Scrum roles and events.

Exam trap

The trap here is assuming that because the Sprint Review is an inspect-and-adapt event, stakeholders can directly add work to the current Sprint.

Practice this question →
28
MCQhard

During a Sprint Review, the Product Owner presents the current state of the Product Backlog and projected delivery dates based on the team's recent velocity. A stakeholder challenges the accuracy of these projections, and the Developers begin defending their estimates. How should the Scrum Master facilitate the remainder of the event?

A.End the Sprint Review early, since the disagreement indicates the event is no longer productive.
B.Refocus the discussion on the Increment and the feedback it generates, reminding participants that projections are the Product Owner's responsibility and that the Review is for inspection and adaptation.
C.Ask the Developers to leave the meeting so the Product Owner and stakeholders can negotiate delivery dates privately.
D.Step in and provide a definitive delivery date based on the team's historical velocity to settle the disagreement.
AnswerB

The Sprint Review is a working session for inspecting the Increment and adapting the Product Backlog, not for defending estimates. The Scrum Master facilitates by refocusing the group on the product and its feedback, while clarifying that projections belong to the Product Owner. This keeps the event productive and preserves stakeholder collaboration.

Why this answer

The Sprint Review is a collaborative working session where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog. The Scrum Master facilitates by keeping the focus on product inspection and feedback, while recognizing that delivery projections are the Product Owner's responsibility. Defending estimates or removing the Developers undermines the event's purpose.

Exam trap

The trap here is treating the Sprint Review as a negotiation or status meeting where the Scrum Master should resolve estimate disputes, rather than a collaborative inspection of the Increment.

Practice this question →
29
MCQmedium

A Scrum Team is midway through a one-month Sprint when the Product Owner identifies a critical market shift that makes the current Sprint Goal obsolete. The Developers are split on the best response. The Scrum Master wants to ensure the team follows the Scrum framework. What is the most appropriate action?

A.Have the Product Owner cancel the Sprint and initiate a new Sprint Planning event to establish a new Sprint Goal.
B.Wait until the Sprint Review to present the Increment and let stakeholders decide whether to change direction.
C.Ask the Scrum Master to cancel the Sprint and immediately reassign the Developers to new tasks without a Sprint Planning event.
D.Continue the Sprint as planned because the Sprint Goal was agreed upon and cannot be changed mid-Sprint.
AnswerA

The Product Owner has the authority to cancel a Sprint when the Sprint Goal becomes obsolete. Canceling allows the team to stop work that no longer delivers value and to replan. After cancellation, the team holds a Sprint Review to inspect the completed work and then a Sprint Retrospective, followed by Sprint Planning for a new Sprint. This aligns with Scrum's empirical approach.

Why this answer

The Product Owner is the sole authority to cancel a Sprint when the Sprint Goal becomes obsolete. Canceling stops investment in work that no longer delivers value and allows the team to replan through a new Sprint Planning event. The Scrum Master facilitates the process but does not cancel the Sprint.

Waiting until the Sprint Review or continuing as planned both ignore the empirical opportunity to adapt early.

Exam trap

The trap here is assuming the Scrum Master or the Developers can cancel the Sprint, or that the Sprint Goal is fixed and cannot be abandoned mid-Sprint.

Practice this question →
30
MCQhard

A Scrum Team has a two-week Sprint. During Sprint Planning, the Developers estimate that they can complete 8 Product Backlog items. However, the Product Owner insists on adding 3 more items to meet a stakeholder request, even though the Developers believe this exceeds their capacity. The Scrum Master is facilitating. What should the Scrum Master do?

A.Allow the Product Owner to add the items, but plan to work overtime to meet the commitment.
B.Instruct the Developers to accept the additional items because the Product Owner represents the stakeholder's interests.
C.Facilitate a discussion so the Developers and Product Owner agree on a realistic Sprint Goal and a set of items the Developers are confident they can complete.
D.Escalate the disagreement to the stakeholders so they can decide which items should be included in the Sprint.
AnswerC

The Scrum Master should coach the team to collaborate and reach a shared understanding. The Developers have the final say on how much work they can take on, but the Product Owner provides the value context. Facilitating a negotiation helps align expectations, protects the Developers' capacity, and ensures the Sprint Goal is realistic. This approach respects self-management while addressing the stakeholder's needs through prioritization.

Why this answer

The Developers are responsible for determining how much work they can take on during Sprint Planning. The Product Owner may negotiate and prioritize, but cannot unilaterally impose more work than the Developers believe is feasible. The Scrum Master facilitates collaboration to reach a realistic Sprint Goal.

Escalation or forced overtime undermines self-management and empiricism, and does not address the root issue of capacity versus stakeholder demand.

Exam trap

The trap here is thinking the Product Owner has the authority to dictate how many items the Developers must accept in a Sprint, or that the Scrum Master should decide for them.

Practice this question →
31
Multi-Selectmedium

Which TWO statements accurately describe the Sprint Review event in Scrum? (Choose TWO)

Select 2 answers
A.It is a formal gatekeeping presentation where management approves or rejects the team performance.
B.It is a collaborative working session with stakeholders to inspect the Increment and adapt the backlog.
C.It is strictly time-boxed to a maximum of four hours for a one-month Sprint.
D.It is primarily used by the Scrum Master to evaluate individual developer velocity and productivity.
E.It replaces the need for continuous communication and stakeholder engagement throughout the Sprint.
AnswersB, C

Collaboration and adaptation are at the heart of the Sprint Review. Stakeholders and the Scrum Team inspect what was built, discuss market shifts, and collaboratively update the Product Backlog to guide future development.

Why this answer

The Sprint Review is a collaborative session where the Scrum Team and stakeholders inspect the Increment resulting from the Sprint and discuss adjustments to the Product Backlog. It is explicitly designed as a working session, not a formal presentation or slide deck demonstration, fostering collaborative dialogue between creators and consumers of the product to maximize future value delivery.

Exam trap

Candidates often mistake the Sprint Review for a formal slide-deck presentation or a gatekeeper status report meant strictly for approving management sign-offs.

Practice this question →
32
MCQeasy

During the Daily Scrum, a Developer begins a lengthy technical debate with the QA engineer regarding the root cause of a complex architectural bug. What is the most appropriate action for the Scrum Master?

A.Allow the debate to continue until a definitive architectural consensus is reached, extending the Daily Scrum timebox accordingly.
B.Intervene immediately to remind the team that the Daily Scrum is for synchronization, and ask them to schedule a separate breakout session.
C.Resolve the technical dispute personally by making a final architectural decision based on your past engineering experience.
D.Cancel the remainder of the Daily Scrum and instruct the entire team to join the impromptu technical troubleshooting session.
AnswerB

The Scrum Master ensures that all Scrum events take place and are kept within their timeboxes. By redirecting deep technical debates into offline discussions, the Scrum Master preserves the primary synchronization purpose and respects the fifteen-minute limit.

Why this answer

The Daily Scrum is a strict fifteen-minute timeboxed event for the Developers to synchronize activities and create a plan for the next twenty-four hours. Lengthy technical deep-dives derail the meeting and exclude other team members. The Scrum Master should remind the participants to park the discussion and schedule a separate follow-up session immediately after.

Exam trap

Candidates often assume the Scrum Master should facilitate the debate or participate to solve the technical problem, rather than strictly enforcing the timebox and keeping the meeting focused on synchronization.

Practice this question →
33
Multi-Selectmedium

A Scrum Team is about to hold its Sprint Planning event. The Product Owner and Developers want to ensure the event fulfills its purpose. Which TWO of the following statements accurately describe Sprint Planning? (Choose two.)

Select 2 answers
A.Only the Developers attend Sprint Planning, since they are the ones doing the work and estimating the effort.
B.Sprint Planning produces a fixed, unchangeable Sprint Backlog that cannot be modified until the Sprint ends.
C.The Scrum Master is solely responsible for creating the Sprint Goal and presenting it to the Developers for approval.
D.Sprint Planning addresses three topics: why the Sprint is valuable, what can be done in the Sprint, and how the chosen work will get done.
E.Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint, and the event may be shorter for shorter Sprints.
AnswersD, E

The Scrum Guide defines Sprint Planning around three topics: the Why (Sprint Goal), the What (Product Backlog items selected), and the How (a plan for delivering them). This structure ensures the team aligns on value, scope, and approach before the Sprint begins. Covering all three topics is essential for a coherent Sprint Backlog and a shared Sprint Goal.

Why this answer

Sprint Planning is a collaborative event where the Scrum Team defines the Sprint Goal (Why), selects Product Backlog items (What), and plans how to deliver them (How). It is timeboxed to eight hours for a one-month Sprint and may be shorter for shorter Sprints. The Sprint Backlog produced is a living plan that the Developers update as they learn.

Exam trap

The trap here is assuming Sprint Planning produces a frozen Sprint Backlog, when in fact the Developers adapt it throughout the Sprint.

Practice this question →
34
MCQmedium

During a Sprint Review, a stakeholder expresses disappointment that a specific feature was not included in the increment. What is the most appropriate response?

A.Apologize and promise to include the feature in the next Sprint.
B.Ask the team to work overtime to finish the feature immediately.
C.Discuss the feature and update the Product Backlog to reflect the feedback.
D.Defend the team by explaining why the stakeholder's request was not a priority.
AnswerC

The Sprint Review is designed for collaboration between the team and stakeholders. The Product Owner should document the feedback and prioritize it within the Product Backlog. This transparent approach ensures the stakeholder is heard and that the product's future is aligned with the most valuable items based on recent feedback.

Why this answer

The Sprint Review is a collaborative event for inspecting the outcome of the Sprint and adapting the Product Backlog. It is the perfect opportunity to align expectations based on the work actually completed. By acknowledging the stakeholder's input and updating the Product Backlog, the Product Owner maintains transparency and ensures the stakeholder's needs are reflected in future planning, keeping the product direction synchronized with market demands.

Exam trap

Candidates often select answers that involve modifying the current Sprint Backlog immediately, or incorrectly stopping the review, rather than recognizing that feedback belongs in the Product Backlog for future planning.

Practice this question →
35
MCQmedium

At the start of Sprint Planning, the Product Owner presents a set of high-priority items, but the Developers realize they lack sufficient clarity on user expectations to commit to a realistic Sprint Goal. What is the best course of action?

A.Proceed with planning by guessing the missing requirements to avoid delaying the start of the new Sprint cycle.
B.Refuse to pull the items into the Sprint and demand that the Product Owner rewrite them alone before the next daily meeting.
C.Collaborate with the Product Owner during Sprint Planning to clarify the items, negotiate scope, and formulate a viable Sprint Goal.
D.Permanently remove all Sprint Planning events from future iterations and replace them with continuous on-demand kanban flow.
AnswerC

Sprint Planning is collaborative. The Scrum team defines a Sprint Goal that communicates why the Sprint is valuable. If items lack clarity, the team works with the Product Owner right then to refine them sufficiently for commitment.

Why this answer

Sprint Planning requires a clear understanding of the proposed work and its value. If items lack clarity, the Developers must collaborate with the Product Owner during the event to refine them, or adjust the scope. While Product Backlog refinement is ongoing, the team cannot plan effectively with ambiguous requirements, necessitating immediate real-time clarification.

Exam trap

Candidates often think the team should postpone the Sprint or refuse to start until the Product Owner brings perfectly refined items, ignoring the collaborative nature of planning and scope negotiation.

Practice this question →
36
MCQmedium

During the Sprint Review, a key stakeholder inspects the Increment and states that a major feature implemented by the Developers does not align with their actual business workflow. However, the feature strictly meets all acceptance criteria defined in the Product Backlog item. How should this situation be handled?

A.Reject the stakeholder's feedback because the Developers successfully met all written acceptance criteria during the Sprint.
B.Scold the Product Owner for failing to write comprehensive acceptance criteria and demand that the feature be rewritten immediately.
C.Acknowledge the valuable feedback, and have the Product Owner create new Product Backlog items to address the workflow adjustment.
D.Immediately halt the Sprint Review and force the Developers to refactor the feature before allowing stakeholders to leave.
AnswerC

The Increment met its acceptance criteria, so the Developers built it correctly; the mismatch is a product-level discovery, not a defect. The Product Owner owns the Product Backlog, so capturing the workflow adjustment as new items lets the stakeholder's feedback enter the backlog for future Sprints rather than reopening finished work.

Why this answer

The Sprint Review is designed for inspection and adaptation. When a stakeholder provides feedback revealing a mismatch between written requirements and real-world utility, the Scrum Team must embrace empiricism. The Product Owner creates new Product Backlog items to address the workflow gap, ensuring continuous alignment with customer needs.

Exam trap

Candidates often assume the team failed because they didn't follow the requirements, forgetting that the Sprint Review is for discovering if the built product actually solves the user's problem.

Practice this question →
37
MCQmedium

During a Sprint Planning event, the Developers realize they have overcommitted and selected more items from the Product Backlog than they can realistically complete. What is the most appropriate action according to Scrum rules?

A.The Scrum Master must unilaterally remove the lowest priority items from the Sprint Backlog to protect the team's velocity.
B.The Developers collaborate with the Product Owner to adjust the selected Product Backlog items, reducing the scope to fit their actual capacity.
C.The team must extend the length of the Sprint to accommodate the extra work without altering the Product Backlog item selection.
D.The Product Owner cancels the Sprint immediately and calls an emergency planning session for the following morning.
AnswerB

The Developers can negotiate the scope of the Sprint Backlog with the Product Owner throughout Sprint Planning as capacity becomes clearer. This collaborative adjustment ensures the team commits only to what is feasible while maintaining alignment with the overall Product Goal.

Why this answer

The Developers are solely responsible for sizing and selecting work during Sprint Planning based on their capacity. If they realize an overcommitment, they must collaborate with the Product Owner to adjust the Sprint Backlog scope before the meeting ends. This protects team sustainability and ensures a realistic Sprint Goal can be achieved without compromising quality.

Exam trap

Candidates often assume management or the Scrum Master must step in to forcibly remove items, forgetting that the Developers own their capacity and forecast.

Practice this question →
38
MCQmedium

If the Sprint Retrospective runs over its timebox, what should the Scrum Master do?

A.Allow the meeting to continue until all items are fully resolved.
B.Force the team to stay late until the Retrospective is finished.
C.Terminate the event, and discuss the remaining topics in a separate session.
D.Ask the team to vote on whether they want to extend the meeting.
AnswerC

Terminating the event ensures the timebox is respected, which is a core Scrum principle. By moving unfinished topics to a separate, optional session, the Scrum Master maintains the integrity of the Retrospective event while still providing the space to address the remaining issues without disrupting the team's flow.

Why this answer

Scrum events are timeboxed to ensure they remain productive and focused. When a timebox is exceeded, the event must conclude. The Scrum Master must ensure the team understands the value of timeboxing, and if the discussion is unfinished, it can be scheduled for a separate, dedicated session.

This maintains the discipline and respect for the team's time that is essential for sustainable development.

Exam trap

Candidates often assume Scrum events can run over time if discussions are productive, violating the strict adherence to timeboxes mandated by the Scrum framework.

Practice this question →
39
MCQmedium

During a Sprint, a developer realizes that a Sprint Backlog item requires significantly more work than originally estimated, threatening the Sprint Goal. What is the most appropriate action?

A.The developer continues working and reports the delay at the Daily Scrum.
B.The developer unilaterally removes the item from the Sprint Backlog.
C.The developer collaborates with the Product Owner to refine the scope or plan.
D.The Scrum Master cancels the Sprint to redefine the team's objectives.
AnswerC

Collaboration with the Product Owner is vital when the Sprint Goal is at risk. The team must inspect the remaining work and adapt their plan, potentially negotiating scope while keeping the Sprint Goal intact. This maintains transparency and ensures the team remains focused on delivering the most valuable outcomes possible.

Why this answer

The Scrum Team must collaborate to assess the impact on the Sprint Goal and adjust the plan. Transparency regarding progress is essential in Scrum. By involving the Product Owner, the team ensures that trade-offs regarding scope are aligned with value delivery, preventing hidden delays.

This event-based inspection allows the team to adapt the Sprint Backlog immediately rather than waiting for the Sprint Review, maintaining the integrity of the commitment.

Exam trap

Candidates often think the developer should unilaterally decide to drop work or work overtime to fix the issue, ignoring the necessity of involving the Product Owner in scope trade-offs.

Practice this question →
40
MCQmedium

Which action is required by the Scrum Master during Sprint Planning?

A.Assign tasks to individual developers based on their technical skills.
B.Select the highest-priority items from the Product Backlog for the team.
C.Ensure the event occurs and that participants understand its purpose.
D.Estimate the effort required for all Product Backlog items in the Sprint.
AnswerC

The Scrum Master is accountable for the effectiveness of the Scrum events. By ensuring Sprint Planning happens and that the Scrum Team understands its purpose and constraints, they enable the team to produce a viable Sprint Goal and plan, which is essential for the success of the upcoming Sprint.

Why this answer

The Scrum Master is responsible for ensuring that the Sprint Planning event takes place and that the participants understand its purpose. They act as a facilitator, ensuring the team stays within the timebox and understands the goal. Their role is to coach the team on how to conduct the event effectively, ensuring the collaborative creation of the Sprint Backlog and clear definition of the Sprint Goal.

Exam trap

Candidates often think the Scrum Master must dictate the technical approach or create the Sprint Backlog during planning, ignoring that their actual duty is purely facilitation and ensuring the event occurs with proper understanding.

Practice this question →
41
MCQmedium

A Scrum Team is preparing for the Sprint Review. The Product Owner wants to know who is required to attend and what the event's primary output should be. Which statement correctly describes the Sprint Review?

A.It is a formal sign-off meeting where stakeholders approve or reject the Increment before it can be released.
B.It is a presentation by the Developers to stakeholders, ending with a report of completed Story Points and velocity.
C.It is a working session where the Scrum Team and stakeholders inspect the Increment and collaborate on what to do next, resulting in an adapted Product Backlog.
D.It is an internal meeting for the Scrum Team only, where the Developers decide which items to carry into the next Sprint.
AnswerC

The Sprint Review is an informal working session, not a formal presentation. The Scrum Team and stakeholders inspect the Increment and discuss progress toward the Product Goal, and the outcome is an adapted Product Backlog that informs the next Sprint. This collaborative inspection is exactly what makes the event valuable and distinguishes it from a status report or demo.

Why this answer

The Sprint Review is a collaborative working session in which the Scrum Team and stakeholders inspect the Increment and progress toward the Product Goal, then adapt the Product Backlog. It is not a formal approval gate, not a status presentation, and not an internal-only meeting. Its output is an updated Product Backlog that shapes what comes next.

Exam trap

The trap here is treating the Sprint Review as a formal sign-off or demo rather than a collaborative working session that adapts the Product Backlog.

Practice this question →
42
MCQeasy

A Scrum Team has just completed the Sprint Review and is about to begin the Sprint Retrospective. The Scrum Master wants to confirm the purpose of the upcoming event. What is the primary purpose of the Sprint Retrospective?

A.To plan the Sprint Goal and select Product Backlog items for the next Sprint.
B.To inspect the Increment and adapt the Product Backlog based on stakeholder feedback.
C.To demonstrate the completed Increment to stakeholders and collect their feedback for the next Sprint.
D.To inspect how the last Sprint went regarding individuals, interactions, processes, tools, and their Definition of Done, and to identify improvements.
AnswerD

The Sprint Retrospective is the event where the Scrum Team inspects how the last Sprint went with respect to individuals, interactions, processes, tools, and the Definition of Done. Its purpose is to identify the most helpful changes to improve effectiveness and to agree on adaptations, which are often added to the next Sprint Backlog.

Why this answer

The Sprint Retrospective is the final event of the Sprint and exists to inspect how the team worked across individuals, interactions, processes, tools, and the Definition of Done. The team identifies the most impactful improvements and may add them to the next Sprint Backlog. Product inspection and backlog adaptation belong to the Sprint Review, while goal setting and item selection belong to Sprint Planning.

Exam trap

The trap here is confusing the Retrospective with the Sprint Review, since both events inspect and adapt but focus on different subjects: one on the product, the other on the team's way of working.

Practice this question →
43
MCQmedium

During the middle of a Sprint, the Development Team realizes they will not be able to complete all the items selected during Sprint Planning. What is the most appropriate course of action according to Scrum?

A.Cancel the Sprint immediately and schedule a new Sprint Planning meeting to reset the team capacity.
B.Work mandatory overtime to ensure all selected Product Backlog items are completed by the end of the Sprint.
C.Collaborate with the Product Owner to renegotiate the scope of the Sprint Backlog based on revised capacity.
D.Independently drop the lowest priority items from the Sprint Backlog without consulting the Product Owner.
AnswerC

Collaborating with the Product Owner ensures transparency and shared understanding of what can realistically be delivered. The Product Owner adjusts expectations and re-prioritizes remaining work, preserving the Sprint Goal while respecting the team actual delivery capacity.

Why this answer

The Product Owner and Development Team collaborate to renegotiate the scope of the Sprint Backlog. Scrum relies on transparency and inspection, allowing adjustments when new constraints emerge. The Product Owner must understand what can be delivered to maximize value while maintaining a sustainable pace.

Canceling the entire Sprint is too extreme for a partial miss, and unilaterally dropping items violates collaborative commitment.

Exam trap

Candidates frequently suggest canceling the Sprint or working overtime, both of which are common anti-patterns that ignore the collaborative, empirical nature of Sprint scope adjustments.

Practice this question →
44
MCQmedium

A Product Owner decides that the market has shifted so dramatically that the current Sprint Goal no longer provides value, and cancels the Sprint midway. What should happen to the completed and incomplete Sprint Backlog items?

A.Completed items are released to production immediately, and the team moves directly into a new Sprint without Sprint Planning.
B.All Sprint Backlog items are discarded, and the team starts fresh in the next Sprint with a new Product Backlog.
C.The entire Sprint Backlog is carried over unchanged into the next Sprint to maintain continuity of work.
D.Completed items that meet the Definition of Done are reviewed and potentially accepted, while incomplete items are returned to the Product Backlog.
AnswerD

When a Sprint is canceled, any completed Product Backlog items are reviewed; if they are potentially releasable, the Product Owner typically accepts them. All incomplete Product Backlog items are returned to the Product Backlog, re-estimated if needed, and reconsidered for future Sprints. This preserves value and keeps the Product Backlog the single source of work.

Why this answer

Canceling a Sprint does not discard work. Completed Product Backlog items that satisfy the Definition of Done are reviewed and may be accepted by the Product Owner if potentially releasable, while incomplete items return to the Product Backlog for future consideration. The next Sprint still begins with Sprint Planning to establish a new Sprint Goal and Sprint Backlog.

Exam trap

The trap here is assuming a canceled Sprint wipes out all work, when in fact completed items can be accepted and incomplete items simply return to the Product Backlog.

Practice this question →
45
MCQeasy

A Scrum Team is preparing for its first Sprint and the Scrum Master is explaining the timebox for Sprint Planning. The upcoming Sprint will last one month. According to the Scrum Guide, what is the maximum timebox for Sprint Planning in this situation?

A.Two hours
B.Four hours
C.One day
D.Eight hours
AnswerD

For a one-month Sprint, the Scrum Guide sets the maximum timebox for Sprint Planning at eight hours. This is the longest event in Scrum and reflects the importance of aligning on the Sprint Goal and the work needed to achieve it. The timebox is a maximum, not a target, so the team may finish sooner if the plan is ready.

Why this answer

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The timebox ensures the team focuses on creating a usable plan without over-investing in planning, while still allowing enough time to define the Sprint Goal and select the necessary Product Backlog items.

Exam trap

The trap here is assuming the timebox is a fixed duration that must be used in full rather than a maximum that scales with Sprint length.

Practice this question →
46
Multi-Selecthard

Which THREE actions are appropriate for the Scrum Master to take during the Sprint Retrospective to ensure it is effective?

Select 3 answers
A.Insist that the team focuses only on negative feedback to drive change.
B.Ensure the event is timeboxed and that the team identifies actionable improvements.
C.Facilitate the event to ensure a safe, collaborative environment for all members.
D.Document the team's performance data to present at the next management review.
E.Encourage the team to inspect their process, tools, and relationships.
AnswersB, C, E

Timeboxing the Retrospective ensures the team stays focused and respects the schedule. Identifying actionable improvements is the ultimate goal of the event; without this, the meeting is just a venting session. Converting insights into concrete steps for the next Sprint is what actually moves the team forward.

Why this answer

A successful Retrospective requires a safe, objective environment where the team can reflect on their process without fear. By facilitating the session, ensuring it is timeboxed, and focusing on actionable improvements, the Scrum Master enables the team to grow. These three actions protect the integrity of the event and ensure that the team actually evolves its practices rather than just complaining about the past.

Exam trap

Examinees frequently select management-heavy options, such as dictating solutions or evaluating individual staff performance, forgetting that the Scrum Master must foster a safe environment for self-managed team reflection.

Practice this question →
47
MCQmedium

Which event is considered the primary planning session for the upcoming Sprint?

A.The Sprint Retrospective.
B.The Daily Scrum.
C.The Sprint Planning.
D.The Sprint Review.
AnswerC

Sprint Planning is explicitly designed to define the work for the Sprint. It brings the whole team together to collaborate on the Sprint Goal and the plan, which is essential for success. It ensures everyone is aligned before the development work begins, making it the cornerstone of Sprint execution.

Why this answer

Sprint Planning is the event that initiates the Sprint. It is here that the Scrum Team defines the Sprint Goal, selects the most valuable items from the Product Backlog, and creates a plan for the Developers to deliver those items. This event sets the entire cadence and commitment for the Sprint, making it the most critical planning point in the Scrum framework.

Exam trap

Candidates sometimes confuse Sprint Planning with Backlog Refinement or the Daily Scrum, misidentifying the event where the actual Sprint commitment and planning occur.

Practice this question →
48
Multi-Selecthard

Which TWO conditions must be met for a Sprint to be officially canceled before its time-box expires? (Choose TWO)

Select 2 answers
A.The Development Team realizes they will finish all backlog items two days ahead of schedule.
B.The Sprint Goal becomes obsolete due to significant shifts in company strategy or market conditions.
C.The Product Owner determines that the business need driving the Sprint Goal no longer exists.
D.Key developers fall ill, causing a temporary reduction in team velocity for the current iteration.
E.The Scrum Master and senior executives mutually agree that the team is moving too slowly.
AnswersB, C

An obsolete Sprint Goal renders the entire iteration pointless, making cancellation the correct economic choice. It prevents wasted effort and allows the team to refocus immediately on newly aligned business priorities.

Why this answer

A Sprint can be canceled only by the Product Owner, and only when the Sprint Goal becomes obsolete due to drastic changes in business conditions, market forces, or technology. This extreme mechanism protects the organization from investing effort in work that no longer holds value. The decision must be based on a clear strategic pivot rather than minor delivery delays or internal team disagreements.

Exam trap

Candidates often mistakenly believe the Scrum Master or the entire team can vote to cancel a Sprint. They fail to realize that only the Product Owner possesses the authority to make this decision.

Practice this question →
49
MCQeasy

What is the maximum timebox for a one-month Sprint's Sprint Planning event?

A.Four hours.
B.Eight hours.
C.Sixteen hours.
D.Two days.
AnswerB

The Scrum Guide prescribes an eight-hour maximum timebox for Sprint Planning for a one-month Sprint. This provides ample time for collaboration and goal setting without allowing the process to become bloated. It sets a clear limit that encourages teams to be efficient and prepared before the planning meeting begins.

Why this answer

The Scrum Guide defines timeboxes as maximum durations. For a one-month Sprint, Sprint Planning is capped at eight hours. This ensures that planning is concise and focused, forcing the team to prioritize effectively.

If a team feels they need more time, it is usually a sign that they need to improve their backlog refinement process rather than simply extending the meeting time.

Exam trap

Candidates often confuse sprint lengths or guess incorrect durations like 4 hours or 16 hours, failing to recall the exact Scrum Guide rule linking a one-month Sprint to an eight-hour maximum planning timebox.

Practice this question →

Ready to test yourself?

Try a timed practice session using only Scrum Events questions.

Start 20-question session