Douglas Talbot & Sandy Mamoli One of the most fundamental problems facing a project is how you decide on, document, and manage your requirements. Obviously Agile software development promotes handling this very differently than a Waterfall approach. One mechanism used by Agile projects to track requirements is the "User Story" - but what are they, how are they created, who uses them, when and how, within the development cycle?

1. Stories for Grown-ups Inspired by Mike Cohn and Kelly Waters – thank you 

2. Fixed written requirements

4. Communications challenge

5. Collaboration

6. A continuum

7. User stories: an improvement

8. Timeline Epics & Stories Stories & Tasks Stories & Tasks Implemented Stories

9. Getting to User Stories

11. Now we can have user stories!

15. Stories are for sizing

16. Stories are for prioritising

17. Stories are monitored

18. Stories are monitored

19. Stories are monitored

20. Stories are monitored

21. Stories are for the team and product owner

24. Card

25. Card

26. A section for capturing further information about the user story and details of conversations The Conversation

27. A section to convey what tests will be carried out to confirm the user story is complete and working as expected The Confirmation

28. 6 attributes of a good user story

30. Independent

31. Negotiable

32. Valuable

33. Estimatable

34. Small

35. Testable

37. What next? Challenges Tasks Spikes Feedback

39. Challenges

40. Iteration 0

41. Non-functional requirements

43. Spikes