Top 30 Scrum Interview Questions and Answers

30 questions. Pick an answer, or open “Show the answer” to read it.

Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.

1. Question 1 of 30

   A team's mandated project dashboard is replacing conversations about blockers. Which response best aligns with the Agile value of individuals and interactions?

   • aReduce mandatory fields, let the team own the board, and resolve blockers through direct conversation while keeping visibility.
   • bRemove the tool completely and rely solely on face-to-face communication for all project tracking.
   • cAssign a coordinator to handle dashboard updates so developers can focus on coding and direct collaboration.
   • dKeep the mandated workflow and add daily meetings so the team can interact while still complying with required updates.
   Show the answer

   Answer: a · Reduce mandatory fields, let the team own the board, and resolve blockers through direct conversation while keeping visibility.

   The correct answer treats the tool as a servant for visibility while prioritizing direct human interaction to resolve blockers, matching the manifesto's intent. B is a tempting distractor because it misreads the value as anti-tool, ignoring the manifesto's caveat that processes and tools still have value.

   Read the full bite: How does 'Individuals and interactions' shape team structure and communication?

2. Question 2 of 30

   According to the article, under what condition is a PBI count metric likely to be more stable for forecasting than story point velocity?

   • aWhen the product backlog items are already relatively uniform in size
   • bWhen story point inflation is corrected by recalibrating the baseline each sprint
   • cWhen the team runs both velocity and PBI count for several sprints before choosing one
   • dWhen senior engineers stop participating in story point estimation debates
   Show the answer

   Answer: a · When the product backlog items are already relatively uniform in size

   The article explicitly warns that if PBI sizes vary wildly, a straight count may mislead more than velocity, so relative uniformity is the key condition for reliable forecasts. Running both metrics in parallel is the recommended adoption strategy, not the condition that makes the count metric itself more stable.

   Read the full bite: Swap Velocity for PBI Count in Sprints

3. Question 3 of 30

   Which statement best describes the Agile Manifesto's core identity?

   • aIt is a prescriptive methodology with strict rules for project management.
   • bIt is a set of guiding values and principles for software development.
   • cIt is an instruction to completely abandon all project documentation.
   • dIt is a specific framework used for iterative software delivery.
   Show the answer

   Answer: b · It is a set of guiding values and principles for software development.

   The card clearly states the Agile Manifesto is "a value system" and "a declaration of four core values," making it a philosophical guide rather than a rigid methodology. It is not a specific framework, nor does it advocate for abandoning all documentation, but rather valuing working software more.

   Read the full bite: The Agile Manifesto: A Shift in Software Values

4. Question 4 of 30

   Which statement best reflects the Agile principle "Individuals and Interactions Over Processes and Tools"?

   • aTeams should avoid using any formal processes or tools to ensure maximum human interaction.
   • bThe primary focus should be on direct communication and collaboration, with processes and tools serving to enable these interactions.
   • cSuccessful Agile teams must always be co-located to facilitate face-to-face communication and minimize reliance on tools.
   • dInvesting in sophisticated project management tools and streamlined processes is key to fostering effective team interactions.
   Show the answer

   Answer: b · The primary focus should be on direct communication and collaboration, with processes and tools serving to enable these interactions.

   This principle highlights that direct human communication and collaboration are more valuable than rigid processes or tools. While processes and tools are necessary, they should facilitate, not replace, these interactions. Option A is incorrect because it misinterprets "over" as "instead of," advocating for the complete removal of processes and tools, which is a common misconception.

   Read the full bite: Individuals and Interactions Over Processes and Tools

5. Question 5 of 30

   An Agile developer finds a bug. According to the value "Individuals and interactions over processes and tools," what is the most effective first step?

   • aDocument the bug in detail within the team's tracking tool.
   • bWait for the next daily stand-up to announce the finding to the whole team.
   • cTalk directly with the relevant team member to quickly understand and verify the issue.
   • dFix the bug independently and submit the code for review.
   Show the answer

   Answer: c · Talk directly with the relevant team member to quickly understand and verify the issue.

   The principle prioritizes direct, high-bandwidth communication to solve problems efficiently. Talking directly is faster and more collaborative than creating a ticket (a process), which can introduce delays and misunderstandings.

   Read the full bite: Individuals & Interactions Over Processes & Tools: Explain This Value

6. Question 6 of 30

   A team runs perfect ceremonies, holds every certification, and maintains a green board, yet the product keeps failing. Which action would address the root cause according to the card?

   • aCreate structural support that makes bad news safe to send upward
   • bHold individual team members accountable for outcome ownership
   • cRewrite the roadmap to match current delivery capacity
   • dAdopt a more comprehensive agile framework with additional ceremonies
   Show the answer

   Answer: a · Create structural support that makes bad news safe to send upward

   The card argues that agile transformations fail when organizations hide hard truths in hallway conversations, so leadership must structurally make bad news safe to escalate. Distractor D misapplies the card's mention of Outcome Ownership by placing accountability on individuals rather than on leadership's responsibility to fix the culture of dishonesty.

   Read the full bite: Agile transformations die from dishonesty, not ceremonies

7. Question 7 of 30

   What is the most significant immediate impact of Mountain Goat Software's shift to exclusively private training for individual practitioners?

   • aMountain Goat Software will now offer its certifications at a reduced cost through new online platforms.
   • bIndividuals must now seek alternative public course providers or persuade their organizations to book private team sessions.
   • cMGS is expanding its public course schedule to accommodate a larger number of individual learners globally.
   • dThe overall quality of Agile and Scrum training provided by MGS is expected to decline due to this change.
   Show the answer

   Answer: b · Individuals must now seek alternative public course providers or persuade their organizations to book private team sessions.

   The card states that MGS is ceasing public courses, removing a key option for individual certification and forcing engineers to find alternatives or convince managers to book private sessions. The other options contradict the information provided or are not supported by the text.

   Read the full bite: Mountain Goat Software Ends Public Agile, Scrum Classes

8. Question 8 of 30

   According to Scrum.org's 8-step plan for AI-native teams, what fundamental shift in focus is emphasized?

   • aPrioritizing the development of new AI features over existing product maintenance.
   • bTransitioning from a 'Definition of Done' to a 'Definition of Value'.
   • cShifting from human-led decision-making to AI-driven strategic planning.
   • dMoving from individual productivity metrics to team-wide AI adoption rates.
   Show the answer

   Answer: b · Transitioning from a 'Definition of Done' to a 'Definition of Value'.

   The card explicitly states that the framework reframes AI adoption as a fundamental process shift, moving the team's focus from 'Definition of Done' to a 'Definition of Value'. This highlights a change in how success is measured and understood. Other options describe plausible aspects of AI integration but are not identified as the core fundamental shift in focus for the team's process.

   Read the full bite: Scrum.org's 8-Step Plan for AI-Native Teams

9. Question 9 of 30

   What is the primary benefit of making Agile planning a shared, collaborative problem for the entire team?

   • aIt allows for quicker decision-making by involving more perspectives upfront.
   • bIt reduces the workload for the Product Owner by delegating tasks.
   • cIt leads to more accurate forecasts and strengthens the team's collective responsibility for outcomes.
   • dIt ensures that all team members are equally accountable for any project failures.
   Show the answer

   Answer: c · It leads to more accurate forecasts and strengthens the team's collective responsibility for outcomes.

   The card states that shared planning results in 'realistic estimates and reliable forecasts' and 'fosters a sense of collective responsibility for the outcome.' While shared responsibility is important, option D focuses solely on accountability for failures, whereas the card emphasizes ownership and commitment to the overall outcome.

   Read the full bite: Make Agile Planning a Shared Problem

10. Question 10 of 30

    In Spec-Driven Development (SDD), how is the role of a specification fundamentally redefined?

    • aIt serves primarily as a detailed handoff document for developers to implement.
    • bIt acts as a static blueprint that must be finalized before any coding work can begin.
    • cIt becomes an optional administrative step, often automated by AI, to pre-populate tickets.
    • dIt functions as a higher-level programming language for AI agents to interpret and build upon.
    Show the answer

    Answer: d · It functions as a higher-level programming language for AI agents to interpret and build upon.

    The card explicitly states that SDD is about "treating the spec as a higher-level programming language" for AI agents, shifting the engineer's role to defining intent and constraints. This contrasts with the traditional view of specs as handoff documents or static blueprints, which the card refutes as a "wrong mental model."

    Read the full bite: AI Turns Specs Into a Programming Language

11. Question 11 of 30

    A Scrum team holds a Sprint Retrospective. Which outcome best demonstrates that the event achieved its primary purpose?

    • aThe team reviewed individual performance metrics and updated velocity forecasts for the upcoming Sprint.
    • bThe team openly discussed Sprint frustrations and left feeling heard without deciding on changes.
    • cThe team presented the working increment to stakeholders and collected product feedback.
    • dThe team inspected its processes and committed to at least one concrete adaptation for the next Sprint.
    Show the answer

    Answer: d · The team inspected its processes and committed to at least one concrete adaptation for the next Sprint.

    The retrospective's primary purpose is to inspect the team's process and adapt it through concrete improvements, not to review the product or vent. While discussing frustrations can be part of transparency, leaving without actionable adaptations misses the empirical pillar of adaptation that makes the event purposeful.

    Read the full bite: Primary goal of a retrospective and its tie to continuous improvement

12. Question 12 of 30

    What is the most crucial outcome of a successful Sprint Retrospective?

    • aAn updated project timeline and budget based on the team's recent performance.
    • bA detailed report for stakeholders on the progress made against the Sprint Goal.
    • cOne to three actionable improvement items that are added to the next Sprint Backlog.
    • dA list of all frustrations and interpersonal conflicts that occurred during the sprint.
    Show the answer

    Answer: c · One to three actionable improvement items that are added to the next Sprint Backlog.

    The primary purpose of a retrospective is to create a concrete plan for process improvement, making it a formal part of the team's work in the next sprint. Simply listing frustrations (Option D) without creating an actionable plan misses the core purpose of the event.

    Read the full bite: Goal of a Retrospective and Continuous Improvement

13. Question 13 of 30

    What is the primary goal of a Sprint Retrospective within the Scrum framework?

    • aTo identify what went wrong during the sprint and assign responsibility for those issues.
    • bTo ensure the Scrum Master has a clear understanding of team dynamics and individual performance.
    • cTo review the completed product increment with stakeholders and gather their feedback.
    • dTo inspect the team's process and create actionable plans for continuous improvement in the next sprint.
    Show the answer

    Answer: d · To inspect the team's process and create actionable plans for continuous improvement in the next sprint.

    The Sprint Retrospective's core purpose is for the Scrum Team to inspect its process (people, interactions, tools) and create concrete, actionable plans for improvement in the upcoming sprint, driving continuous improvement. Option A is a common misconception, as the retrospective is not a forum for assigning blame but for collective learning and adaptation.

    Read the full bite: What is the goal of a sprint retrospective?

14. Question 14 of 30

    When an engineer applies the Agile principle of 'simplicity,' their main objective is to...

    • aMaximize delivered customer value by identifying and focusing solely on essential features for the immediate need.
    • bDevelop highly generic and reusable architectural components to anticipate future feature needs.
    • cWrite the smallest possible amount of code to meet current requirements, even if it means refactoring later.
    • dStrictly adhere to the product manager's initial specifications to avoid scope creep.
    Show the answer

    Answer: a · Maximize delivered customer value by identifying and focusing solely on essential features for the immediate need.

    The principle of simplicity focuses on maximizing value by avoiding unnecessary work and delivering what is essential for the customer right now. Over-engineering for future needs (B) or passively accepting all requirements (D) goes against this principle, as does creating low-quality code (C).

    Read the full bite: Explain 'Simplicity' and how you apply it as an engineer

15. Question 15 of 30

    When applying the Agile principle of simplicity, what is the team's primary focus?

    • aChoosing the technical implementation that is easiest for new developers to understand.
    • bMaximizing the amount of work not done by delivering only what is essential to solve the immediate problem.
    • cBuilding a comprehensive, future-proof solution to prevent the need for rework later.
    • dWriting the simplest possible code, even if it means compromising on quality or testing.
    Show the answer

    Answer: b · Maximizing the amount of work not done by delivering only what is essential to solve the immediate problem.

    Simplicity is defined as 'the art of maximizing the amount of work not done,' focusing effort on immediate value. Building a complex 'future-proof' solution is a form of over-engineering that this principle aims to prevent.

    Read the full bite: Explain the Agile principle of Simplicity and how you apply it.

16. Question 16 of 30

    Which approach best reflects the principle "working software over comprehensive documentation"?

    • aCreate detailed documentation for every feature before coding begins.
    • bFocus solely on in-code comments, as external documents quickly become outdated.
    • cPrioritize documentation that directly supports the software's value, like tests or API specs.
    • dEliminate all documentation to maximize development speed.
    Show the answer

    Answer: c · Prioritize documentation that directly supports the software's value, like tests or API specs.

    The principle is about prioritizing working software, not eliminating documentation. A good approach prioritizes documentation that adds value and evolves with the software, such as living documentation like tests or auto-generated API specs. Option D is a common misinterpretation, as documentation can be a valuable tool when it supports the software's value.

    Read the full bite: How do you apply 'working software over comprehensive documentation'?

17. Question 17 of 30

    A team finds that many newly shipped features have very low user engagement. Which action best addresses this specific form of software development waste ('Muda')?

    • aIncrease the time spent on QA and automated testing for all new features.
    • bImplement strict Work-In-Progress (WIP) limits to accelerate feature delivery.
    • cBreak down features into smaller user stories to improve sprint planning.
    • dPrioritize the backlog based on direct user feedback and data.
    Show the answer

    Answer: d · Prioritize the backlog based on direct user feedback and data.

    This directly addresses the waste of 'Extra Features' by ensuring work is aligned with customer value, as per the YAGNI principle. Implementing WIP limits addresses bottlenecks and partially done work, not building unwanted features.

    Read the full bite: Explain Muda (Waste) with three software development examples

18. Question 18 of 30

    According to Lean principles, which activity is the clearest example of 'Muda' in software development?

    • aInvesting time in refactoring existing code to improve its internal structure and readability.
    • bConducting regular team meetings to ensure alignment and resolve blockers.
    • cEngaging in extensive architectural discussions for long-term system evolution.
    • dImplementing features based on speculative future needs that are ultimately unused.
    Show the answer

    Answer: d · Implementing features based on speculative future needs that are ultimately unused.

    The card defines Muda as any activity that consumes resources but creates no value for the end customer. Implementing unused features (Extra Features) is explicitly cited as a form of Muda. The other options, while potentially inefficient if poorly executed, are generally considered necessary overhead or value-adding activities for long-term system health and collaboration, not pure waste.

    Read the full bite: Explain the Lean concept of 'Muda' (Waste)

19. Question 19 of 30

    What key technical foundation allows a team to implement frequent changes in a disciplined, Agile manner, rather than descending into chaos?

    • aA well-groomed backlog and daily stand-up meetings to track progress.
    • bLoosely coupled architecture, high test coverage, and a mature CI/CD pipeline.
    • cA change control board that requires detailed upfront specifications for all modifications.
    • dA culture of working overtime to immediately implement any new stakeholder request.
    Show the answer

    Answer: b · Loosely coupled architecture, high test coverage, and a mature CI/CD pipeline.

    Disciplined agility relies on a technical foundation that makes change safe and cheap, such as loose coupling and CI/CD. A common misconception is that Agile is only about process; while backlog grooming is important, it doesn't technically enable safe, rapid change.

    Read the full bite: Agile Change vs. Chaos: Technical Enablers

20. Question 20 of 30

    Agile's principle of "welcoming change" is distinguished from chaotic development primarily by its reliance on what?

    • aEmpowering teams to make independent decisions without external oversight.
    • bFrequent stakeholder meetings and rapid iteration cycles.
    • cMinimizing detailed documentation and upfront design.
    • dA robust framework of engineering discipline, including automated testing and modular design.
    Show the answer

    Answer: d · A robust framework of engineering discipline, including automated testing and modular design.

    The card explicitly states that Agile's flexibility is a direct result of rigorous engineering discipline, highlighting practices like comprehensive automated testing, CI/CD, and modular architectural design. While frequent meetings and rapid iterations (Option B) are Agile practices, without this underlying technical discipline, they can lead to chaos rather than effective change management.

    Read the full bite: How does Agile's 'welcoming change' differ from chaos?

21. Question 21 of 30

    For what kind of problem domain is empirical process control primarily designed?

    • aComplex problems where requirements and technical challenges are unpredictable.
    • bSituations requiring minimal overhead and no need for frequent adjustments.
    • cSimple problems with well-understood, unchanging requirements.
    • dProjects where a detailed, upfront plan can guarantee success.
    Show the answer

    Answer: a · Complex problems where requirements and technical challenges are unpredictable.

    Empirical process control is explicitly designed for complex problem domains where more is unknown than known, and where requirements or technical challenges are likely to change. It is inefficient for simple, well-understood problems or situations where a detailed, predictive plan is sufficient.

    Read the full bite: Empirical Process Control: Steer by Observing, Not by Plan

22. Question 22 of 30

    In Scrum, who is ultimately accountable for deciding how much work from the Product Backlog can be included in a Sprint?

    • aThe entire Scrum Team, as they must collectively agree on the Sprint Goal.
    • bThe Scrum Master, as they are responsible for the team's effectiveness and process.
    • cThe Developers, as they are the ones responsible for creating the plan and doing the work.
    • dThe Product Owner, as they are responsible for maximizing the product's value.
    Show the answer

    Answer: c · The Developers, as they are the ones responsible for creating the plan and doing the work.

    The Developers are solely accountable for selecting the work for the Sprint Backlog, as they own the 'how'. While the Product Owner prioritizes the work, they do not dictate how much the Developers can forecast for a Sprint.

    Read the full bite: What are the three Scrum accountabilities and their focus?

23. Question 23 of 30

    Which statement accurately describes the distinct primary focus of the three accountabilities within a Scrum Team?

    • aThe Product Owner gathers user requirements, the Scrum Master acts as a team lead, and the Developers are responsible for quality assurance.
    • bThe Product Owner manages the project budget, the Scrum Master resolves team conflicts, and the Developers are solely responsible for testing.
    • cThe Product Owner is accountable for maximizing product value, the Scrum Master coaches the team on Scrum, and the Developers create usable Increments.
    • dThe Product Owner defines product features, the Scrum Master ensures team adherence to the process, and the Developers handle all technical implementation.
    Show the answer

    Answer: c · The Product Owner is accountable for maximizing product value, the Scrum Master coaches the team on Scrum, and the Developers create usable Increments.

    The Product Owner's primary accountability is maximizing product value, the Scrum Master's is establishing and coaching on Scrum, and the Developers' is creating usable Increments. Distractors often misrepresent the Scrum Master as a project manager or team lead, or narrow the Developers' role to just coding or testing.

    Read the full bite: What are the three accountabilities in a Scrum Team?

24. Question 24 of 30

    Which statement accurately describes the Scrum Master's accountability as defined in the 2020 Scrum Guide?

    • aFostering an environment where transparency, inspection, and adaptation can thrive
    • bPerforming the hands-on work required to turn backlog items into a releasable Increment
    • cManaging the Developers by assigning tasks and controlling Sprint deadlines
    • dOrdering the Product Backlog to maximize value and address the most important items first
    Show the answer

    Answer: a · Fostering an environment where transparency, inspection, and adaptation can thrive

    The Scrum Master fosters an environment for empiricism rather than assigning tasks or controlling deadlines, which is a common misconception that confuses the accountability with project management. Ordering the backlog belongs to the Product Owner, and producing the Increment is the accountability of the Developers.

    Read the full bite: Three accountabilities in a Scrum Team and their primary focuses

25. Question 25 of 30

    During an active Scrum Sprint, what is the general approach to the scope of work?

    • aIt is continuously refined and expanded as the team learns more about the product.
    • bIt is adjusted daily by the Development Team based on their progress and challenges.
    • cIt can be freely modified by the Product Owner to incorporate urgent new requirements.
    • dIt remains fixed to ensure the team can achieve the defined Sprint Goal.
    Show the answer

    Answer: d · It remains fixed to ensure the team can achieve the defined Sprint Goal.

    The card explicitly states, "The scope is fixed; no changes are made that would endanger the Sprint Goal." This ensures focus and predictability for the team. While the overall product backlog is flexible, the scope within an active sprint is protected.

    Read the full bite: The Sprint: A Timeboxed Rhythm for Work

26. Question 26 of 30

    When Developers detect an undesirable variance during a Daily Scrum, which response best aligns with the event's intended outcome?

    • aEscalate the issue to the Scrum Master and await direction on how to reassign work.
    • bAdjust their plan or approach to keep progress within acceptable limits before the Sprint ends.
    • cUpdate the task board for stakeholder visibility and continue executing the current plan unchanged.
    • dTreat the finding as a signal to replan the entire Sprint scope with the Product Owner immediately.
    Show the answer

    Answer: b · Adjust their plan or approach to keep progress within acceptable limits before the Sprint ends.

    The Daily Scrum is designed for Developers to inspect progress and adapt their own plan when variances appear so the Sprint stays within acceptable limits. Replanning the entire Sprint confuses this event with Sprint Planning, while escalating to the Scrum Master contradicts the rule that the Developers own and direct their plan.

    Read the full bite: Describe the Daily Scrum's purpose, audience, and intended outcome.

27. Question 27 of 30

    What is the primary purpose of the Daily Scrum?

    • aTo ensure every developer formally answers what they did yesterday, what they will do today, and their blockers.
    • bTo provide a detailed status update to the Product Owner and Scrum Master.
    • cTo solve complex technical problems and remove impediments as a group.
    • dTo inspect progress toward the Sprint Goal and create an actionable plan for the next 24 hours.
    Show the answer

    Answer: d · To inspect progress toward the Sprint Goal and create an actionable plan for the next 24 hours.

    The Daily Scrum is a planning event for the Developers to inspect progress and adapt their plan for the day. It is not a status report for others, which is a common misconception.

    Read the full bite: Describe the purpose of the Daily Scrum

28. Question 28 of 30

    What is the primary purpose of the Daily Scrum event?

    • aTo provide a detailed status report to the Product Owner and Scrum Master.
    • bTo ensure each team member answers the three prescribed questions about their individual work.
    • cTo allow Developers to inspect progress toward the Sprint Goal and adapt their plan.
    • dTo resolve technical impediments and discuss design challenges as a team.
    Show the answer

    Answer: c · To allow Developers to inspect progress toward the Sprint Goal and adapt their plan.

    The Daily Scrum is a planning event for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next 24 hours. It is not a status report for management (option A), nor is it for in-depth problem-solving (option D) or rigidly following a set of individual questions (option B).

    Read the full bite: What is the purpose of the Daily Scrum?

29. Question 29 of 30

    A Scrum Team has just finished a Sprint. What is the key difference between the Sprint Review and the Sprint Retrospective that follows?

    • aThe Review is a formal demonstration of the product, while the Retrospective is an informal session for the team to voice complaints.
    • bThe Review focuses on inspecting the product with stakeholders, while the Retrospective focuses on inspecting the team's process without them.
    • cThe Review's outcome is a shippable increment, while the Retrospective's outcome is a report on team velocity for management.
    • dThe Review is for stakeholders to approve the increment, while the Retrospective is for the team to plan the next Sprint's work.
    Show the answer

    Answer: b · The Review focuses on inspecting the product with stakeholders, while the Retrospective focuses on inspecting the team's process without them.

    The Sprint Review is an event to inspect the product increment with stakeholders to adapt the Product Backlog. In contrast, the Sprint Retrospective is for the Scrum Team only to inspect its own process and create a plan for improvement.

    Read the full bite: What is the purpose of Sprint Review vs. Sprint Retrospective?

30. Question 30 of 30

    What is the key distinction between a Sprint Review and a Sprint Retrospective?

    • aThe Sprint Review is led by the Product Owner to gather feedback on future features, and the Sprint Retrospective is led by the Scrum Master to resolve technical impediments.
    • bThe Sprint Review is a formal presentation of the Increment to management, while the Sprint Retrospective is a casual team discussion about individual performance.
    • cThe Sprint Review primarily focuses on updating the Definition of Done, while the Sprint Retrospective focuses on refining user stories for the next Sprint.
    • dThe Sprint Review involves the Scrum Team and stakeholders to inspect the product and adapt the Product Backlog, whereas the Sprint Retrospective involves only the Scrum Team to inspect the process and plan improvements.
    Show the answer

    Answer: d · The Sprint Review involves the Scrum Team and stakeholders to inspect the product and adapt the Product Backlog, whereas the Sprint Retrospective involves only the Scrum Team to inspect the process and plan improvements.

    The Sprint Review focuses on inspecting the product with stakeholders to adapt the Product Backlog, while the Sprint Retrospective focuses on inspecting the team's process with only the Scrum Team to identify improvements. Option B is incorrect because the Review is a collaborative working session, not just a formal presentation, and the Retrospective is about process, not individual performance.

    Read the full bite: Sprint Review vs. Sprint Retrospective: Purpose and Audience