Intermediate interview questions in Agile & Scrum
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 do you decide the right level of project documentation?
This tests your pragmatism beyond literal Agile interpretation. A great answer defines docs as a product for a specific user, ties value to reducing future work, and proposes a tiered approach. A red flag is treating all documentation as pure overhead.
How do you apply 'working software over comprehensive documentation'?
This tests your ability to balance velocity with maintainability. A great answer defines docs by audience and purpose (onboarding, ops), prioritizes "living" docs like tests, and uses a just-in-time approach. A red flag is treating this as "no documentation."
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.
Explain Muda (Waste) with three software development examples
Tests your ability to apply Lean's 'Muda' (waste) concept to software. A good answer defines Muda, then gives 3 examples like partially done work or extra features, with specific mitigations like WIP limits or YAGNI. A red flag is giving generic examples.
Explain the Lean concept of 'Muda' (Waste)
Tests applying manufacturing principles to software. Define Muda as non-value-adding work. Cite 3 software wastes like partially done work, extra features, or defects, and offer specific mitigations like smaller batches, YAGNI, or TDD.
How does Agile welcome changing requirements without chaos?
Whether you know that Agile embraces change only when supported by engineering discipline. Distinguish planned adaptability from reactive chaos by citing short feedback loops, evolutionary architecture, and continuous integration.
Agile Change vs. Chaos: Technical Enablers
Tests if you know Agile is disciplined, not chaotic. A great answer contrasts structured, time-boxed change with reactive chaos, then details technical enablers like CI/CD and loose coupling. A red flag is equating Agile with no planning.
How does Agile's 'welcoming change' differ from chaos?
Tests if you know Agile flexibility requires engineering discipline. Answer by defining the difference (discipline vs. chaos), listing technical practices (TDD, CI/CD), and naming architectural patterns (modular design).
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.
Relate Lean's 'Build Quality In' to TDD and CI
This tests your ability to connect historical Lean principles to modern software development. Explain Jidoka as "stop the line," then frame TDD and CI as its software equivalents that prevent defects from propagating.
Relate 'Build Quality In' (Jidoka) to TDD and CI
Tests your ability to connect abstract Lean principles to concrete practices. A great answer defines Jidoka (stop the line on defect), then links TDD as the micro-level check and CI as the macro-level automated line-stop. A red flag is just defining the terms.
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.
Relationship Between Product Backlog, Sprint Backlog, and Increment
This tests your understanding of Scrum artifacts as commitments to goals, not just to-do lists. Define the Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), and Increment (Definition of Done), then trace an item's flow.
Explain the Product Backlog, Sprint Backlog, and Increment
Tests your understanding of Scrum's three artifacts and their commitments (Product Goal, Sprint Goal, Definition of Done). Define each, explain the flow from Product to Sprint Backlog, and how completed items form a usable Increment.
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 does a team forecast work for a Sprint?
This tests if you know the Developers own the forecast, not the PO or SM. A good answer cites past performance, current capacity, and the Product Backlog as inputs. A red flag is saying the Product Owner dictates the work.
How does a team forecast work for a Sprint?
Tests your grasp of Scrum's empirical forecasting. A great answer cites three inputs: the Product Backlog, past performance, and team capacity. The Developers pull the work; they don't have it pushed on them. A red flag is saying a manager dictates the scope.
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 do you handle an urgent mid-sprint feature request?
This tests your understanding of Scrum roles and protecting the Sprint Goal. A great answer redirects the stakeholder to the Product Owner, who then assesses the request's impact and negotiates with the team if it can be swapped in without harming the Sprint…
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