All About Agile | Agile Development Made Easy

ScrumMaster Tales – Waiting Too Long to Create Acceptance Criteria

by Mark Levison, 13 January 2013 | The Agile Blogosphere

This content is syndicated from Agile Pain Relief by Mark Levison. To view the original post in full, click here.

The recent Backlog Refinement session helped split the upcoming User Stories.

The team was able to get from a very large Story: “As a first time book buyer I want to read a trustworthy review before I buy a book” to:

We’re in better shape than we have been with previous Sprint Planning meetings but the team lacks concrete acceptance criteria.


During the first half of a Planning meeting the team is trying to determine its goal for the Sprint. Specifically, it’s trying to answer the question, “What stories can we commit to?”  To have a realistic commitment the team needs small Stories and a clear understanding of what they will look like when they’re done.


Brad reads the first Story aloud, “As a first time book buyer I would like to read a review so I can see if a book is worth reading.” He sees an entire new web page, separate styling and a whole lot of infrastructure to support it. Doug, on the other hand, sees a small addition to each book page. He says that no new style sheets need to be developed. After a few more minutes of debate Product Owner Sue intervenes by saying that reviews will just live on the main page for now. In addition, each review must be under a thousand words and in plain text only.

Debate continues around each successive Story until two hours have passed; and the team is still unsure what they can commit to. ScrumMaster John has been doing his best to bring team members back to focus, but it’s been a struggle.


The team is struggling because they don’t have clear acceptance criteria. As a result, they don’t agree on the size and can’t agree on what to commit to. They’re spending the Planning meeting focusing on the question of, “What are we trying to do?” as opposed to, “What should we be doing?”

Acceptance Criteria (from a forthcoming Agile Atlas article):

The goals of Acceptance Criteria are:

Creating good acceptance criteria is a collaborative effort. Usually, they’re created by the Product Owner working with several other team members. When created in isolation they fail to meet the first two values.

In addition when we create them a few days before the Sprint Planning meeting, team members have time to consider just what they mean, how they fit the product and what is missing.

Let’s wind the clock back for the team to three days before our Sprint Planning meeting.


Sue asks Ian, Brad and Tonia to come spend half an hour with her. Their goal is to hammer out the acceptance criteria for each Story that might be committed for the next Sprint.

At the end of their white-boarding session they’ve got very rough sketches for the first three Stories that clearly limit their scope. In addition there are also textual criteria:

A few days later during the Sprint Planning meeting the team spends far less time debating and manages to get to commit to their Stories within the first hour vs. their traditional two or more hours.

When do you write your Acceptance Criteria?


Leave a Reply

What is 1 + 10 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)