The Client Changed Their Mind!
A client requests a new feature that was not included in the original requirements. Before adding it, the team should first do this.
What is Clarify the Request and Evaluate Its Priority?
A team writes a user story describing a feature but never identifies who will use it. Before development, the team should add this information.
What is the User Role or Persona?
A Scrum Team notices that several task cards have remained in the "In Progress" column for days. The team should discuss these to determine what is preventing progress.
What are Blockers or Impediments?
During the Daily Scrum, Developers discover that two people are completing the same task. They should coordinate their work and do this.
What is Adjust the Daily Plan to Eliminate Duplicate Effort?
A feature has been developed, but the required testing has not been completed. The team should classify the feature as this.
What is Not Done?
A client says their new app must be "fast and easy to use." Before development begins, the team should do this.
What is Clarify the Requirements and Make Them Measurable?
A user story states, "As a customer, I want to save my payment information," but it does not explain the benefit. The team should clarify this part of the story.
What is the User's Goal or Reason for Wanting the Feature?
A team's Burn-Down Chart shows that remaining work has not decreased for several days. The team should investigate this before deciding how to proceed.
What is Why Work Is Not Being Completed?
During a Sprint Review, stakeholders identify a valuable feature they want added in the future. The Product Owner should consider doing this.
What is Adding or Reprioritizing the Feature in the Product Backlog?
A feature meets most requirements, but one required acceptance criterion has not been satisfied. Before accepting the story, the team should do this.
What is Address the Unmet Criterion and Verify the Result?
A client wants to know which features customers actually need rather than relying on assumptions. The team should gather information directly from these people.
Who are Actual or Potential Users?
A team develops a feature based on assumptions about customers, but users report that it does not solve their actual problems. The team should revisit these.
What are User Needs and Pain Points?
During Sprint Planning, the team realizes it cannot realistically complete all the proposed work. The Developers should do this with the Product Owner.
What is Negotiate a Realistic Sprint Scope Based on Capacity and the Sprint Goal?
A Scrum Team has experienced communication problems during several Sprints. This meeting is the best opportunity to identify improvements to how the team works.
What is the Sprint Retrospective?
A team finishes a feature, but it fails the security checks required by the Definition of Done. The team should do this before considering the feature complete.
What is Resolve the Security Problem and Complete the Required Checks?
A client requests a feature that conflicts with an existing security requirement. Before proceeding, the team should do this.
What is Evaluate the Conflict and Clarify the Requirements with the Appropriate Stakeholders?
A user story is too large to complete during a Sprint. The team should take this action to make the work manageable.
What is Break the Story into Smaller, Valuable User Stories?
Halfway through a Sprint, a Developer discovers that a task is more complex than expected. The team should make this information visible and do this.
What is Reevaluate the Work and Adapt the Sprint Plan?
During Sprint Planning, the Product Owner explains the highest-priority backlog items, but Developers believe the work is too large for one Sprint. The team should do this.
What is Refine or Split the Work and Develop a Realistic Sprint Plan?
A Product Owner wants to release a feature immediately, but the work does not meet the team's Definition of Done. The Scrum Team should do this.
What is Make the Incomplete Work Transparent and Avoid Treating It as a Completed Increment?
A client requests three major new features halfway through a Sprint, but adding them would threaten the Sprint Goal. The team should consult this person to determine how to handle the changes while protecting the Sprint Goal.
Who is the Product Owner?
A team cannot determine whether a completed user story meets the client's expectations because the requirements are vague. Before accepting the work, the team should establish these.
What are Clear, Testable Acceptance Criteria?
A team repeatedly carries unfinished work into the next Sprint because it commits to more than it can complete. During its next Sprint Planning session, it should use past performance and available capacity to do this.
What is Select a More Realistic Amount of Sprint Work?
During a Sprint Retrospective, the team identifies that unclear responsibilities repeatedly caused delays. Rather than simply discussing the problem, the team should take this action.
What is Agree on a Specific Improvement and Put It into Practice During the Next Sprint?
A team repeatedly discovers defects after declaring features complete. To reduce future problems, the team should review its quality practices and this shared standard.
What is the Definition of Done?