User Stories Are Not Requirements (User Stories vs. Requirements)

User stories and use cases are just the starting point for documenting a certain type of requirement. User Stories don't fit the bill when it comes to the development portion of the project. User stories ARE NOT requirements.

You will Learn
1. The instances when user stories are appropriate to use. (Agile)
2. Consider the developers' perspective when producing requirements.
3. 5 key questions to address when documenting requirements.

--
#businessanalysis #userstory #requirements

[rogermouton]

Agree. I think this applies to everything. There's no one tool that's right for every job; there's the right tool IN CONTEXT. In my experience, user stories are useful, as you indicate, for giving a high-level concept of what the system is required to do. But they're next to useless for developers. If you're going to code something, you need a know, in very precise detail, what the system is required to do. For anyone that knows anything about software development, user stories are utterly inadequate for this purpose.

[sdevane]

arent user stories just thin slices of a use case - as ultmately you'll need the use case level detail to fulfill the business require/ process - right?