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
441 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

Neetu
Neetu
As a business analyst, we capture client requirements in different documents like BRD (business requirement document), FSD (functional specification document) and SRS (software requirement specification). If we are capturing the requirements in these documents, then why the document nomenclature is different? The answer is Yes. We are capturing the...
2 Responses
Jason White
Jason White
With time, we have evolved from oiled lamps to ever-present electricity, printing every page manually to now producing thousands of copies a day and so on. But what is the one thing these distinct things have in common? Yes, technology.One such branch of technology that has crossed leaps and bounds and turned into a  working technology fr...
1 Responses
Digital Business Analysis
Digital Business Analysis
Nowadays, companies like Audi and HSBC, use IT systems in everything they do. Does that make them to be IT companies rather than banks? Most would probably agree that HSBC is a bank, just as Audi is a car manufacturer. But what about digital banks such as Chime or companies offering digital products? In digital companies, most of the employees work...
1 Responses






Latest Articles

Why Modeling Is an Essential Business Analysis Technique
Mar 22, 2020
0 Comments
Visual analysis models provide a powerful set of tools that let business analysts depict system information at various levels of abstraction. These mo...
Copyright 2006-2020 by Modern Analyst Media LLC