Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  When user stories should not be used?
Previous Previous
 
Next Next
New Post 3/19/2013 3:50 PM
User is offline sp_key
7 posts
10th Level Poster


When user stories should not be used? 

 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

 
New Post 4/24/2013 12:47 PM
User is offline dldelancey
61 posts
8th Level Poster


Re: When user stories should not be used? 

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.

 
New Post 4/25/2013 12:05 PM
User is offline Tony Markos
493 posts
5th Level Poster


Re: When user stories should not be used? 

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.

 

 

 
New Post 4/26/2013 3:31 AM
User is offline Kimbo
454 posts
5th Level Poster


Re: When user stories should not be used? 

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

 
New Post 8/8/2014 6:27 PM
User is offline Shiro
5 posts
10th Level Poster


Re: When user stories should not be used? 

Hi there,

How do you write an overview that ties all user stories together?

Thanks

Shiro

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  When user stories should not be used?

Community Blog - Latest Posts

Context:  Intro Change Request Definition Reasons for CRs Adaptive, predictive and mixed projects Flow of processing change requests Change Management Workflow Tools and Techniques 1. Intro  The World will never stop changing, as well as human needs and desires. The business environment evolves continually. An or...
For many people, a career in business systems analysis can be an ideal opportunity to use their skills in technology and business. Business systems analysts bring together the best of both worlds – technical know-how and business acumen – to help organizations become more efficient and effective. Here are some of the key benefits of pur...
There is no doubt in my mind that curiosity nurtures the mind when it comes to T shaped skills.  T shaped professional are specialist in something(the vertical line) and also have a wide range of skills and knowledge in a broad range of subjects(the horizontal line) and are are highly sought after in the workplace.  I’ve recently...

 






 

Copyright 2006-2023 by Modern Analyst Media LLC