Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  User Stories & Best practices
Previous Previous
 
Next Next
New Post 5/13/2015 8:54 AM
User is offline Michael
1 posts
No Ranking


User Stories & Best practices 

 

Hi

My question is around how to structure a user story for a user filling out an online application for a personal loan. For complexity, lets assume that the user must enter 3 different sets of contact details (name, address, contact number, email, & role). They must also provide supporting documentation (pdf, excel, word documents) and they need to answer 20 mandatory questions.


My thinking is that I should firstly create a Epic with the following description: "As a applicant, I want to fill up the Personal Loan form, so I can apply for a loan". I then need to create separate user stories for the 3 different sets of contact details. I should then create 20 additional user stories for each of the mandatory questions (as each question may have different acceptance criteria) and a further user story to cover the uploading of the supporting documentation. 


My concern at this point is that at no point have I created a user story to cover actually creating the form. I can create a separate user stories to cover the submit and cancel application processes.

Am I correct in my approach, or can you suggest a more effective approach? The approach I've used covers the requirements, but I don't believe it does it in a cost effective manner.

Michael.
 
New Post 5/17/2015 12:51 AM
User is offline Kimbo
456 posts
5th Level Poster


Re: User Stories & Best practices 

Hi Michael,

I'm certainly no expert but the idea is to pitch a user story at what your scrum team can achieve to the definition of done within one cycle. That may mean you have too many or too few. At face value it looks like too many to me.

Kimbo

 
New Post 6/10/2015 10:33 PM
User is offline Matt Adams (Business Analyst)
6 posts
10th Level Poster


Re: User Stories & Best practices 

You could create a feature for each section of the form (including that each feature must be on the same form) within the epic and then stories within each feature. That way if it is too big to create in one cycle, you can set a sprint goal as one or two features instead of the whole form.

Ken Rubin has a great explanation in his book 'Essential Scrum: A Practical Guide...'. 

Also, if you're using Scrum techniques.

The developers should pick up these details through conversations during planning, estimating or any other form of conversation you have. And then you can capture notes to each Story, Feature or Epic.

 

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  User Stories & Best practices

Community Blog - Latest Posts

I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...
Now, I know, I don’t know what kind of new intro BPO may require, but at least I can promise you upfront that I have something different to say about Business Process Outsourcing or simply BPO. What is it? This hasn't been a call center job or a sales job as we all think. It is a mammoth profile, and firms are grappling to ge...
Leveraging Blockchain Technology for Enhanced Data Security in Business Operations
In an age where data breaches and cyberattacks are becoming more frequent and sophisticated, businesses are searching for robust solutions to safeguard their data. Blockchain technology has emerged as a promising tool in this quest, offering a way to secure data with unparalleled reliability. Although initially known for powering cryptocurrencies l...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC