Agile
535 bites tagged Agile — interview questions with model answers, and 60-second explainers.
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. If you shield the Sprint and defer to the Product Owner.
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. Empirical process control via inspection and adaptation. Treating it as a status report for managers or Scrum Master.
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.
Describe the relationship between Jidoka and TDD/CI
Jidoka is stop-the-line; map TDD to unit detection and CI to build verification; show shift-left. Linking Lean quality control to software feedback loops. Treating them as separate or equating Jidoka with manual QA.
Explain Lean Muda and give three software lifecycle waste examples with mitigations
Tests mapping Lean waste to software with concrete countermeasures. A strong answer defines Muda as non-value-add work, cites three distinct types like waiting, defects, or overproduction, and pairs each with a specific practice.
How do you decide appropriate documentation levels without creating unnecessary overhead?
This tests balancing Manifesto values with operational reality. Strong answers define audience first, favor living docs over static artifacts, and calibrate depth to team topology and lifecycle stage. Red flag: using the Manifesto to justify no documentation.
How would you apply Agile simplicity when implementing a new feature?
Validate the smallest user-problem slice; defer gold-plating and custom abstractions; prefer existing tools. Can you separate busy work from value and cut scope before coding. Calling simplicity lazy engineering.
Primary goal of a retrospective and its tie to continuous improvement
State the goal is improving quality, tie it to Scrum's empirical pillars, and demand adaptations. If you see the retrospective as inspect-and-adapt for processes. Treating it as blame session lacking process changes.
How does 'Individuals and interactions' shape team structure and communication?
Say teams should be cross-functional and favor direct communication like pairing and standups over mandated tool workflows. If you know Agile values human collaboration above rigid systems.
AI Use Creates 'Cognitive Debt' in Scrum Teams
Over-relying on AI for sprint planning and backlog refinement creates "Cognitive Debt," eroding a team's problem-solving skills. While AI boosts productivity, it can eliminate the collaborative friction that builds shared understanding and critical reasoning.
How do you build a business case for technical debt?
This tests your ability to translate engineering problems into business impact. A strong answer quantifies the debt's cost (e.g., slower velocity), frames it as risk, and proposes a concrete payback plan like allocating 20% capacity.
Throughput vs. Velocity in Agile Planning
This tests your grasp of flow vs. estimation metrics. Define throughput as a count of delivered items and velocity as a sum of estimated points. Throughput measures actual output, making it better for forecasting. Red flag: claiming velocity is more accurate.
How do you coach a team to self-management?
Tests your grasp of situational leadership. A great answer uses a maturity model like Tuckman's stages to show how your coaching evolves from directive teaching (Forming) to strategic advising (Performing), and explains which techniques you retire.
How do you handle wildly fluctuating team velocity?
Tests if you know velocity is for team planning, not a manager's KPI. A good answer reframes the goal to predictability, investigates root causes with the team (e.g., story sizing, unplanned work), and proposes experiments.
Advocating to decentralize a deployment approval board
Tests your ability to influence change with data. A good answer frames deployments as frequent, time-critical decisions ideal for decentralization, proposes a phased rollout with metrics like cycle time, and defines new guardrails.
Manager Wants to Attend Your Sprint Retrospective. How Do You Respond?
Tests your grasp of psychological safety and stakeholder management. A good answer identifies the risk to open feedback, proposes other ways to inform the manager, and suggests a structured, one-time experiment if they must attend.
A story is too large for one sprint. What are your options?
Tests your grasp of incremental value delivery over just task completion. A great answer first re-validates priority with the PO, then discusses vertical splitting strategies and their trade-offs.
Get Agile bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.