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 209
Stakeholder rejects a completed feature in Sprint Review. Process and Backlog impact?
Tests whether you see Sprint Review as inspection or sign-off. Strong answers: welcome feedback as new data, keep the Increment Done, and have the Product Owner order new work into the Backlog. Red flag: extending the current Sprint to rework the feature.
What is the Sprint Retrospective output and what happens next?
Output is a concrete improvement plan enacted in the next Sprint, not parked.
How would you handle a mandated Definition of Done with legacy debt?
Tests whether you treat the Definition of Done as a negotiable standard or a rigid rule, and if you know how to close the gap via transparency, incremental remediation, and organizational negotiation without shipping unfinished work.
How would you address a teammate working on misaligned low-priority tasks?
Tests whether you use the Daily Scrum to inspect progress toward agreed goals. Strong answers raise the misalignment at that event, adapt the plan as peers, and involve the Scrum Master only for environmental impediments.
How do you help establish a Sprint Goal when the PO hasn't?
Ask why the items matter, find a unifying outcome, and draft a goal the selected work supports.
Explain the difference between code complete and Done. What artifact defines this?
Tests whether you know Done means a usable Increment, not just written code. Strong answer: code complete is a dev milestone; Done means the Increment meets quality standards. Red flag: saying testing happens after Done or that Done is optional.
Daily Scrum ticket updates: what primary purpose is missing?
This tests whether you know the Daily Scrum inspects Sprint Goal progress and adapts the plan rather than reporting status. A strong answer identifies the missing purpose as team inspection and adaptation against the Sprint Goal.
What is the Sprint Goal and how does it guide planning?
Goal-driven Sprints vs ticket batches. The Sprint Goal is the agreed objective guiding selection of ordered backlog items to build a valuable Increment and enable inspection. Red flag: calling it optional or pulling the top N items without negotiation.
What root causes and retrospective fixes address chronic sprint overcommitment?
Tests systemic diagnosis over blaming the team. Check capacity math, refinement quality, psychological safety, and stakeholder pressure; propose velocity-guided planning, capacity recalculation, and better refinement.
How would you break a large epic into sprint-ready user stories?
This tests decomposing scope into vertical, shippable slices. A strong answer maps user journeys, slices end-to-end functionality, applies INVEST, and sequences by risk and value. Red flag: horizontal layers like database, API, then UI.
What are the key components of a well-written user story?
Tests your ability to turn vague needs into actionable, testable work. A strong answer covers who, what, and why; defines acceptance criteria as specific, testable scenarios; and references INVEST.
How should the team handle a PO adding urgent work mid-sprint?
This tests your grasp of agreed goals and the Scrum Master role. A strong answer covers: inspecting the current work selection, negotiating swaps, and having the Scrum Master foster conversation.
What is your responsibility when frontend developers are overloaded?
Tests cross-functional accountability and shared Sprint Goal ownership. Strong answer: own the goal collectively; pair, test, or learn simpler frontend tasks; raise the blocker at the Daily Scrum.
Outline your strategy for influencing organizational change to remove stage-gated releases.
Tests reframing governance around people readiness versus bureaucratic gates. Answer: map the change landscape; pilot Release on Demand with governance cadences for operational readiness; measure via Release, Stabilise, Measure, Adjust.
How should a Scrum Master resolve local optimizations hurting cross-team integration?
Tests if you see cross-team friction as a Scrum Master impediment needing global optimization. Answer: map the bottleneck, convene leaders to align on company goals, and broker a sustainable workflow. Red flag: blaming other teams or escalating without data.
How would you coach a developer skipping backlog refinement?
Coach one-on-one to find blockers; tie skipped refinement to planning delays; adapt format with the team.
Daily Scrum runs over 15 minutes; what facilitation techniques realign it?
This tests if you view the Daily Scrum as an inspection and adaptation event. A strong answer proposes a parking lot, coaches self-management of the timebox, and keeps talk focused on adapting the plan. A red flag is asking the Scrum Master to extend the.
Where does accountability lie when acceptance criteria miss the user problem?
Tests your grasp of Scrum's empirical accountability and value inspection. A strong answer cites shared Scrum Team ownership, uses the Sprint Review as the adaptation trigger, and proposes outcome-based refinement with stakeholders.
Product Owner wants to change Sprint Backlog scope mid-sprint
This tests empirical adaptation and Sprint plan ownership. A strong answer says scope changes risk the Increment and agreed goals, so the team must inspect and adapt together. A red flag is treating the Sprint Backlog as a fixed contract immune to adjustment.
Describe your engineering contribution in backlog refinement and needed PO info
This tests if you treat refinement as collaborative planning. A strong answer covers feasibility feedback, sizing, dependency flags, and the business value or priority you need from the PO. Red flag: claiming engineers only receive requirements.