Top 30 Easy Agile & Scrum Interview Questions and Answers for Freshers

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.

1. 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?

   • aReduce mandatory fields, let the team own the board, and resolve blockers through direct conversation while keeping visibility.
   • bRemove the tool completely and rely solely on face-to-face communication for all project tracking.
   • cAssign a coordinator to handle dashboard updates so developers can focus on coding and direct collaboration.
   • dKeep the mandated workflow and add daily meetings so the team can interact while still complying with required updates.
   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?

2. Question 2 of 30

   Which statement best reflects the Agile principle "Individuals and Interactions Over Processes and Tools"?

   • aTeams should avoid using any formal processes or tools to ensure maximum human interaction.
   • bThe primary focus should be on direct communication and collaboration, with processes and tools serving to enable these interactions.
   • cSuccessful Agile teams must always be co-located to facilitate face-to-face communication and minimize reliance on tools.
   • dInvesting in sophisticated project management tools and streamlined processes is key to fostering effective team interactions.
   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

3. Question 3 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?

   • aDocument the bug in detail within the team's tracking tool.
   • bWait for the next daily stand-up to announce the finding to the whole team.
   • cTalk directly with the relevant team member to quickly understand and verify the issue.
   • dFix the bug independently and submit the code for review.
   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

4. Question 4 of 30

   A Scrum team holds a Sprint Retrospective. Which outcome best demonstrates that the event achieved its primary purpose?

   • aThe team reviewed individual performance metrics and updated velocity forecasts for the upcoming Sprint.
   • bThe team openly discussed Sprint frustrations and left feeling heard without deciding on changes.
   • cThe team presented the working increment to stakeholders and collected product feedback.
   • dThe team inspected its processes and committed to at least one concrete adaptation for the next Sprint.
   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

5. Question 5 of 30

   What is the most crucial outcome of a successful Sprint Retrospective?

   • aAn updated project timeline and budget based on the team's recent performance.
   • bA detailed report for stakeholders on the progress made against the Sprint Goal.
   • cOne to three actionable improvement items that are added to the next Sprint Backlog.
   • dA list of all frustrations and interpersonal conflicts that occurred during the sprint.
   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

6. Question 6 of 30

   What is the primary goal of a Sprint Retrospective within the Scrum framework?

   • aTo identify what went wrong during the sprint and assign responsibility for those issues.
   • bTo ensure the Scrum Master has a clear understanding of team dynamics and individual performance.
   • cTo review the completed product increment with stakeholders and gather their feedback.
   • dTo inspect the team's process and create actionable plans for continuous improvement in the next sprint.
   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?

7. Question 7 of 30

   When an engineer applies the Agile principle of 'simplicity,' their main objective is to...

   • aMaximize delivered customer value by identifying and focusing solely on essential features for the immediate need.
   • bDevelop highly generic and reusable architectural components to anticipate future feature needs.
   • cWrite the smallest possible amount of code to meet current requirements, even if it means refactoring later.
   • dStrictly adhere to the product manager's initial specifications to avoid scope creep.
   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

8. Question 8 of 30

   When asked to build a complex new feature, which action best demonstrates Agile simplicity?

   • aSkip automated tests and documentation to ship the feature faster
   • bConsolidate all logic into a single file to reduce apparent complexity
   • cBuild custom infrastructure instead of using managed services to maintain full control
   • dShip the thinnest end-to-end slice that validates user value before adding edge cases
   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?

9. Question 9 of 30

   When applying the Agile principle of simplicity, what is the team's primary focus?

   • aChoosing the technical implementation that is easiest for new developers to understand.
   • bMaximizing the amount of work not done by delivering only what is essential to solve the immediate problem.
   • cBuilding a comprehensive, future-proof solution to prevent the need for rework later.
   • dWriting the simplest possible code, even if it means compromising on quality or testing.
   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.

10. Question 10 of 30

    In Scrum, who is ultimately accountable for deciding how much work from the Product Backlog can be included in a Sprint?

    • aThe entire Scrum Team, as they must collectively agree on the Sprint Goal.
    • bThe Scrum Master, as they are responsible for the team's effectiveness and process.
    • cThe Developers, as they are the ones responsible for creating the plan and doing the work.
    • dThe Product Owner, as they are responsible for maximizing the product's value.
    Show the answer

    Answer: c · The Developers, as they are the ones responsible for creating the plan and doing the work.

    The Developers are solely accountable for selecting the work for the Sprint Backlog, as they own the 'how'. While the Product Owner prioritizes the work, they do not dictate how much the Developers can forecast for a Sprint.

    Read the full bite: What are the three Scrum accountabilities and their focus?

11. Question 11 of 30

    Which statement accurately describes the distinct primary focus of the three accountabilities within a Scrum Team?

    • aThe Product Owner gathers user requirements, the Scrum Master acts as a team lead, and the Developers are responsible for quality assurance.
    • bThe Product Owner manages the project budget, the Scrum Master resolves team conflicts, and the Developers are solely responsible for testing.
    • cThe Product Owner is accountable for maximizing product value, the Scrum Master coaches the team on Scrum, and the Developers create usable Increments.
    • dThe Product Owner defines product features, the Scrum Master ensures team adherence to the process, and the Developers handle all technical implementation.
    Show the answer

    Answer: c · The Product Owner is accountable for maximizing product value, the Scrum Master coaches the team on Scrum, and the Developers create usable Increments.

    The Product Owner's primary accountability is maximizing product value, the Scrum Master's is establishing and coaching on Scrum, and the Developers' is creating usable Increments. Distractors often misrepresent the Scrum Master as a project manager or team lead, or narrow the Developers' role to just coding or testing.

    Read the full bite: What are the three accountabilities in a Scrum Team?

12. Question 12 of 30

    Which statement accurately describes the Scrum Master's accountability as defined in the 2020 Scrum Guide?

    • aFostering an environment where transparency, inspection, and adaptation can thrive
    • bPerforming the hands-on work required to turn backlog items into a releasable Increment
    • cManaging the Developers by assigning tasks and controlling Sprint deadlines
    • dOrdering the Product Backlog to maximize value and address the most important items first
    Show the answer

    Answer: a · Fostering an environment where transparency, inspection, and adaptation can thrive

    The Scrum Master fosters an environment for empiricism rather than assigning tasks or controlling deadlines, which is a common misconception that confuses the accountability with project management. Ordering the backlog belongs to the Product Owner, and producing the Increment is the accountability of the Developers.

    Read the full bite: Three accountabilities in a Scrum Team and their primary focuses

13. Question 13 of 30

    When Developers detect an undesirable variance during a Daily Scrum, which response best aligns with the event's intended outcome?

    • aEscalate the issue to the Scrum Master and await direction on how to reassign work.
    • bAdjust their plan or approach to keep progress within acceptable limits before the Sprint ends.
    • cUpdate the task board for stakeholder visibility and continue executing the current plan unchanged.
    • dTreat the finding as a signal to replan the entire Sprint scope with the Product Owner immediately.
    Show the answer

    Answer: b · Adjust their plan or approach to keep progress within acceptable limits before the Sprint ends.

    The Daily Scrum is designed for Developers to inspect progress and adapt their own plan when variances appear so the Sprint stays within acceptable limits. Replanning the entire Sprint confuses this event with Sprint Planning, while escalating to the Scrum Master contradicts the rule that the Developers own and direct their plan.

    Read the full bite: Describe the Daily Scrum's purpose, audience, and intended outcome.

14. Question 14 of 30

    What is the primary purpose of the Daily Scrum?

    • aTo ensure every developer formally answers what they did yesterday, what they will do today, and their blockers.
    • bTo provide a detailed status update to the Product Owner and Scrum Master.
    • cTo solve complex technical problems and remove impediments as a group.
    • dTo inspect progress toward the Sprint Goal and create an actionable plan for the next 24 hours.
    Show the answer

    Answer: d · To inspect progress toward the Sprint Goal and create an actionable plan for the next 24 hours.

    The Daily Scrum is a planning event for the Developers to inspect progress and adapt their plan for the day. It is not a status report for others, which is a common misconception.

    Read the full bite: Describe the purpose of the Daily Scrum

15. Question 15 of 30

    What is the primary purpose of the Daily Scrum event?

    • aTo provide a detailed status report to the Product Owner and Scrum Master.
    • bTo ensure each team member answers the three prescribed questions about their individual work.
    • cTo allow Developers to inspect progress toward the Sprint Goal and adapt their plan.
    • dTo resolve technical impediments and discuss design challenges as a team.
    Show the answer

    Answer: c · To allow Developers to inspect progress toward the Sprint Goal and adapt their plan.

    The Daily Scrum is a planning event for the Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next 24 hours. It is not a status report for management (option A), nor is it for in-depth problem-solving (option D) or rigidly following a set of individual questions (option B).

    Read the full bite: What is the purpose of the Daily Scrum?

16. Question 16 of 30

    A Scrum Team has just finished a Sprint. What is the key difference between the Sprint Review and the Sprint Retrospective that follows?

    • aThe Review is a formal demonstration of the product, while the Retrospective is an informal session for the team to voice complaints.
    • bThe Review focuses on inspecting the product with stakeholders, while the Retrospective focuses on inspecting the team's process without them.
    • cThe Review's outcome is a shippable increment, while the Retrospective's outcome is a report on team velocity for management.
    • dThe Review is for stakeholders to approve the increment, while the Retrospective is for the team to plan the next Sprint's work.
    Show the answer

    Answer: b · The Review focuses on inspecting the product with stakeholders, while the Retrospective focuses on inspecting the team's process without them.

    The Sprint Review is an event to inspect the product increment with stakeholders to adapt the Product Backlog. In contrast, the Sprint Retrospective is for the Scrum Team only to inspect its own process and create a plan for improvement.

    Read the full bite: What is the purpose of Sprint Review vs. Sprint Retrospective?

17. Question 17 of 30

    What is the key distinction between a Sprint Review and a Sprint Retrospective?

    • aThe Sprint Review is led by the Product Owner to gather feedback on future features, and the Sprint Retrospective is led by the Scrum Master to resolve technical impediments.
    • bThe Sprint Review is a formal presentation of the Increment to management, while the Sprint Retrospective is a casual team discussion about individual performance.
    • cThe Sprint Review primarily focuses on updating the Definition of Done, while the Sprint Retrospective focuses on refining user stories for the next Sprint.
    • dThe Sprint Review involves the Scrum Team and stakeholders to inspect the product and adapt the Product Backlog, whereas the Sprint Retrospective involves only the Scrum Team to inspect the process and plan improvements.
    Show the answer

    Answer: d · The Sprint Review involves the Scrum Team and stakeholders to inspect the product and adapt the Product Backlog, whereas the Sprint Retrospective involves only the Scrum Team to inspect the process and plan improvements.

    The Sprint Review focuses on inspecting the product with stakeholders to adapt the Product Backlog, while the Sprint Retrospective focuses on inspecting the team's process with only the Scrum Team to identify improvements. Option B is incorrect because the Review is a collaborative working session, not just a formal presentation, and the Retrospective is about process, not individual performance.

    Read the full bite: Sprint Review vs. Sprint Retrospective: Purpose and Audience

18. Question 18 of 30

    Which statement correctly distinguishes the Sprint Review from the Sprint Retrospective?

    • aThe Retrospective includes stakeholders to inspect the Increment; the Review is for the Scrum Team to plan the next Sprint
    • bBoth events are combined into a single lessons-learned meeting at the end of the Sprint
    • cThe Review inspects the Increment with stakeholders to adapt the Product Backlog; the Retrospective inspects the team's process to improve how they work
    • dThe Review is a demo for stakeholders to approve work; the Retrospective is for the team to show the Increment to each other
    Show the answer

    Answer: c · The Review inspects the Increment with stakeholders to adapt the Product Backlog; the Retrospective inspects the team's process to improve how they work

    The Sprint Review is a collaborative inspection of the Increment and Product Backlog with stakeholders, not a demo or approval gate, while the Retrospective is solely for the Scrum Team to inspect and adapt its own processes. Option D is tempting but wrong because it mischaracterizes the Review as a demo and the Retrospective as an internal show-and-tell.

    Read the full bite: Sprint Review vs Retrospective: purpose, focus, and audience

19. Question 19 of 30

    A stakeholder makes an urgent request for new work during an active Sprint. What is the most appropriate initial response?

    • aPolitely inform the stakeholder that no new work can be added to an ongoing Sprint.
    • bAcknowledge the request, explain that the Product Owner prioritizes all new work, and discuss its potential impact on the current Sprint Goal.
    • cImmediately add the request to the Sprint Backlog and begin working on it if it seems small.
    • dEscalate the request to your team lead or manager for them to decide how to handle it.
    Show the answer

    Answer: b · Acknowledge the request, explain that the Product Owner prioritizes all new work, and discuss its potential impact on the current Sprint Goal.

    The most appropriate response involves acknowledging the stakeholder's urgency, explaining that the Product Owner is responsible for prioritizing new work, and transparently communicating the potential impact on the current Sprint Goal. Directly adding work (Option C) undermines the Sprint commitment and the Product Owner's authority.

    Read the full bite: How do you handle an urgent request during a Sprint?

20. Question 20 of 30

    Mid-Sprint, a stakeholder asks you to add an urgent feature. What is the most appropriate developer response?

    • aAdd the feature to the Sprint Backlog and have the team work overtime to finish both commitments
    • bListen to the request, then redirect the stakeholder to the Product Owner without altering the Sprint Backlog
    • cRemove the lowest priority Sprint item yourself to create room for the new request
    • dEstimate the feature immediately and promise to deliver it if it appears small enough
    Show the answer

    Answer: b · Listen to the request, then redirect the stakeholder to the Product Owner without altering the Sprint Backlog

    The developer should gather context but defer ordering decisions to the Product Owner and protect the current Sprint plan by not changing the Sprint Backlog themselves. Option A is tempting but wrong because injecting work and mandating overtime violates Scrum design and hides planning problems rather than solving them.

    Read the full bite: How do you handle a mid-Sprint urgent feature request?

21. Question 21 of 30

    A stakeholder asks you, a developer, to add an urgent feature mid-sprint. What is the most appropriate initial action to take?

    • aBegin working on the feature immediately to be responsive to the stakeholder's urgent need.
    • bAsk the Scrum Master to resolve the conflict between the stakeholder's request and the team's current work.
    • cAcknowledge the request's urgency and connect the stakeholder with the Product Owner to discuss prioritization.
    • dTell the stakeholder that the team cannot accept new work because the sprint plan is locked.
    Show the answer

    Answer: c · Acknowledge the request's urgency and connect the stakeholder with the Product Owner to discuss prioritization.

    The Product Owner is responsible for managing priorities and the product backlog. The correct response is to acknowledge the stakeholder's need while redirecting them to the PO, who can properly evaluate the request against the Sprint Goal. Simply starting the work undermines the PO's role and the sprint's integrity.

    Read the full bite: How do you handle an urgent, mid-sprint stakeholder request?

22. Question 22 of 30

    A team's Daily Scrum consistently exceeds 15 minutes due to in-depth problem-solving. What is the most effective coaching action for the Scrum Master to take?

    • aSuggest using a 'parking lot' to defer deep dives to a follow-up meeting for only those involved.
    • bAllow the meeting to run long, since the team finds the problem-solving sessions valuable.
    • cStrictly enforce the timebox with a timer and cut off discussions that run too long.
    • dInsist that every developer only answer the three standard questions about yesterday, today, and blockers.
    Show the answer

    Answer: a · Suggest using a 'parking lot' to defer deep dives to a follow-up meeting for only those involved.

    The correct action is to facilitate a solution, like a 'parking lot', which respects the Daily Scrum's purpose and timebox while creating a space for problem-solving. Simply cutting people off is authoritarian, while letting the meeting run long ignores the event's purpose.

    Read the full bite: How do you fix a Daily Scrum that runs too long?

23. Question 23 of 30

    A team's Daily Scrum regularly exceeds 15 minutes because developers debate technical solutions. Which Scrum Master action best aligns with Scrum theory?

    • aIntroduce a parking lot and coach the team to self-manage the timebox
    • bInvite stakeholders to attend and help resolve the technical debates quickly
    • cUnilaterally cut off speakers who exceed their allotted time to enforce the limit
    • dExtend the event to 30 minutes so complex topics receive adequate discussion
    Show the answer

    Answer: a · Introduce a parking lot and coach the team to self-manage the timebox

    Introducing a parking lot preserves the 15-minute timebox for inspection and adaptation while coaching self-management aligns with Scrum Master accountability. Extending the timebox masks dysfunction and reduces transparency, while unilateral control replaces self-management with command and control.

    Read the full bite: Daily Scrum runs over 15 minutes; what facilitation techniques realign it?

24. Question 24 of 30

    A Daily Scrum consistently exceeds its timebox due to detailed problem-solving. What is the most effective approach for a Scrum Master?

    • aReiterate the event's purpose, use a 'parking lot' for deep topics, and facilitate separate follow-up discussions.
    • bStrictly enforce the 15-minute limit by cutting off discussions and moving to the next person.
    • cExtend the Daily Scrum timebox to 30 minutes to accommodate all discussions.
    • dRequire each team member to only state what they did, what they will do, and any blockers.
    Show the answer

    Answer: a · Reiterate the event's purpose, use a 'parking lot' for deep topics, and facilitate separate follow-up discussions.

    The most effective approach is to re-educate the team on the Daily Scrum's purpose (planning, not problem-solving), use a 'parking lot' to defer detailed discussions, and facilitate separate follow-up meetings for those topics. Extending the timebox (Option C) fundamentally misunderstands the event's purpose and violates Scrum principles.

    Read the full bite: How to fix a Daily Scrum that runs over its timebox?

25. Question 25 of 30

    What is a primary outcome of a well-defined and consistently applied Definition of Done in Scrum?

    • aIt functions as a flexible set of suggestions for the team to consider when finishing work.
    • bIt makes the team's velocity a reliable metric for forecasting future Sprints.
    • cIt ensures that each Product Backlog Item has unique, specific requirements for its completion.
    • dIt allows individual developers to determine their own quality standards for their assigned tasks.
    Show the answer

    Answer: b · It makes the team's velocity a reliable metric for forecasting future Sprints.

    The card explicitly states that a strict Definition of Done prevents the accumulation of 'undone work' or technical debt, making the team's velocity a reliable metric for forecasting future Sprints. Option C describes Acceptance Criteria, which are distinct from the Definition of Done.

    Read the full bite: What is the Definition of Done and its impact?

26. Question 26 of 30

    How does a shared Definition of Done most directly support empirical process control?

    • aBy serving as a mandatory checklist that managers use to audit the team.
    • bBy making the state of the Increment transparent so inspection is reliable.
    • cBy allowing each Developer to apply their own personal quality standards.
    • dBy ensuring the Product Owner creates detailed requirements before the Sprint begins.
    Show the answer

    Answer: b · By making the state of the Increment transparent so inspection is reliable.

    A shared Definition of Done makes the Increment transparent, allowing stakeholders to inspect real value and adapt based on facts rather than assumptions. The distractor about a manager-imposed audit checklist is tempting because many organizations treat quality as bureaucratic gatekeeping, but Scrum treats the standard as a team-owned commitment that enables empirical control, not external oversight.

    Read the full bite: Definition of Done: how does a shared DoD impact quality and predictability?

27. Question 27 of 30

    What is the primary purpose of a Definition of Done (DoD) in Scrum?

    • aTo track the completion of individual development tasks assigned to developers during a Sprint.
    • bTo ensure everyone has a shared understanding of the quality required to create a releasable Increment.
    • cTo provide a checklist for the Product Owner to validate that all requested features have been coded.
    • dTo list the specific functional requirements for an individual Product Backlog Item.
    Show the answer

    Answer: b · To ensure everyone has a shared understanding of the quality required to create a releasable Increment.

    The Definition of Done is a shared quality standard for the entire Increment, creating transparency and ensuring it is potentially releasable. Confusing it with Acceptance Criteria, which are specific to a single Product Backlog Item, is a common mistake.

    Read the full bite: What is the Definition of Done (DoD)?

28. Question 28 of 30

    What is the primary purpose of a user story in an agile team?

    • aTo provide a detailed, comprehensive specification of a feature for developers to implement.
    • bTo formally document all technical tasks required to complete a feature, such as database changes.
    • cTo ensure every requirement is written in the standard 'As a [persona], I want [goal]' format.
    • dTo act as a placeholder for a conversation where the team will clarify details and requirements.
    Show the answer

    Answer: d · To act as a placeholder for a conversation where the team will clarify details and requirements.

    A user story's main purpose is to be a 'promise of a conversation.' It is a starting point for collaboration, not a rigid specification. Treating it as a detailed spec is a common anti-pattern.

    Read the full bite: What are the components of a well-written user story?

29. Question 29 of 30

    What must be added to the story 'As a shopper, I want a fast checkout page, so that I save time' before sprint planning?

    • aSpecific, testable acceptance criteria defining what fast means
    • bSubjective quality goals stating the page should feel responsive
    • cA technical architecture diagram for the checkout flow
    • dA detailed task breakdown assigned to individual developers
    Show the answer

    Answer: a · Specific, testable acceptance criteria defining what fast means

    The card emphasizes that acceptance criteria must be specific, binary, and testable, and it cites vague goals like 'fast' as a red flag. A task breakdown treats the story as a developer to-do list, which is another common mistake the card warns against.

    Read the full bite: What are the key components of a well-written user story?

30. Question 30 of 30

    Which of the following is explicitly identified as a common pitfall in writing user stories?

    • aThe story includes a clear "As a [persona]" statement.
    • bThe story is broken down into smaller, independent pieces.
    • cThe story describes a technical backend task rather than a user-facing outcome.
    • dThe story requires further "Conversation" with the team for clarification.
    Show the answer

    Answer: c · The story describes a technical backend task rather than a user-facing outcome.

    The card states that "describing a technical task instead of a user-facing feature" is a major red flag because it delivers no direct user value. Conversely, "Conversation" is one of the "3 Cs" and is an essential part of clarifying story details, not a pitfall.

    Read the full bite: What are the components of a well-written user story?