Agile
535 bites tagged Agile — interview questions with model answers, and 60-second explainers.
A high-priority story is too large for one sprint. What are the options?
This tests your ability to deliver incremental value. A good answer prioritizes vertical slicing (end-to-end functionality) over horizontal (task-based) splits. Discuss trade-offs of different splitting patterns.
Handling a user story too large for a sprint
This tests your grasp of vertical slicing and incremental value. A good answer involves collaborating with the PO, splitting the story into smaller, value-delivering slices, and negotiating scope.
What systemic impediments cause 'Zombie Scrum'?
Tests your ability to diagnose systemic issues beyond team-level Scrum mechanics. A great answer identifies four root causes: misunderstood purpose, no stakeholder involvement, fake continuous improvement, and low team autonomy. A red flag is blaming the team.
How would you design an architecture for rapid product iteration?
Tests your grasp of evolutionary architecture for uncertain markets. A great answer outlines incremental change via modularity and CI/CD, fitness functions to guard qualities like security, and evolving across multiple dimensions (tech, data).
How do you quantify the cost of not addressing technical debt?
Tests your ability to translate technical issues into business impact. A good answer quantifies the slowdown, calculates the 'tax' on new features, and proposes a specific, time-boxed plan. A red flag is complaining about the PO without providing data.
How do you handle non-functional requirements in a product backlog?
This tests your ability to integrate quality attributes (NFRs) into the agile workflow. Make them visible in the backlog, add them to the Definition of Done, and break them into testable sprint tasks. Red flag: treating NFRs as separate, non-sprint work.
Blocker vs. Impediment: Definitions and Escalation
Tests your grasp of Scrum terms and escalation. A blocker stops work; an impediment slows it. A good answer defines both, then outlines an escalation path for impediments: visualize, quantify impact, and engage leadership.
Which Scrum event is most critical for a failing team?
This tests your grasp of Scrum's empirical process. A great answer champions the Sprint Retrospective for team self-inspection and process adaptation. A red flag is blaming a role or picking an event without justifying it based on Scrum principles.
How does an EM's role change in an agile model?
This tests your grasp of servant leadership. A great answer explains the shift from directing work to enabling teams by building capabilities, removing impediments, and managing boundaries.
Challenges of Transitioning to Cross-Functional Teams?
This tests your grasp of the friction in agile transitions. A good answer covers skill gaps requiring cross-training, new process demands like CI/CD ownership, and ambiguity over responsibilities like on-call.
How Management's Role Evolves When Scaling Agile
This tests your grasp of servant leadership vs. command-and-control. A good answer contrasts traditional managers (directing work) with enabling managers (removing impediments, teaching problem-solving) as seen in LeSS.
What is an Architectural Runway and how do you maintain it?
Tests balancing intentional architecture with emergent design in SAFe. Define it as the tech foundation for near-term features, built via Enabler stories. You contribute by identifying and implementing these enablers.
How would you create a probabilistic forecast for a backlog?
This tests your grasp of probabilistic forecasting over single-date estimates. A good answer explains using historical throughput to run a Monte Carlo simulation, then presenting a range of dates with confidence levels (e.g., 50%, 85%).
When does a task's Cycle Time begin and end?
This tests your practical grasp of process metrics. Define Cycle Time as starting when active work begins ('In Progress') and ending when 'Done' (shippable). Contrast it with Lead Time (request to delivery). A red flag is confusing the two or being too vague.
Explain Little's Law and its application in Kanban
Tests your grasp of flow metrics. A good answer defines the formula (Lead Time = WIP / Throughput), explains the trade-offs, and gives a practical example. A red flag is ignoring the prerequisite of a stable system, which makes the formula's output…
Purpose and Consequences of Kanban WIP Limits
Tests your grasp of flow efficiency. A good answer defines WIP limits as a tool to manage system flow, expose bottlenecks, and create a pull system, then links ignoring them to cascading delays. A red flag is seeing them as a tool to micromanage individuals.
How do you use a spike to de-risk a story?
This tests your ability to use agile spikes for targeted de-risking, not just vague research. A strong answer defines the specific question the spike will answer, proposes a strict time-box, and lists concrete deliverables like a decision or a better estimate.
Sprint Review vs. Sprint Retrospective: Purpose and Participants
Tests if you distinguish inspecting the product (Review) from the process (Retro). A good answer defines purpose (what vs. how), participants (stakeholders vs. team-only), and outcomes (backlog vs. process improvements).
Explain story points and why they're used over time-based estimates
Tests your grasp of relative vs. absolute estimation. Define story points as a relative measure of effort, complexity, and uncertainty. Explain they foster team consensus and provide a more stable velocity than time-based estimates.
Explain a backlog refinement meeting's purpose, participants, and outcomes
Tests understanding of a core Scrum ceremony. A good answer defines the goal (clarifying future work), names participants (Dev Team, PO), and lists outcomes (estimated stories).
How do you facilitate a heated technical disagreement between two seniors?
Tests your ability to de-escalate conflict and guide a team to a data-driven decision. Acknowledge the issue, separate the people from the problem, use a structured process, and focus on shared goals. A red flag is immediately picking a side or escalating.
Trade-offs: Product-Oriented vs. Project-Oriented Teams
This tests your understanding of how team structure and funding models impact long-term software quality. A great answer contrasts temporary, scope-funded project teams with durable, problem-funded product teams, highlighting the latter's benefits for…
How to apply Conway's Law to design team structures?
Tests if you can use Conway's Law proactively (the 'Inverse Conway Maneuver'). Outline: define the target architecture, then align small, autonomous teams to its components. A red flag is seeing the law only as a constraint, not a tool for intentional design.
Why is tracking team velocity as a KPI dysfunctional?
Tests if you know velocity is for planning, not performance. Explain it's easily gamed and measures output, not outcome. Propose metrics focused on value delivery and process improvement like cycle time.
Get Agile bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.