Agile &amp; Scrum

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.

What is Definition of Ready and why must the PO uphold it?

Tests grasp of backlog refinement as a team agreement. Strong answers define ready as value, scope, and acceptance criteria; explain it stops mid-sprint churn; and cite dependencies mapped and designs attached.

How do you handle a mid-Sprint urgent feature request?

Send the stakeholder to the Product Owner; do not add directly to the Sprint Backlog; protect the current plan.

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

Tests if you see the DoD as a transparency standard and the Retrospective as inspect-and-adapt. Explain that the DoD makes true progress visible, enabling honest inspection, while the Retrospective inspects process and adapts the DoD.

Stakeholder approaches mid-sprint with a feature request. What is the Scrum process?

Tests whether you know the Product Owner orders the backlog and the Sprint selection is fixed. Strong answer: send the stakeholder to the PO, who decides placement. Red flag: adding the work to the Sprint Backlog yourself.

How is work selected and forecasted for the Sprint Backlog?

Tests empirical forecasting. Outline: the team selects from the ordered Product Backlog using observed experience and expertise to create one valuable Increment. Red flag: treating the forecast as a hard commitment or citing velocity as a required input.

How do items flow between the Product Backlog, Sprint Backlog, and Increment?

Tests whether you understand Scrum's three artifacts as commitments to value, not just task lists. A strong answer describes ordering, selection, and the Definition of Done. Red flag: calling the Sprint Backlog a task list owned by the Product Owner.

Describe the Daily Scrum's purpose, audience, and intended outcome.

Say it's a Sprint event for Developers to inspect progress toward agreed goals and adapt their plan.

Three accountabilities in a Scrum Team and their primary focuses

Tests recall of the three Scrum accountabilities. Outline: Product Owner orders the backlog; Developers create an Increment each Sprint; Scrum Master fosters an environment for empiricism. Red flag: Using roles or treating the Scrum Master as a task master.

How would you implement a software Andon Cord equivalent?

This tests translating Lean stop-the-line into CI/CD culture. Trigger: compile, test, or integration failures. Impact: halt pipeline, block merges, and swarm to fix immediately with collective ownership. Red flag: blaming committers or deferring fixes.