1. Setup slide 2. I'm here to talk about elements that make up user stories. It's supposed to be a starting point and does not discuss priority, planning or other elements of AGILE. Even if you don't write user tories, you should expect certain things. 3. Don't consider it a chore, be creative and try to discover edge cases. 4. This isn't strictly true but it's a collaborative process. Don't enforce your style on the rest of the team. Adapt as needed. 5. Do as much work upfront as you can and get rid of ambiguity. Agree a level of acceptability with the developers and testers. 6. We've all seen this. If you leave it to interpretation, people will do just that. Keep your AC in check. 7. You really can! Use as many visual aids as you can... they don't have to be perfect. Use a tool you're comfortable with. 8. Prepare to re-write. This should ALWAYS happen. Stories MUST NOT replace discussions. 9. Write stories that an end-user could do and then have a coffee. 10. Think about everything. It's okay to sit at your desk and just think. Consider the ridiculous and ask all the questions that you can. 11. Stories should be a surprise - planning should involve stories that everyone has previously seen. Do backlog reviews. 12. Write stories as if you had to test them and ask a tester to review the stories with you. Make sure you give them the level of detail that they need. 13. Keep stories small (but not too small). Apply common sense and experience. 14. Even if a story has zero development points, keep it in the sprint. It's a good marker for everyone to make sure it is done. 15. Don't expect to keep the same approach forever. Teams, projects and methods change. 16. Recap 17. Thank you

1. Hello, I’m Leo.

2. Writing Great User
Stories
with added Stormtroopers
Leo Barnes
Business Analyst
@productoven

3. Some
people
find
the
story
writing
process
boring

4. The only
rules are…
…there are
no rules!

5. Good user stories
mean fewer
headaches later on

6. Don’t do this Do do this
As a user on the website, I
expect to see a search box
GIVEN I on the homepage
WHEN I look at the header
THEN I expect to see a search box
GIVEN I have selected the search box
WHEN I begin typing
THEN I expect to see search suggestions
GIVEN I on the homepage
WHEN I select a suggestion
OR click ‘Go’
THEN I expect to be taken to a search
results page

7. Everybody can draw

8. Write, review and re-write

9. Reward
yourself
with
a
coffee

10. Make sure you can’t find any
more questions
to ask

11. Review your stories with the people doing the work

12. Make it testable

13. Make
stories
small
enough
to
estimate

14. Not all stories need to have development tasks

15. Be
prepared
to
change

16. Remember
•Stories can be fun!
•Make your own rules
•Be thorough
•You can (and should) draw
•Rewrite, a lot
•Reward yourself with coffee
•Ask all the questions
•Talk to your developers
•Make it testable
•Small enough to estimate
•Include stories with no tasks
•Prepare to change

17. MAKE
GOOD
DEATH
STAR
As an Imperial Overlord, I expect to have a dedicated
parking space for my Tie-Fighter
Thank You
@productoven