Intermediate everything in Agile & Scrum, page 13
Your Contribution in Backlog Refinement
Tests your proactivity in shaping work, not just executing it. A good answer covers adding technical detail, estimating effort, and splitting stories. From the PO, you need the business goal and clear acceptance criteria.
What is the 'Definition of Ready' for a backlog item?
This tests your understanding of Agile team contracts and preventing sprint waste. A great answer defines 'Definition of Ready' as a team checklist for actionable work, explains how it enables predictable sprints, and gives examples like clear acceptance…
How do you handle an urgent mid-sprint feature request?
This tests your understanding of Scrum roles and protecting the Sprint Goal. Acknowledge the request, redirect the stakeholder to the Product Owner who manages the backlog, and explain the trade-offs.
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.
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.
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 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).
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 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."
Agile Center of Excellence: Internal Consultants, Not Process Police
Think of an Agile CoE as internal consultants, not process police. They enable teams by providing coaching, tools, and shared standards. They're useful for scaling Agile consistently, but fail when they become a bureaucratic bottleneck instead of an…
Communities of Practice: Scaling Knowledge Across Teams
A Community of Practice is a cross-team guild for a specific skill, like 'frontend' or 'testing'. It's how large orgs prevent knowledge silos, standardize tooling, and mentor juniors. The footgun: they fail without dedicated time and a clear charter.
Nexus Integration Team: Air Traffic Control for Scrum
The Nexus Integration Team is like air traffic control for multiple Scrum teams, guiding them to a single, integrated product. It's used in the Nexus framework to coordinate 3-9 teams on one product, resolving cross-team dependencies and integration failures.
Nexus Framework: Scaling Scrum Without Breaking It
Nexus is a lightweight wrapper for 3-9 Scrum teams working on one product. It adds a coordinating Nexus Integration Team and shared events to manage dependencies and deliver a single, integrated increment each sprint.
Right-Shifting Forecasts: Why Your Deadlines Keep Moving
A forecast is like a GPS ETA in traffic; new tasks are like accidents ahead, pushing your arrival time further out. This happens when initial estimates are treated as fixed deadlines, ignoring new scope. The footgun is anchoring on the first date given.
Flow Efficiency: Are You Working or Waiting?
Flow efficiency measures the ratio of active work time to total lead time, revealing how much time tasks spend just waiting. Use it to diagnose why features take so long to ship. The biggest footgun is optimizing work speed when most delays hide in queues.
Classes of Service: Prioritize Work Beyond 'First In, First Out'
Classes of Service are policies that prioritize work by its business impact, not just arrival time. When a bug, a deadline, and normal work compete, CoS tells you which to pull first.
Throughput: Measuring What Gets Done
Throughput measures how many work items a team *finishes* in a time period, not how busy they are. It's used for forecasting future work and spotting bottlenecks. The footgun: never compare throughput between different teams, as item sizes and context vary.
Hypothesis-Driven Development: Stop Guessing, Start Learning
Hypothesis-Driven Development treats new features as experiments, not foregone conclusions. It's used to de-risk major changes by first testing the core assumption with a minimal product. The biggest footgun is writing vague, untestable hypotheses.
Five Whys: From Symptom to Root Cause
The Five Whys is a root cause analysis technique that traces a problem to its origin by asking 'Why?' repeatedly. It's used in post-mortems to find the underlying process failure, not just the surface-level symptom. The footgun is stopping at human error.
Agile Facilitation: Guiding Teams to Outcomes
An Agile Facilitator is a neutral guide, designing the *process* for a team to reach its own conclusions, not just running the meeting. They are crucial for sprint planning, retrospectives, and conflict resolution.
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