Top 30 Agile Interview Questions and Answers
30 multiple-choice questions on Agile, drawn from 30 bites out of the 535 tagged Agile on Tezvyn. Answer them here or read straight down. Every question carries the correct option, why it is correct, and a link to the bite it came from.
30 questions. Pick an answer, or open “Show the answer” to read it.
Answers are graded in your browser. Nothing is saved, and no XP or streak is earned here. The app keeps score.
Question 1 of 30
A team's mandated project dashboard is replacing conversations about blockers. Which response best aligns with the Agile value of individuals and interactions?
Show the answer
Answer: a · Reduce mandatory fields, let the team own the board, and resolve blockers through direct conversation while keeping visibility.
The correct answer treats the tool as a servant for visibility while prioritizing direct human interaction to resolve blockers, matching the manifesto's intent. B is a tempting distractor because it misreads the value as anti-tool, ignoring the manifesto's caveat that processes and tools still have value.
Read the full bite: How does 'Individuals and interactions' shape team structure and communication?
Question 2 of 30
According to the article, under what condition is a PBI count metric likely to be more stable for forecasting than story point velocity?
Show the answer
Answer: a · When the product backlog items are already relatively uniform in size
The article explicitly warns that if PBI sizes vary wildly, a straight count may mislead more than velocity, so relative uniformity is the key condition for reliable forecasts. Running both metrics in parallel is the recommended adoption strategy, not the condition that makes the count metric itself more stable.
Question 3 of 30
Which statement best describes the Agile Manifesto's core identity?
Show the answer
Answer: b · It is a set of guiding values and principles for software development.
The card clearly states the Agile Manifesto is "a value system" and "a declaration of four core values," making it a philosophical guide rather than a rigid methodology. It is not a specific framework, nor does it advocate for abandoning all documentation, but rather valuing working software more.
Read the full bite: The Agile Manifesto: A Shift in Software Values
Question 4 of 30
Which statement best reflects the Agile principle "Individuals and Interactions Over Processes and Tools"?
Show the answer
Answer: b · The primary focus should be on direct communication and collaboration, with processes and tools serving to enable these interactions.
This principle highlights that direct human communication and collaboration are more valuable than rigid processes or tools. While processes and tools are necessary, they should facilitate, not replace, these interactions. Option A is incorrect because it misinterprets "over" as "instead of," advocating for the complete removal of processes and tools, which is a common misconception.
Read the full bite: Individuals and Interactions Over Processes and Tools
Question 5 of 30
An Agile developer finds a bug. According to the value "Individuals and interactions over processes and tools," what is the most effective first step?
Show the answer
Answer: c · Talk directly with the relevant team member to quickly understand and verify the issue.
The principle prioritizes direct, high-bandwidth communication to solve problems efficiently. Talking directly is faster and more collaborative than creating a ticket (a process), which can introduce delays and misunderstandings.
Read the full bite: Individuals & Interactions Over Processes & Tools: Explain This Value
Question 6 of 30
A team runs perfect ceremonies, holds every certification, and maintains a green board, yet the product keeps failing. Which action would address the root cause according to the card?
Show the answer
Answer: a · Create structural support that makes bad news safe to send upward
The card argues that agile transformations fail when organizations hide hard truths in hallway conversations, so leadership must structurally make bad news safe to escalate. Distractor D misapplies the card's mention of Outcome Ownership by placing accountability on individuals rather than on leadership's responsibility to fix the culture of dishonesty.
Read the full bite: Agile transformations die from dishonesty, not ceremonies
Question 7 of 30
What is the most significant immediate impact of Mountain Goat Software's shift to exclusively private training for individual practitioners?
Show the answer
Answer: b · Individuals must now seek alternative public course providers or persuade their organizations to book private team sessions.
The card states that MGS is ceasing public courses, removing a key option for individual certification and forcing engineers to find alternatives or convince managers to book private sessions. The other options contradict the information provided or are not supported by the text.
Read the full bite: Mountain Goat Software Ends Public Agile, Scrum Classes
Question 8 of 30
According to Scrum.org's 8-step plan for AI-native teams, what fundamental shift in focus is emphasized?
Show the answer
Answer: b · Transitioning from a 'Definition of Done' to a 'Definition of Value'.
The card explicitly states that the framework reframes AI adoption as a fundamental process shift, moving the team's focus from 'Definition of Done' to a 'Definition of Value'. This highlights a change in how success is measured and understood. Other options describe plausible aspects of AI integration but are not identified as the core fundamental shift in focus for the team's process.
Read the full bite: Scrum.org's 8-Step Plan for AI-Native Teams
Question 9 of 30
What is the primary benefit of making Agile planning a shared, collaborative problem for the entire team?
Show the answer
Answer: c · It leads to more accurate forecasts and strengthens the team's collective responsibility for outcomes.
The card states that shared planning results in 'realistic estimates and reliable forecasts' and 'fosters a sense of collective responsibility for the outcome.' While shared responsibility is important, option D focuses solely on accountability for failures, whereas the card emphasizes ownership and commitment to the overall outcome.
Question 10 of 30
A Scrum team uses AI to automate sprint planning and backlog refinement, resulting in faster cycles. What is the primary risk of this approach, described as 'Cognitive Debt'?
Show the answer
Answer: c · The team's shared understanding and critical thinking skills will erode over time.
Cognitive Debt is the erosion of a team's collective problem-solving and critical reasoning, not a failure of the AI tool itself. While inaccurate AI outputs are a risk, the core concept focuses on the decline in the team's shared understanding from offloading collaborative thinking.
Read the full bite: AI Use Creates 'Cognitive Debt' in Scrum Teams
Question 11 of 30
Which scenario best illustrates Cunningham's concept of legitimate technical debt?
Show the answer
Answer: a · Shipping early in a complex domain to gain insights, then immediately refactoring to align code with new understanding
Cunningham defines technical debt as a deliberate loan taken to gain learning time in complex domains, which is only valid if repaid immediately through refactoring. Skipping tests in a well-understood domain is simply cutting corners, not the exploratory debt he described.
Read the full bite: Ward Cunningham: Ship Early, But Repay Technical Debt
Question 12 of 30
What is the main benefit of assigning AI agents directly within Jira rather than using them in separate chat windows?
Show the answer
Answer: b · It removes orchestration friction and keeps automated work inside the existing audit trail.
The card argues that chat-based agents create orchestration friction and accountability blind spots, whereas native Jira assignment embeds automated work in the same traceable workflow used for humans. Option D misattributes the 10-15% productivity lift to integration speed rather than recovered friction, and B describes the problematic status quo that actually erodes those gains.
Read the full bite: Jira makes AI agents assignable teammates
Question 13 of 30
In Spec-Driven Development (SDD), how is the role of a specification fundamentally redefined?
Show the answer
Answer: d · It functions as a higher-level programming language for AI agents to interpret and build upon.
The card explicitly states that SDD is about "treating the spec as a higher-level programming language" for AI agents, shifting the engineer's role to defining intent and constraints. This contrasts with the traditional view of specs as handoff documents or static blueprints, which the card refutes as a "wrong mental model."
Read the full bite: AI Turns Specs Into a Programming Language
Question 14 of 30
A Scrum team holds a Sprint Retrospective. Which outcome best demonstrates that the event achieved its primary purpose?
Show the answer
Answer: d · The team inspected its processes and committed to at least one concrete adaptation for the next Sprint.
The retrospective's primary purpose is to inspect the team's process and adapt it through concrete improvements, not to review the product or vent. While discussing frustrations can be part of transparency, leaving without actionable adaptations misses the empirical pillar of adaptation that makes the event purposeful.
Read the full bite: Primary goal of a retrospective and its tie to continuous improvement
Question 15 of 30
Which scenario best describes a project where the Waterfall model would be an appropriate choice?
Show the answer
Answer: b · A project with a well-defined scope and stable requirements that are unlikely to change.
The Waterfall model is explicitly recommended for projects with stable, well-understood, and fixed requirements, as its sequential nature struggles with changes. Projects with evolving requirements (like option A) are a poor fit due to the high cost of late-stage modifications.
Read the full bite: Waterfall Model: Build Software Like a Building
Question 16 of 30
What is the most crucial outcome of a successful Sprint Retrospective?
Show the answer
Answer: c · One to three actionable improvement items that are added to the next Sprint Backlog.
The primary purpose of a retrospective is to create a concrete plan for process improvement, making it a formal part of the team's work in the next sprint. Simply listing frustrations (Option D) without creating an actionable plan misses the core purpose of the event.
Read the full bite: Goal of a Retrospective and Continuous Improvement
Question 17 of 30
What is the primary goal of a Sprint Retrospective within the Scrum framework?
Show the answer
Answer: d · To inspect the team's process and create actionable plans for continuous improvement in the next sprint.
The Sprint Retrospective's core purpose is for the Scrum Team to inspect its process (people, interactions, tools) and create concrete, actionable plans for improvement in the upcoming sprint, driving continuous improvement. Option A is a common misconception, as the retrospective is not a forum for assigning blame but for collective learning and adaptation.
Read the full bite: What is the goal of a sprint retrospective?
Question 18 of 30
When an engineer applies the Agile principle of 'simplicity,' their main objective is to...
Show the answer
Answer: a · Maximize delivered customer value by identifying and focusing solely on essential features for the immediate need.
The principle of simplicity focuses on maximizing value by avoiding unnecessary work and delivering what is essential for the customer right now. Over-engineering for future needs (B) or passively accepting all requirements (D) goes against this principle, as does creating low-quality code (C).
Read the full bite: Explain 'Simplicity' and how you apply it as an engineer
Question 19 of 30
When asked to build a complex new feature, which action best demonstrates Agile simplicity?
Show the answer
Answer: d · Ship the thinnest end-to-end slice that validates user value before adding edge cases
Agile simplicity focuses on delivering the smallest end-to-end slice that proves user value while deferring unnecessary complexity. Skipping tests and documentation is a common misconception that mistakes simplicity for cutting corners, and collapsing logic into one file creates unmaintainable complexity rather than true simplicity.
Read the full bite: How would you apply Agile simplicity when implementing a new feature?
Question 20 of 30
When applying the Agile principle of simplicity, what is the team's primary focus?
Show the answer
Answer: b · Maximizing the amount of work not done by delivering only what is essential to solve the immediate problem.
Simplicity is defined as 'the art of maximizing the amount of work not done,' focusing effort on immediate value. Building a complex 'future-proof' solution is a form of over-engineering that this principle aims to prevent.
Read the full bite: Explain the Agile principle of Simplicity and how you apply it.
Question 21 of 30
A team is running a usability study across three two-week sprints. How should this research work be managed in the product backlog?
Show the answer
Answer: a · Maintain one backlog item across all three sprints, marking individual tasks done as they are completed.
The card emphasizes that research should live as a single backlog item that stays open across sprints while bite-sized tasks are completed, making B correct. Option D is tempting because it follows strict sprint boundaries, but forcing a research story closed at sprint end regardless of study status is explicitly flagged as a common mistake.
Read the full bite: How does UX research integrate into a two-week agile sprint?
Question 22 of 30
Which of the following best explains the Lean Software Development principle of 'Decide as Late as Possible'?
Show the answer
Answer: c · It aims to preserve flexibility and keep options open until the last responsible moment, adapting to new information.
The card explicitly states that 'Decide as Late as Possible' is to 'preserve flexibility and keep options open until the last responsible moment.' This allows for adaptation to new information. Option B is incorrect because Lean emphasizes fast feedback and adaptation over extensive upfront analysis, which could be considered waste if it delays learning or delivery.
Read the full bite: Lean Software Development: Focus on Value, Not Waste
Question 23 of 30
What is the primary objective when an agile team applies the concept of Muda to its development process?
Show the answer
Answer: d · To identify and eliminate activities that consume resources without adding value for the customer.
The core purpose of Muda is to identify and remove activities that consume resources but create no customer value, thereby maximizing value-adding work. While delays and handoffs are wastes, the card explicitly warns against blindly eliminating all forms, as some might be necessary, making option A incorrect.
Read the full bite: The Seven Wastes of Software Development (Muda)
Question 24 of 30
Which approach best reflects the principle "working software over comprehensive documentation"?
Show the answer
Answer: c · Prioritize documentation that directly supports the software's value, like tests or API specs.
The principle is about prioritizing working software, not eliminating documentation. A good approach prioritizes documentation that adds value and evolves with the software, such as living documentation like tests or auto-generated API specs. Option D is a common misinterpretation, as documentation can be a valuable tool when it supports the software's value.
Read the full bite: How do you apply 'working software over comprehensive documentation'?
Question 25 of 30
A mature microservice platform with 15 dependent teams must reduce documentation maintenance overhead. Which strategy best applies the principle that documentation must earn its keep?
Show the answer
Answer: d · Archive low-traffic wikis, publish auto-generated API docs from code, and maintain curated human-written runbooks and onboarding guides
This approach calibrates documentation to audience size and lifecycle stage, favoring low-overhead generated specs while preserving human-written artifacts for high-value decisions like incident response. Option A is tempting because automation feels efficient, but generated specs alone cannot capture operational context such as runbooks and onboarding guidance.
Question 26 of 30
When determining the appropriate level of documentation for a new system, what is the most effective guiding principle?
Show the answer
Answer: a · Treat documentation as a product for a specific audience, weighing its creation cost against the future cost of its absence.
The correct approach is to treat documentation as a product with a specific audience and purpose, justifying its existence by ensuring its value outweighs its cost. While self-documenting code is valuable, it cannot capture architectural decisions or onboarding context, making that option incomplete.
Read the full bite: How do you decide the right level of project documentation?
Question 27 of 30
A team finds that many newly shipped features have very low user engagement. Which action best addresses this specific form of software development waste ('Muda')?
Show the answer
Answer: d · Prioritize the backlog based on direct user feedback and data.
This directly addresses the waste of 'Extra Features' by ensuring work is aligned with customer value, as per the YAGNI principle. Implementing WIP limits addresses bottlenecks and partially done work, not building unwanted features.
Read the full bite: Explain Muda (Waste) with three software development examples
Question 28 of 30
A team spends days merging branches, deploys frequent hotfixes, and maintains unused features. Which countermeasure set best targets the structural root causes of these three wastes?
Show the answer
Answer: b · Use trunk-based development with fast CI, test-driven development with automated regression, and hypothesis-driven MVPs with story slicing
The correct answer maps each waste to a structural Lean countermeasure: trunk-based development removes waiting caused by batching, TDD prevents defects before production, and MVPs stop overproduction by validating demand first. Option C is tempting because hiring staff and adding upfront documentation feel like responsible management, but they ignore Lean principles of flow and feedback loops and do not remove root causes.
Question 29 of 30
According to Lean principles, which activity is the clearest example of 'Muda' in software development?
Show the answer
Answer: d · Implementing features based on speculative future needs that are ultimately unused.
The card defines Muda as any activity that consumes resources but creates no value for the end customer. Implementing unused features (Extra Features) is explicitly cited as a form of Muda. The other options, while potentially inefficient if poorly executed, are generally considered necessary overhead or value-adding activities for long-term system health and collaboration, not pure waste.
Read the full bite: Explain the Lean concept of 'Muda' (Waste)
Question 30 of 30
A software development team consistently observes that their Lead Time is significantly longer than their Cycle Time. What does this disparity most likely suggest?
Show the answer
Answer: b · Significant bottlenecks exist in the workflow before or after the team's active development phase.
The card explicitly states that "A large difference between Lead Time and Cycle Time signals that the biggest delays are happening outside of active development, in your queues and handoffs." Option A represents a common mistake, as focusing only on Cycle Time optimization ignores these larger, customer-impacting delays.
Read the full bite: Cycle Time vs. Lead Time: Team Speed vs. Customer Wait
Could you explain these out loud?
That is what an interview actually tests. Tezvyn gives you questions like these with what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.