This presentation covers the why, who, what and when of writing requirements for Agile projects. Then we look at an example and how we can use mindmapping to brainstorm
14. Three Steps
• Get the initial list
• Write the user stories
• Add the acceptance criteria
14
15. #1: Initial List
• Start with the who and what
Bulleted-list
Non-technical
• Start with a story of who is doing what in the application
A literal story
15
16. #2: Write the Stories
As a [role]
I can [do something]
So that I [get some benefit]
16
17. Quick Tip #1
If you can’t state a benefit, then you might not need that
feature.
17
18. #3: Acceptance Criteria
• Defines done
• As much as you need for task breakdown
• Mockups
• Design is 1-2 sprints ahead of development
18
34. User Story Example
As a Site Visitor, I can browse marketing pages, so that I can learn
more about the benefits
Acceptance Criteria
The marketing pages should be controlled by a CMS
The pages should render in less than 2 seconds
Should render properly in IE8, FF 3.x, Safari 3.x, and Google Chrome
34