Writing Agile Requirements
-
Upload
robert-dempsey -
Category
Technology
-
view
9.846 -
download
1
description
Transcript of Writing Agile Requirements
Writing Agile Requirements
adsdevshop.comWith Robert Dempsey
1
Welcome!
Robert Dempsey
CEO & Founder
LinkedIn: robertwdempsey
Twitter: @rdempsey
2
Fundamentals of Agile
http://agilefundamentalsphilly.eventbrite.com/3
Agenda
4
Agenda
• Why
• Who
• What
• When
• Example
• Q&A
• Pick a winner
5
How to Ask Questions
• Twitter: @rdempsey
• In the webinar chat window
6
Quick Poll
7
Agenda
‣Why
• Who
• What
• When
• Example
• Q&A
8
Do It For The Team
9
Do It For The Users
10
Agenda
• Why
‣Who
• What
• When
• Example
• Q&A
11
Hello Product Owner
12
Agenda
• Why
• Who
‣What
• When
• Example
• Q&A
13
Three Steps
• Get the initial list
• Write the user stories
• Add the acceptance criteria
14
#1: Initial List
• Start with the who and whatBulleted-list
Non-technical
• Start with a story of who is doing what in the applicationA literal story
15
#2: Write the Stories
As a [role]
I can [do something]
So that I [get some benefit]
16
Quick Tip #1
If you can’t state a benefit, then you might not need that feature.
17
#3: Acceptance Criteria
• Defines done
• As much as you need for task breakdown
• Mockups
• Design is 1-2 sprints ahead of development
18
Agenda
• Why
• Who
• What
‣When
• Example
• Q&A
19
When We Write
• Write an initial list before the project starts
• Have your high priority stories fleshed out 2-3 sprints ahead
20
Quick Tip #2
Try to hold off on writing acceptance criteria until closer to the time you are going to design or develop a feature.
21
Agenda
• Why
• Who
• What
• When
‣Example
• Q&A
22
MindMapping
23
MindMap Template
24
Social Network
25
Start With The Roles
26
Add Role Details
27
What Can They Do?
28
What’s the Benefit?
29
Quick Tip #3
If we can describe each role before writing what they can do, then the what and benefit comes much easier
30
Use Case?
http://www.w3.org/2001/sw/sweo/public/UseCases/Chevron/figure.png31
Quick Tip #4
• Donʼt worry about the “so what” part
• More benefits are good
32
The Full Monty
33
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
Agenda
• Why
• Who
• What
• When
• Example
‣Q&A
35
Q&A
• Twitter: @rdempsey
• In the webinar chat window
36
Thank You!
Robert Dempsey
CEO & Founder
LinkedIn: robertwdempsey
Twitter: @rdempsey
Atlantic Dominion Solutions 321-274-4684http://www.adsdevshop.com
38