Intermediate interview questions in Agile & Scrum, page 10
How would you advocate for decentralizing a deployment approval dependency?
Propose a pilot with guardrails; track lead time, defect rate, rollbacks; define escalation paths.
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.
How would you advocate for decentralizing deployment approvals?
This tests your ability to drive organizational change with data. A great answer frames the problem using a decision framework (e.g., SAFe), proposes a phased pilot, and defines metrics like Cycle Time and Change Failure Rate to prove value.
Velocity is fluctuating wildly. How would you coach the team?
Tests whether you treat velocity as a diagnostic, not a target. A strong answer checks story sizing, unplanned work, definition of done, and team stability before changing process. Red flag: demanding higher estimates or comparing teams to normalize velocity.
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.
How would you coach a team with fluctuating velocity?
This tests your ability to use metrics for coaching, not just reporting. A good answer reframes the goal to predictability, investigates both qualitative and quantitative data, and proposes experiments. A red flag is treating velocity as a performance metric.
How do you evolve a team from dependent to self-managing?
Tests situational leadership across Tuckman's stages. Answer: direct in Forming, facilitate conflict in Storming, observe in Norming, system-coach in Performing, and retire each stance as trust grows.
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.
Coaching a team from dependency to self-management
This tests your ability to apply a maturity model (like Tuckman's) to Agile coaching. Outline your shift from directive teaching in Forming to challenging in Performing, retiring basic facilitation as the team matures. A red flag is a static coaching style.
What is throughput and how does it differ from velocity?
Tests whether you know throughput is count-based and velocity estimate-based. Define throughput as items finished per sprint regardless of size, contrast velocity's point sum, pick throughput for forecasting and keep velocity for calibration.
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.
Distinguish Throughput from Velocity in agile planning
This tests your grasp of outcome (Throughput) vs. effort (Velocity) metrics. Define both: Throughput is item count/time, Velocity is points/sprint. Contrast them by explaining Throughput measures actual delivery, not estimates.
How would you frame technical debt for your manager's business case?
This tests translating debt into business risk and cost of delay. A strong answer quantifies velocity drag, proposes phased remediation via WSJF or capacity allocation, and offers roadmap trade-offs.
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.
How do you build a business case for technical debt work?
Tests your ability to translate technical issues into business impact. Frame debt as business risk, quantify its impact on velocity and cost, and propose a clear, capacity-based plan.
Definition of Done vs. Acceptance Criteria: What's the difference?
Tests your grasp of Agile quality gates. Define both, then contrast scope (global DoD vs. local AC) and ownership (Team vs. PO). Connect them to creating a shippable, valuable Increment. A red flag is treating them as interchangeable.
A PBI is vague. How do you get clarity?
This tests ownership and proactive communication. A great answer involves documenting questions in the ticket, engaging the PM and tech lead for a discussion, and updating the ticket with clear acceptance criteria before starting any work.
How do you handle an unavailable Product Owner?
Tests your ability to solve process bottlenecks collaboratively. A great answer starts with data, then direct communication with the PO, proposes solutions like office hours, and escalates only as a last resort.
How do you explain tech debt's business impact to a Product Owner?
Tests your ability to translate technical issues into business value. A great answer quantifies the slowdown (e.g., cycle time), proposes an iterative plan (e.g., 20% capacity), and connects the work to future feature velocity.
How do you measure your effectiveness as a Scrum Master?
Tests your ability to link coaching to business outcomes, not just team output. A great answer quantifies impediment removal, team health improvements, and stakeholder satisfaction, avoiding vague claims or simply citing team velocity.
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