Agile
535 bites tagged Agile — interview questions with model answers, and 60-second explainers.
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.
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.
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.
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.
Explain the Agile principle of Simplicity and how you apply it.
This tests your ability to connect Agile theory to engineering practice. A good answer defines simplicity as maximizing work not done, applies YAGNI with a concrete example (e.g., phased feature rollout), and links it to business value.
Goal of a Retrospective and Continuous Improvement
Tests if you see process improvement as a core engineering duty. A great answer defines the retro's goal (inspect & adapt the process), its output (actionable items for the next Sprint), and its role as the engine of continuous improvement.
Individuals & Interactions Over Processes & Tools: Explain This Value
Tests your grasp of Agile's core philosophy: empowering people over rigid systems. A great answer defines the principle, links it to cross-functional team structures, and champions direct communication over ticket-passing.
Evidence-Based Management: Metrics Over Gut Feel
EBM replaces 'I think' with 'I know because the data shows...' It's about making decisions using evidence, not just intuition. Use it to prioritize features with user data or optimize processes by measuring cycle time. The footgun is metric fixation.
AI Turns Specs Into a Programming Language
Spec-Driven Development (SDD) reframes specs as a higher-level programming language for AI agents, not just pre-coding docs. This shifts engineering work from implementation details to defining intent and constraints.
Scrum.org's 8-Step Plan for AI-Native Teams
Scrum.org has outlined an 8-step framework to guide teams in becoming 'AI-native.' This structured approach aims to embed AI into all aspects of Scrum, shifting focus from production to evaluation and from 'Definition of Done' to 'Definition of Value'.
Make Agile Planning a Shared Problem
Chaotic sprints and messy backlogs often result from planning being treated as a solo task. This siloed approach leads to overcommitment and erodes stakeholder trust, making agile feel unreliable.
Mountain Goat Software Ends Public Agile, Scrum Classes
Mountain Goat Software is ending its public Agile/Scrum courses to focus on private team training. This removes a key option for individual certification, forcing engineers to find alternatives or convince managers to book a more costly private session for…
What is a Community of Practice or Guild?
Tests understanding of cross-team knowledge sharing. Define CoPs as voluntary groups for a shared craft, explain their purpose (sharing best practices, standardizing tools), and give an example like a 'Frontend Guild.'
What is a cross-functional team in Agile?
This tests your grasp of how team structure impacts velocity. A great answer defines it as a team with all skills to ship value, explains how it reduces handoffs and boosts ownership, and links it to faster cycle times.
How do you escalate a blocking external dependency?
Tests your ability to quantify impact, show ownership, and empower leaders. A great answer details the business cost, documents your due diligence, and defines a clear 'ask' for the leader.
Using Flow Metrics to Coach for Predictability
Tests if you use data for coaching, not coercion. Define Lead/Cycle Time, explain how stable times (p85) create predictability, and contrast this with Velocity's flaws. The red flag is treating any metric as a target instead of a diagnostic tool for the team.
Servant Leadership in Scrum: Meaning and Examples
Tests your ability to apply agile theory. Define servant leadership as enabling team success, not managing tasks. Give concrete examples like shielding the team from distractions or facilitating technical decisions.
Scrum Master vs. Project Manager: How do they direct teams?
This tests your understanding of servant-leadership vs. command-and-control. A good answer contrasts their core goals (process vs. project), team interaction (coaching vs. directing), and how they handle change. Red flag: saying an SM is just an 'agile PM.'
Nexus Integration Team vs. Traditional Integration Teams
Tests your grasp of scaled Agile's shift from phase-gate integration to shared ownership. Contrast the NIT as a coach for continuous integration with a traditional team's gatekeeper role.
How do you resolve a cross-team dependency in scaled agile?
This tests your ability to navigate organizational complexity and take ownership. First, validate the blocker and try direct peer contact. Then, escalate via Scrum of Scrums or PM syncs, proposing technical solutions like API contracts.
How do you build a Monte Carlo project forecast?
Tests your ability to model uncertainty and communicate probabilistic outcomes. A good answer covers gathering cycle time data, running thousands of simulations, and presenting results as a probability distribution (e.g., "85% confidence by X date"), not a…
How do you use a cycle time scatterplot to set an SLE?
This tests your ability to use data, not feelings, to manage stakeholder expectations. Explain the scatterplot, identify the outlier, calculate the 85th percentile, and propose a data-backed Service Level Expectation (SLE).
What's the relationship between Cycle Time, WIP, and Throughput?
This tests your grasp of Little's Law. A great answer defines Cycle Time, WIP, and Throughput, states the formula (Cycle Time = WIP / Throughput), and explains why lowering WIP reduces cycle time.
Burn-up vs. Burn-down Charts: What's the Difference?
Tests your understanding of project tracking metrics and their implications. A burn-down shows work remaining vs. time. A burn-up shows work completed vs. total scope, making it better for visualizing scope creep. A red flag is just describing the lines.
Get Agile bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.