Intermediate interview questions in Agile & Scrum, page 3
How do you handle a PO adding work mid-sprint?
Tests your ability to protect the Sprint Goal via collaboration, not conflict. A good answer uses the Retrospective to discuss impact, proposes a 'one-in, one-out' policy for the Sprint Backlog, and involves the Scrum Master.
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.
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.
How would you break down an epic into user stories?
Tests your ability to turn business goals into independent engineering tasks. A great answer maps user journeys, breaks work into vertical slices, defines acceptance criteria, and prioritizes by value.
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.
A task takes longer than estimated, jeopardizing the Sprint Goal. Next steps?
This tests empirical adaptation when forecasts fail. Strong answer: inspect in the Daily Scrum, adapt scope with the Product Owner, and protect the Sprint Goal via self-management.
A mid-sprint task jeopardizes the Sprint Goal. What now?
This tests your grasp of Scrum's core principles: adaptation and prioritizing the Sprint Goal. A great answer involves immediate transparency, collaborating with the Product Owner to renegotiate scope, and adapting the plan. A red flag is suggesting overtime.
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.
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.
How do you help establish a Sprint Goal?
This tests your agency beyond coding and your ability to facilitate collaboration. A good answer involves asking probing questions to find a theme, suggesting a value-oriented goal, and getting team buy-in. A red flag is passively accepting the task list.
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.
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 to address a teammate working on low-priority tasks?
This tests your understanding of peer accountability and Scrum roles. A good answer starts with a private conversation, focuses on the Sprint Goal, and uses Scrum events for transparency before escalating.
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.
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.
How do you handle negative stakeholder feedback in a Sprint Review?
This tests if you see feedback as successful adaptation, not failure. A good answer has the PO capture feedback as new backlog items for prioritization, without immediate commitment, and the team discusses process improvements in the retro.
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 action ensures a retrospective improvement is implemented?
Tests whether you treat adaptation as a deliverable. Propose making the top improvement a Sprint Backlog item with an owner and definition of done, then inspect it in the next retrospective. Vague agreements or more meetings without ownership are red flags.
How do you ensure retro action items are implemented?
Tests your ability to make process improvements concrete within Scrum. A great answer suggests adding the top improvement item from the retro directly into the next Sprint 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.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles