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 2: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 11:47 AM
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 11:05 AM
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 2:31 AM
User is offline Kimbo
438 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 5: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

Heta Raval
Heta Raval
In a current scenario, when you are eliciting software service-based requirements then, you may be able to derive requirements in certain varieties. In the beginning, they can be just functional or non-functional requirements. But when you come across many other requirements as time goes, you can conclude requirements into several categories and wi...
0 Responses
Heta Raval
Heta Raval
It is essential to write an impressive approach which helps you to make a client convinced about your understanding of his requirement. The satisfactory approach would help you to be on the same page with the client. So, your chances to get the contract/project would raise. In order to provide a technical solution, a business analyst needs to recog...
2 Responses
Arash
Arash
Machine Learning (ML) models are intended to positively impact business efficiency. By understanding how these models are created, how they function, and how they are put into production, one can fully utilize their potential to make a difference in every day scenarios.   What is a Machine Learning Model? By creating cases within a narrow d...
0 Responses




Latest Articles

Six Estimation Safety Tips
Oct 13, 2019
0 Comments
Estimation is a chronically thorny issue for software practitioners. Most people need to prepare estimates for the work they do, but in our industry w...
Copyright 2006-2019 by Modern Analyst Media LLC