Hi all,
My team is eager to replace our traditional requirements document with user stories.
I would like to know whether there are any clear disadvantages in this approach.
For example, are there any cases that you know of that user stories are not able to capture requirements in a sufficient manner?
Many thanks in advance
I find NON-functional requirements to be more difficult to derive from user stories. That's not to say you can't, just that it's a risk.
sp_key:
Here are a couple of things to think about. They reflect recent discussions within the Linkedin "Agile Business Analysis" group.
* How do you determine the extent of of a user story? Or stated differently, how do you right-size a user story?
* If you have a bunch of user stories, how do you integrate them all together? It is realatively easy to identify standalone requirements (such as via a user story); the real need is to identify the interrelationships between them.
Agree with Tony. User stories in isolation are not sufficient to model a system (software or manual or both). You still need an overview that ties them all together.
Kimbo
Hi there,
How do you write an overview that ties all user stories together?
Thanks
Shiro
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: