📊 Product Management

Changing Scope Mid-Sprint: Consequences and Conversations

This tests your grasp of the Sprint Goal's immutability vs. the Sprint Backlog's flexibility. A good answer assesses impact on the Sprint Goal, then negotiates trade-offs with the PO, like swapping an item of equal size. A red flag is a rigid 'no'.

Your Contribution in Backlog Refinement

Tests your proactivity in shaping work, not just executing it. A good answer covers adding technical detail, estimating effort, and splitting stories. From the PO, you need the business goal and clear acceptance criteria.

What is the 'Definition of Ready' for a backlog item?

This tests your understanding of Agile team contracts and preventing sprint waste. A great answer defines 'Definition of Ready' as a team checklist for actionable work, explains how it enables predictable sprints, and gives examples like clear acceptance…

How do you handle an urgent request during a Sprint?

This tests your ability to protect team focus while managing stakeholders. Acknowledge the request, explain its impact on the Sprint Goal, and redirect the stakeholder to the Product Owner, who owns the backlog. A red flag is saying 'yes' or 'no' directly.

How do the Sprint Retrospective and Definition of Done support empiricism?

This tests connecting Scrum theory to practice. Answer by linking the Definition of Done (Transparency) to the Retrospective, where the team Inspects process effectiveness and Adapts by improving the DoD itself. Red flag: defining terms in isolation.

How does the Sprint container enable empiricism and protect developers?

Tests if you see the Sprint as a time-box for empirical control. A good answer explains how the fixed duration and Sprint Goal create a cadence for inspection and protect developers from shifting priorities.

How do you handle an urgent mid-sprint feature request?

This tests your understanding of Scrum roles and protecting the Sprint Goal. Acknowledge the request, redirect the stakeholder to the Product Owner who manages the backlog, and explain the trade-offs.

How does a team forecast work for a Sprint?

Tests your grasp of Scrum's empirical forecasting. A great answer cites three inputs: the Product Backlog, past performance, and team capacity. The Developers pull the work; they don't have it pushed on them. A red flag is saying a manager dictates the scope.

Explain the Product Backlog, Sprint Backlog, and Increment

Tests your understanding of Scrum's three artifacts and their commitments (Product Goal, Sprint Goal, Definition of Done). Define each, explain the flow from Product to Sprint Backlog, and how completed items form a usable Increment.

Sprint Review vs. Sprint Retrospective: Purpose and Audience

This tests your grasp of Scrum's dual feedback loops. A great answer defines Review as inspecting the *product* with stakeholders to adapt the backlog, and Retrospective as inspecting the *process* with the team to improve the next Sprint.

What is the purpose of the Daily Scrum?

This tests if you know the Daily Scrum is a planning event for Developers, not a status report. A great answer states it's a 15-min meeting for Developers to inspect progress toward the Sprint Goal and adapt their plan.

What are the three accountabilities in a Scrum Team?

Tests recall of Scrum fundamentals and separation of concerns. Name the three accountabilities (Product Owner, Scrum Master, Developers) and define their focus: PO on value, Developers on delivery, and SM on process. A red flag is adding non-Scrum roles.

How would you implement an Andon Cord for a software team?

Tests your understanding of CI, team ownership, and balancing speed with quality. Define a trigger (broken main build), an action (halt merges/deploys), and a team response (swarming to fix). Red flag: scheduling the fix or blaming an individual.

How would you identify and elevate your team's primary constraint?

This tests systems thinking over local optimization. A great answer outlines the 5 steps: identify the constraint (e.g., long queues), exploit it, subordinate other processes, elevate it, and repeat. A red flag is jumping straight to hiring or buying tools.

Relate 'Build Quality In' (Jidoka) to TDD and CI

Tests your ability to connect abstract Lean principles to concrete practices. A great answer defines Jidoka (stop the line on defect), then links TDD as the micro-level check and CI as the macro-level automated line-stop. A red flag is just defining the terms.

How does Agile's 'welcoming change' differ from chaos?

Tests if you know Agile flexibility requires engineering discipline. Answer by defining the difference (discipline vs. chaos), listing technical practices (TDD, CI/CD), and naming architectural patterns (modular design).

Explain the Lean concept of 'Muda' (Waste)

Tests applying manufacturing principles to software. Define Muda as non-value-adding work. Cite 3 software wastes like partially done work, extra features, or defects, and offer specific mitigations like smaller batches, YAGNI, or TDD.

How do you apply 'working software over comprehensive documentation'?

This tests your ability to balance velocity with maintainability. A great answer defines docs by audience and purpose (onboarding, ops), prioritizes "living" docs like tests, and uses a just-in-time approach. A red flag is treating this as "no documentation."

Explain 'Simplicity' and how you apply it as an engineer

Tests if you see simplicity as maximizing value, not just minimizing code. A good answer defines it as avoiding unneeded work, then explains how you'd build an MVP, defer gold-plating, and validate scope with product.