Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Splitting User Stories
Previous Previous
 
Next Next
New Post 11/21/2016 3:27 AM
User is offline Aaron
1 posts
No Ranking


Splitting User Stories 

Hi all, 

I keep encountering a recurring issue when developing user stories from Epics that the business have devised. 

I come up with a number of stories which capture the requirements of the system users and present them to the development team. At this point we review them along with the acceptance criteria and discuss INVEST and potential solutions. 

However. when we move onto the sizing a number of them come back as being too large and I'm asked to further split the stories. Every time I have had this issue it seems that what the developers want is for me to split them into tasks  for them. 

Has anyone else come across this problem? If so, how do you manage it?

Thanks, 

Aaron

 
New Post 3/3/2017 5:06 AM
User is offline sutnarcha
7 posts
10th Level Poster


Re: Splitting User Stories 

In my opinion, as long as your stories are sized to be started, developed and completed involving Dev & Test within one sprint cycle, they are good from a BA perspective.

Dividing them into tasks is Not a BA responsibility.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Splitting User Stories

Community Blog - Latest Posts

Bert Wagner
Bert Wagner
It’s 4:30 pm on Friday and Mr. Manager comes along to tell you that he needs you to run some important ad-hoc analysis for him. Previously this meant having to stay late at the office, writing cumbersome queries to extract business information from transactional data. Lucky for you, you’ve recently started using Temporal Tables in SQL...
0 Responses
Ronak Sanghavi
Ronak Sanghavi
Current State For many years now, the most commonly used metaphor on Business Analysis has been the “Bridge”. However, in recent past, some in the BA community have started revisiting the metaphor resulting in a debate on how relevant it is. Of course, the value business analysis can provide for an organization does not depend on how i...
1 Responses
SarikaA
SarikaA
Pega systems(Software Company) is the leading provider of business process management (BPM) and customer relationship management (CRM) software solutions. Pega systems motto is “Build For Change” and their goal is to “eliminate software coding” and “automate manual work”. Pega systems has bee...
0 Responses




Latest Articles

The Crucial Art of Pre-Project Problem Analysis
Aug 13, 2017
0 Comments
Business analysis is a broad discipline and we have a whole range of tools and techniques at our disposal. We may get involved within projects, but al...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC