Are User Stories The Same as Requirements? - Mike Cohn
Are user stories the same as requirements? Not quite, but they’re close.
Rather than thinking of a user story as a requirement, I find it more useful to think of each story as a pointer to a requirement.
Most commonly, every story is a placeholder for a future conversation between the team and its stakeholders. During that conversation, stakeholders will convey the details about what is needed. If more detail is needed than can be conveyed in a conversation, the story may point to a flow diagram, a sketch of the user interface, sample data, instructions on how to perform a calculation, or so on.
A user story itself is too vague to be considered a requirement. You’re better off thinking of a story as a pointer to a requirement.
How to connect with AgileDad:
- [website] https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/

Ver todos los episodios