More in Agile & Scrum — page 7
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?
WHAT IT TESTS: Can you separate busy work from value and cut scope before coding. ANSWER OUTLINE: Validate the smallest user-problem slice; defer gold-plating and custom abstractions; prefer existing tools. RED FLAG: Calling simplicity lazy engineering.
Primary goal of a retrospective and its tie to continuous improvement
WHAT IT TESTS: If you see the retrospective as inspect-and-adapt for processes. ANSWER OUTLINE: State the goal is improving quality, tie it to Scrum's empirical pillars, and demand adaptations. RED FLAG: Treating it as blame session lacking process changes.
How does 'Individuals and interactions' shape team structure and communication?
WHAT IT TESTS: If you know Agile values human collaboration above rigid systems. ANSWER OUTLINE: Say teams should be cross-functional and favor direct communication like pairing and standups over mandated tool workflows.
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.
How do you handle a story that's too large for a sprint?
Tests your ability to apply agile principles pragmatically. A great answer prioritizes the Sprint Goal, collaborates with the PO to vertically slice the story into smaller valuable pieces, and then re-plans the sprint backlog.
What systemic impediments cause 'Zombie Scrum' in an organization?
This tests your ability to diagnose organizational dysfunction beyond team-level issues. A great answer identifies systemic impediments like a lack of stakeholder involvement, low team autonomy, and a focus on output over value.
Design an Architecture for Rapid Product Iteration
This tests your grasp of evolutionary architecture for uncertain markets. Outline how to support guided, incremental change across multiple dimensions (tech, data, security) using fitness functions to protect key characteristics.
How do you quantify the cost of technical debt?
This tests translating engineering problems into business impact. Calculate the ongoing time cost per sprint, estimate the fix cost, and present a breakeven point to frame the refactor as an investment.
How do you handle non-functional requirements in a product backlog?
This tests if you can make abstract quality goals concrete. A good answer covers making NFRs explicit backlog items, adding them to the Definition of Done, and creating technical stories. A red flag is treating NFRs as assumed work that doesn't need tracking.
Blocker vs. Impediment: How do you escalate an impediment?
This tests your proactivity in removing systemic friction. Define a blocker (full stop) vs. an impediment (drag). Explain how you surface impediments in retros, track them in a backlog, and escalate systemic issues to leadership.
Which Scrum event fixes consistently failed Sprints?
Tests your grasp of Scrum's empirical process control. A great answer identifies the Sprint Retrospective as the event for inspecting the *process*, not just the product. It contrasts this with the Sprint Review.