📊 Product Management

How do you handle a teammate working on low-priority tasks?

This tests your accountability and interpersonal skills within a Scrum team. A great answer starts with a private, curious conversation, then uses the Daily Scrum to refocus the team on the Sprint Goal, and only then involves the Scrum Master as a coach.

How do you establish a Sprint Goal in planning?

This tests your ability to shift from a task-taker to a value-driver. A great answer involves asking 'why' to find a theme, proposing a goal based on that theme, and then negotiating scope against it. A red flag is passively waiting or confronting the PO.

What do you do when a Sprint Goal is in jeopardy?

Tests your grasp of adaptation over rigid plans. A great answer involves immediate transparency, team problem-solving on how to still meet the Sprint Goal, and negotiating scope with the Product Owner.

Difference Between 'Code Complete' and 'Done'?

Tests if you grasp value delivery vs. task completion. A great answer defines 'code complete' as a dev step and 'Done' as a team-agreed state of shippable value, governed by the Definition of Done. A red flag is equating 'Done' with just 'QA passed'.

What's missing from a ticket-focused Daily Scrum?

This tests if you know the Daily Scrum is for Developers to inspect progress toward the Sprint Goal, not a status report. A great answer states this purpose, explains how it enables adapting the next day's plan, and focuses on the team.

Sprint Goal: Purpose and Influence on Sprint Planning

Tests if you understand a Sprint is about a single objective, not just a list of tasks. Define the Sprint Goal as the 'why'—a commitment providing focus and flexibility that guides PBI selection. A red flag is defining the goal as a summary of tickets.

How do you fix a 200-item unmanageable product backlog?

Tests strategic thinking and Agile leadership. A strong answer proposes a collaborative workshop, re-anchors on the Product Goal, ruthlessly triages items, and establishes a new refinement process.

How do you fix a team that consistently overcommits?

This tests diagnosing systemic process failures. A great answer investigates root causes like stakeholder pressure, then proposes using historical velocity, tracking actual capacity, and improving backlog refinement.

How do you break down an epic into user stories?

Tests translating business needs into incremental work. A great answer uses story mapping to define a vertical slice MVP, then creates sprint-ready stories with acceptance criteria. A red flag is just listing features without prioritizing user value.

What are the components of a well-written user story?

Tests your ability to translate business needs into actionable engineering work. A great answer covers the '3 Cs' (Card, Conversation, Confirmation), the INVEST criteria, and specific, testable Acceptance Criteria. A red flag is just reciting the 'As a...'

How does a team handle strong technical disagreements?

This tests your ability to facilitate productive conflict. A great answer frames disagreement as healthy, then outlines structured techniques like timeboxing dialogue or multi-voting with reasoning.

How do you handle a PO adding work mid-sprint?

This tests your ability to protect the Sprint Goal collaboratively. A good answer acknowledges the PO's intent, proposes a scope swap to make trade-offs visible, and uses the Retrospective for long-term fixes.

What do you do when only frontend work remains in a sprint?

This tests your commitment to team ownership over role specialization. A great answer prioritizes the Sprint Goal, offers to help the frontend devs directly (pairing, testing), and finds other ways to unblock them.

What is the Definition of Done and its impact?

Tests your grasp of Scrum's core quality mechanism and its link to predictability. Define DoD as the formal quality standard for a releasable Increment, creating transparency and ensuring all work is truly complete.

Strategy for Changing a Stage-Gated Release Process

This tests your ability to influence organizational change. A great answer diagnoses the problem with data, understands stakeholder concerns, proposes a small pilot, and scales success. A red flag is complaining or proposing a purely technical fix.

How do you resolve team optimizations causing org-level friction?

Tests your ability to see beyond your team and facilitate org-level change. Gather data on the friction, facilitate cross-team discussions to align on shared goals, and propose structural solutions. A red flag is blaming others or only protecting your team.

How to coach a developer who skips backlog refinement?

This tests your coaching skills and ability to influence peers. First, understand their 'why' in a 1-on-1. Then, frame refinement as an investment to reduce future rework. A red flag is immediately escalating to a manager or being overly dogmatic.

How to fix a Daily Scrum that runs over its timebox?

Tests your understanding of the Daily Scrum's purpose: inspection and adaptation, not problem-solving. A good answer re-centers the team on the Sprint Goal, uses a 'parking lot' for deep dives, and addresses the root cause offline.

Accountability When an Increment Fails the User Problem

This tests your understanding of shared accountability versus blame culture. A great answer frames this as a whole-team process failure and proposes specific improvements to backlog refinement and in-sprint feedback loops, rather than blaming the Product…