All bites
The whole library, newest first. Filter by what you are here for, or pick a topic if you already know.
8668 bites
Page 241
How to Handle Poor Quality with Happy Stakeholders?
This tests your commitment to Scrum's Transparency pillar. A great answer involves being honest about unsustainable quality in the Sprint Review, proposing a plan (e.g., 20% capacity for tech debt), then using the Retrospective to fix the root cause.
Shift a Sprint Review from a Demo to a Working Session
Tests your understanding of Sprint Review's purpose: inspection and adaptation. A great answer shows how an engineer can partner with the PO to frame the session around goals, solicit feedback on the Increment, and collaboratively update the Product Backlog.
How do you ensure retro ideas become action?
This tests your ability to drive change by treating process improvements as formal work. A great answer suggests adding the top retro item to the next Sprint Backlog, making it visible, accountable, and part of the team's commitment.
Handling Negative Feedback in a Sprint Review
This tests your grasp of the Sprint Review's purpose (inspection, not acceptance). A strong answer has the Product Owner lead a discussion on the feedback, which then informs new, prioritized Product Backlog Items, rather than blaming or committing to…
What is the output of a Sprint Retrospective, and what happens next?
This tests if you create actionable outcomes, not just vent. The output is a plan to improve quality and effectiveness, with the most impactful items added to the next Sprint Backlog. A red flag is calling the output just 'notes' with no plan for integration.
Team delivers features, but stakeholders are unhappy. Why?
This tests your focus on outcomes over outputs. A strong answer diagnoses weak feedback loops, citing ineffective Sprint Reviews, a vague Product Goal, and a disconnected Product Owner.
Your team can't meet the mandated Definition of Done. What's your plan?
This tests your pragmatism and ability to manage risk. A strong answer makes the gap transparent, proposes a temporary aspirational DoD, and creates a concrete plan to close the gap. A red flag is ignoring the DoD or asking for a permanent exemption without a.
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.