Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  User Stories: What is the best way to capture and manage
Previous Previous
 
Next Next
New Post 9/6/2016 5:55 PM
User is offline Jayman21
28 posts
9th Level Poster


User Stories: What is the best way to capture and manage 

Hello All,

I need you input/help on the best way to capture and manage user stories through out the delivery of a solution (i.e Case or problem Management systems - development and implementation).

1. Do you use a tool to capture and management? what tool? what tools are available for such?

2. Do you capture and manage manually i.e. word documents, spread sheets etc? do you have templates to share?

3. in the management of US do you assign unique numbers to each US? 

4. Do you versions them?

5. How do you align Acceptance Criteria, Test Cases to your US? 

6. How do you know when you have an epic and not a US?

7. How do you decompose the user stories into smaller sets of US?

8. How do you generate and document technical stories from existing US?

Thanks

Jay

 

 
New Post 3/28/2019 5:05 PM
User is offline Kris 03
9 posts
10th Level Poster


Re: User Stories: What is the best way to capture and manage 

My organization uses JIRA and I feel its one of the best tools I've ever used.

1. Do you use a tool to capture and management? what tool? what tools are available for such?

JIRA (other tools - IBM RTC, Mingle, Trello)

2. Do you capture and manage manually i.e. word documents, spread sheets etc? do you have templates to share?

If using tool like mentioned above, would not manage in Word document or Spreadsheet. If I've to (given no tool is available), then in word or spreadsheet - but these ideally should be in sharepoint. 

Templates vary per project. Ideally table with columns: UseCase#, AS A, I WANT, SO THAT 

3. in the management of US do you assign unique numbers to each US? 

Tools would assign unique numbers. Otherwise, US1 for main components. US1.1 for sub components.

4. Do you versions them?

Of course!

5. How do you align Acceptance Criteria, Test Cases to your US? 

Acceptance criteria should signify what is the acceptable quality of the US output.

6. How do you know when you have an epic and not a US?

Thumb rule: If the US cannot be completed in a sprint (or 2), its too big (epic).

7. How do you decompose the user stories into smaller sets of US?

Read: Mountain Goat SPIDR user story splitting techniques

8. How do you generate and document technical stories from existing US?

What kind of technical stories? My frontend stories have backend API to be implemented. I write acceptance criteria for API functionality.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  User Stories: What is the best way to capture and manage

Community Blog - Latest Posts

Gen1us2k
Gen1us2k
Most of the IT projects imply constant cooperation between the team members and customers. Although it might be often overlooked, the role and the importance of the client within the project is very crucial. Thus, it is in your interest to build a strong relationship based on trust. However, gaining trust on a single occasion is not a dealmaker &md...
0 Responses
emorphistechno
emorphistechno
Introduction In today's world, most enterprises work aggressively to achieve a higher level of business growth, which is made possible by leveraging one of the best automation technologies. One such technology is Robotic Process Automation (RPA) that plays a vital role in streamlining the customer experience in the most profitable manner.&nb...
0 Responses
Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses






Latest Articles

Copyright 2006-2020 by Modern Analyst Media LLC