-
Notifications
You must be signed in to change notification settings - Fork 19
Defintion of Ready
chime-mu edited this page May 9, 2017
·
1 revision
- Everybody working in the sprint understand the story
- The story has been estimated, supporting a common understanding of the story
- It's clear from the story:
- Who the user is
- What functionality should be developed/removed/changed
- What the purpose of this change is. How will it benefit the user?
- Other stories that this story is dependent on is Done
- Acceptance criteria is either obvious or explicitly stated
- For small user facing stories, we believe we can make a useful design within the sprint. It doesn't have to be perfect, just good enough to release and possibly to create a new story with further adjustments
- For large user facing stories, a design proposal (sketch, wireframe, ...) has been prepared, possibly tested by user and approved
- The UX and graphic design process
- How do we signify a design as done?