Top 30 Easy Product Management Interview Questions and Answers for Freshers

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

   What should a well-structured metric hierarchy include when tracking engagement for a new feature?

   • aOne north star metric, two to three supporting KPIs, and at least one guardrail metric
   • bA comprehensive list of every possible user action to ensure complete data coverage
   • cVanity metrics such as total page views and total clicks to show overall activity
   • dOnly a north star metric to keep the plan simple and avoid metric overload
   Show the answer

   Answer: a · One north star metric, two to three supporting KPIs, and at least one guardrail metric

   A strong measurement plan uses a tight hierarchy with one north star, supporting KPIs, and guardrails to detect unintended harm. Option B is wrong because tracking every possible action creates instrumentation sprawl without prioritization, and Option C is wrong because vanity metrics do not tie directly to the feature's success.

   Read the full bite: How do you translate increase user engagement into a technical measurement plan?

3. Question 3 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

4. Question 4 of 30

   A product manager asks you to help "increase engagement" with a new feature. What is the most effective first step to take?

   • aSelect an analytics tool and draft a technical spec for instrumenting user interaction events.
   • bPropose A/B testing several different UI designs to see which one users prefer.
   • cAsk clarifying questions to define what specific user action constitutes 'engagement' for this feature.
   • dBegin tracking generic metrics like Daily Active Users (DAU) and session duration to establish a baseline.
   Show the answer

   Answer: c · Ask clarifying questions to define what specific user action constitutes 'engagement' for this feature.

   The first step is always to collaborate with the PM to clarify the vague business goal into a specific, measurable user action. Jumping to generic metrics like DAU is a common mistake as it doesn't provide specific insight into the new feature's performance.

   Read the full bite: Translate 'increase engagement' into a technical measurement plan

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

   What is the most crucial first step when translating a vague business goal like "increase engagement" into a technical measurement plan?

   • aIdentify a single, high-level metric, such as Daily Active Users (DAU), to track progress.
   • bDesign the database schema to capture all possible user interactions.
   • cDefine "engagement" with the Product Manager, specifying frequency, depth, or breadth.
   • dSelect an analytics platform and begin instrumenting basic click events.
   Show the answer

   Answer: c · Define "engagement" with the Product Manager, specifying frequency, depth, or breadth.

   The card emphasizes that the first and most crucial step is to collaborate with the Product Manager to define what 'engagement' specifically means for the feature. Without this clarification, any technical measurement plan would be based on assumptions and might not align with the actual business goal. Identifying a high-level metric (A) is part of the next step, but only after 'engagement' itself is clearly defined.

   Read the full bite: Translate 'increase engagement' into a technical measurement plan

7. Question 7 of 30

   How do vision, strategy, and roadmap most accurately relate to each other?

   • aThe roadmap defines the vision, which then defines the strategy
   • bVision sets the long-term aspiration, strategy chooses the path, and the roadmap executes it over time with feedback flowing back up
   • cThey are three names for the same artifact at different times
   • dStrategy is the fixed list of features and dates the team commits to
   Show the answer

   Answer: b · Vision sets the long-term aspiration, strategy chooses the path, and the roadmap executes it over time with feedback flowing back up

   Vision informs strategy, which prioritizes the roadmap, while execution learnings flow back upward. They are distinct layers, not synonyms; the roadmap does not define the vision, and a fixed feature-date list is not what strategy means.

   Read the full bite: How vision, strategy, and roadmap relate

8. Question 8 of 30

   A growth team boosts WAU with aggressive push notifications. Which counter metric most directly reveals shallow engagement caused by the campaign?

   • aSessions per user per week
   • b7-day retention rate
   • cLifetime value
   • dClient-side error rate
   Show the answer

   Answer: a · Sessions per user per week

   The card maps sessions per user to shallow engagement from notification spam, whereas 7-day retention tracks churn risk, making it the most tempting distractor because it is a valid counter metric but for a different problem. Lifetime value is explicitly called out as a lagging business outcome, not a real-time UX health signal.

   Read the full bite: What counter metrics track health of weekly active users?

9. Question 9 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

10. Question 10 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

11. Question 11 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?

12. Question 12 of 30

    What is the key data architecture difference when instrumenting a product-led growth loop versus a marketing funnel?

    • aLoops require persistent identity resolution and graph-style models to connect invitees to referrers across sessions and devices, while funnels use session-based attribution.
    • bLoops are monitored with historical drop-off dashboards, whereas funnels need near-real-time telemetry to detect compounding acceleration.
    • cLoops rely on session-based attribution and last-click tracking, while funnels require graph-style models to resolve user identities across devices.
    • dBoth systems can use the same event taxonomy and attribution model because they ultimately track user conversions.
    Show the answer

    Answer: a · Loops require persistent identity resolution and graph-style models to connect invitees to referrers across sessions and devices, while funnels use session-based attribution.

    Growth loops instrument cross-user viral events such as invites and referrals, so they require persistent identity resolution and graph-style models to link invitees to referrers across sessions and devices, while funnels rely on session-based attribution for linear stage tracking. Distractor A reverses these needs: session-based attribution is actually characteristic of funnels, and loops specifically cannot rely on single-session tracking because a referral may happen days later on a different device.

    Read the full bite: How do you instrument a marketing funnel versus a product-led growth loop?

13. Question 13 of 30

    What is a direct engineering risk when a team executes on a detailed roadmap without an underlying product strategy?

    • aTeams ship the wrong features efficiently because customer and market context are undefined
    • bProduct managers alone are blamed when features fail to meet market needs
    • cThe main impact is limited to business outcomes like revenue and marketing
    • dThe roadmap quickly becomes too vague to guide technical execution
    Show the answer

    Answer: a · Teams ship the wrong features efficiently because customer and market context are undefined

    Without strategy, teams risk building the wrong features efficiently because the ideal customer profile and market positioning are undefined. Distractor D is wrong because citing only business risks ignores the direct technical consequences, such as architectural drift and orphaned features, that the card emphasizes.

    Read the full bite: What are the risks of a roadmap without product strategy?

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 asked to build a complex new feature, which action best demonstrates Agile simplicity?

    • aSkip automated tests and documentation to ship the feature faster
    • bConsolidate all logic into a single file to reduce apparent complexity
    • cBuild custom infrastructure instead of using managed services to maintain full control
    • dShip the thinnest end-to-end slice that validates user value before adding edge cases
    Show the answer

    Answer: d · Ship the thinnest end-to-end slice that validates user value before adding edge cases

    Agile simplicity focuses on delivering the smallest end-to-end slice that proves user value while deferring unnecessary complexity. Skipping tests and documentation is a common misconception that mistakes simplicity for cutting corners, and collapsing logic into one file creates unmaintainable complexity rather than true simplicity.

    Read the full bite: How would you apply Agile simplicity when implementing a new feature?

16. Question 16 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.

17. Question 17 of 30

    Which approach to instrumenting an A/B test event best ensures trustworthy, maintainable experiment data?

    • aLog unstructured events and formalize the schema after the feature launches
    • bUse different field names in dev and production to keep environments separate
    • cDefine a tracking plan with minimal scoped properties, environment flags, and consistent naming conventions
    • dInclude every available user and device attribute so analysts can decide later what matters
    Show the answer

    Answer: c · Define a tracking plan with minimal scoped properties, environment flags, and consistent naming conventions

    A disciplined tracking plan with minimal, explicitly scoped properties and environment separation creates a trustworthy contract between engineering and analytics. Option D is tempting because flexibility sounds useful, but dumping every attribute creates a data swamp that breaks the single source of truth and makes schemas unmaintainable.

    Read the full bite: What fields belong in an experiment tracking event?

18. Question 18 of 30

    Which approach best demonstrates how to estimate user base for a new feature before coding begins?

    • aRun a broad user survey and use the raw number of interested respondents as the projected user base
    • bDefine the behavioral profile, triangulate internal and external proxy data, and synthesize a bounded range with stated assumptions
    • cRely primarily on executive opinion and industry benchmarks to set a single revenue target
    • dBuild a minimum viable product first, then extrapolate user base from early usage metrics
    Show the answer

    Answer: b · Define the behavioral profile, triangulate internal and external proxy data, and synthesize a bounded range with stated assumptions

    The card emphasizes de-risking bets by defining the job-to-be-done, layering multiple proxies, and bounding the estimate with explicit assumptions and ranges. Option D is a common red flag because insisting on an MVP first avoids pre-coding estimation entirely, while D relies on a single data source without triangulation.

    Read the full bite: How would you estimate user base for a new feature before coding?

19. Question 19 of 30

    Which method best persists marketing campaign attribution from a user's first visit through to their eventual signup?

    • aUse Facebook Pixel and Google Ads conversion tags as the sole record of which campaign drove the signup
    • bRely on the HTTP referer header when the user submits the signup form
    • cParse UTM parameters on arrival, store them in a first-party cookie, and read the cookie at signup
    • dAsk users to select how they heard about you during registration
    Show the answer

    Answer: c · Parse UTM parameters on arrival, store them in a first-party cookie, and read the cookie at signup

    Parsing UTM parameters into a first-party cookie preserves the original campaign source across browsing sessions until the user completes signup. Relying solely on ad platform conversion tags is insufficient because it prevents independent reconciliation and omits sources like organic blog traffic.

    Read the full bite: How do you attribute signups to Facebook, Google, and blog campaigns?

20. Question 20 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?

21. Question 21 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?

22. Question 22 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

23. Question 23 of 30

    Why validate song completion on the backend instead of trusting a client-side 'song finished' event alone for activation tracking?

    • aClient events can be lost, duplicated, or spoofed, inflating activation counts
    • bIt is impossible to measure playback position on the client
    • cBackend validation makes the event payload smaller
    • dBackend validation removes the need for an idempotency key
    Show the answer

    Answer: a · Client events can be lost, duplicated, or spoofed, inflating activation counts

    Client events are unreliable and forgeable, so server-side validation against actual streamed duration keeps activation counts trustworthy. It does not shrink payloads, replace idempotency keys, or imply the client cannot measure position.

    Read the full bite: Instrument a first-full-song activation event

24. Question 24 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.

25. Question 25 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

26. Question 26 of 30

    In a three-step funnel, how do you correctly calculate relative conversion between step two and step three?

    • aDivide unique users at step three by unique users at step one
    • bDerive the drop-off from the difference in pageviews between step two and step three
    • cDivide unique users at step three by unique users at step two
    • dDivide raw event counts at step three by raw event counts at step two
    Show the answer

    Answer: c · Divide unique users at step three by unique users at step two

    Relative conversion between adjacent steps requires dividing unique users at step N by unique users at the previous step. Option A measures overall conversion from the top, option D inflates numbers with refreshes, and option B relies on page differences that hide exactly where users quit.

    Read the full bite: How do you track events and calculate funnel drop-off?

27. Question 27 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?

28. Question 28 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?

29. Question 29 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

30. Question 30 of 30

    Which statement correctly distinguishes the Sprint Review from the Sprint Retrospective?

    • aThe Retrospective includes stakeholders to inspect the Increment; the Review is for the Scrum Team to plan the next Sprint
    • bBoth events are combined into a single lessons-learned meeting at the end of the Sprint
    • cThe Review inspects the Increment with stakeholders to adapt the Product Backlog; the Retrospective inspects the team's process to improve how they work
    • dThe Review is a demo for stakeholders to approve work; the Retrospective is for the team to show the Increment to each other
    Show the answer

    Answer: c · The Review inspects the Increment with stakeholders to adapt the Product Backlog; the Retrospective inspects the team's process to improve how they work

    The Sprint Review is a collaborative inspection of the Increment and Product Backlog with stakeholders, not a demo or approval gate, while the Retrospective is solely for the Scrum Team to inspect and adapt its own processes. Option D is tempting but wrong because it mischaracterizes the Review as a demo and the Retrospective as an internal show-and-tell.

    Read the full bite: Sprint Review vs Retrospective: purpose, focus, and audience