Writing Agile Requirements
22 likes13,938 views
The document outlines a webinar hosted by Robert Dempsey on writing agile requirements. It emphasizes the importance of defining user stories and acceptance criteria through a structured process, including creating an initial list, outlining user roles, and prioritizing features. Key tips are provided to enhance the effectiveness of agile requirements gathering for product development.
![#2: Write the Stories
As a [role]
I can [do something]
So that I [get some benefit]
16](https://image.slidesharecdn.com/writingagilerequirements-100210142553-phpapp01/85/Writing-Agile-Requirements-16-320.jpg)
Writing Agile Requirements
- 1. Writing Agile Requirements adsdevshop.com With Robert Dempsey 1
- 2. Welcome! Robert Dempsey CEO & Founder LinkedIn: robertwdempsey Twitter: @rdempsey 2
- 3. Fundamentals of Agile http://agilefundamentalsphilly.eventbrite.com/ 3
- 4. Agenda 4
- 5. Agenda • Why • Who • What • When • Example • Q&A • Pick a winner 5
- 6. How to Ask Questions • Twitter: @rdempsey • In the webinar chat window 6
- 7. Quick Poll 7
- 8. Agenda ‣Why • Who • What • When • Example • Q&A 8
- 9. Do It For The Team 9
- 10. Do It For The Users 10
- 11. Agenda • Why ‣Who • What • When • Example • Q&A 11
- 12. Hello Product Owner 12
- 13. Agenda • Why • Who ‣What • When • Example • Q&A 13
- 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
- 19. Agenda • Why • Who • What ‣When • Example • Q&A 19
- 20. When We Write • Write an initial list before the project starts • Have your high priority stories fleshed out 2-3 sprints ahead 20
- 21. 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
- 22. Agenda • Why • Who • What • When ‣Example • Q&A 22
- 23. MindMapping 23
- 24. MindMap Template 24
- 25. Social Network 25
- 26. Start With The Roles 26
- 27. Add Role Details 27
- 28. What Can They Do? 28
- 29. What’s the Benefit? 29
- 30. Quick Tip #3 If we can describe each role before writing what they can do, then the what and benefit comes much easier 30
- 31. Use Case? http://www.w3.org/2001/sw/sweo/public/UseCases/Chevron/figure.png 31
- 32. Quick Tip #4 • Donʼt worry about the “so what” part • More benefits are good 32
- 33. The Full Monty 33
- 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
- 35. Agenda • Why • Who • What • When • Example ‣Q&A 35
- 36. Q&A • Twitter: @rdempsey • In the webinar chat window 36
- 37. Pick Me Pick Me! [email protected] 37
- 38. Thank You! Atlantic Dominion Solutions 321-274-4684 http://www.adsdevshop.com Robert Dempsey CEO & Founder LinkedIn: robertwdempsey Twitter: @rdempsey 38