Member-only story
Acceptance criteria, the most important part of the Scrum Story
A Story has several pieces of information. If I would keep only one of them (except the progress part), I would keep the acceptance criteria.
This article is a part of my Scrum series, see with free links (including to this article):
I like Scrum. The good Scrum.
The case
A feature development is splitted to Epic-Story-Task hierarchy. The Product Owner (PO) focuses only on Epics and Stories, the Task is the business of the team members. When the PO gives us the Story description, which has specifications, the developers extend it some implementation-specific information. Sometimes the implementation-specific info is too long or complex as clear-text in the Story description part and it’s moved to the company intranet (for example: Confluence).
When everything is clarified, the acceptance criterias should be finished, before the team votes the Story Points. I always ask the PO to write what they would like to see on the demo as acceptance criterias. I ask the team members to write acceptance criterias for the selected “ilities”, based on PO’s requirement and their experience.
The cross-check of the acceptance criterias is checking the coverage of requirements and they selected “ilities”. If one of them is…
