Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  How to avoid implementation details in a User Story
Previous Previous
 
Next Next
New Post 4/3/2017 1:20 AM
User is offline Vijit
1 posts
No Ranking


How to avoid implementation details in a User Story 

Hello to one and all.

 

I am writing a user story and have stumbled upon this problem of avoiding the implementation detail in it. I already have a UI design created for the project.

 

Say, for example, I am writing a story for the login functionality. The login has two textboxes and a button. As I cannot use the terms textbox & button, as they are HTML implementation details, then how do I write the story.

I have written the following lines:

The Login module should have the following options:

  • The module should have an option (textbox) to enter a username
  • The module should have an option (textbox) to enter a password
  • The module should have an option (textbox) to submit the login details

Also, I am using the term Login Module instead of Login Page as Page is an HTML term

As I come from a development background I find it difficult to wrap my head around the concept of staying away from the implementation detail.

I am also uncomfortable to use the term "should" in my user story, but I have been asked to use it instead of can, will, shall etc.

This is my first project and I am quite nervous. I have read a lot on requirement gather and am quite overwhelmed.

Can someone please guide me with the requirement process for the following:

  • Requirement template
  • Mapping and tracing requirement with User stories

 

I hope I was able to convey my problem. Any form of help will be appreciated. Thank you for reading.

 
New Post 4/17/2017 8:05 AM
User is offline Patrick Schmöllerl
5 posts
10th Level Poster


Re: How to avoid implementation details in a User Story 

Hi Vijit,

I am not a nativ speaker, but the words "textbox" or "Login Module" don't sound like implementation details to me. You obviously don't want to write: "As a user I want to call POST userLogin with the following request-parameters ...". That would be over the top :-)

If you should include details on the implementation in your user-story or strictly avoid it, depends on your project. In my experience it very often depends on the size of the project (how many people are in between your specification and the developer) or your precise role (vgl. http://www.modernanalyst.com/TheProfession/Roles.aspx)

However, there is a a part of a user-story called the"Conversation".This is the best place to add further implementation details (vgl. http://www.modernanalyst.com/Careers/InterviewQuestions/tabid/128/ID/533/What-are-User-Stories.aspx)

 
New Post 5/10/2017 11:34 PM
User is offline Kimbo
433 posts
5th Level Poster


Re: How to avoid implementation details in a User Story 

Hi Vijit,

Don't stress too much about using solution in a user story. Your acceptance criteria will be hard to write if you do. Are you concerned because the end solution is not decided? 

If your solution includes other channels for login e.g. fingerprint, iris scan; you'll need separate user stories anyway. If not, then you'll need text boxes and buttons and stuff.

Kimbo

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  How to avoid implementation details in a User Story

Community Blog - Latest Posts

LN Mishra, CBAP
LN Mishra, CBAP
Traceability is one of the lesser understood aspects of business analysis. It is indeed quite hard to maintain good traceability unless automated. This is why BABoK® warns us being theoretical about traceability. In this article, I would like to explain traceability concepts with help of an example. BABoK® definition of traceability: ...
1 Responses
Hitendra 01
Hitendra 01
Most IT jobs have a clear, specific job description and career path. However, the business analyst career path tends to vary, as do the descriptions from job to job. The business analyst career path is best. Because, “There are career tracks that zigzag back and forth between IT and business. Someone might start as a business analyst, and the...
0 Responses
Arash
Arash
What is Data Analytics? To understand the meaning of Predictive Analytics, let’s describe what Data is first. Data is a collection of facts, information, and observations related to a context. The data can be either structured or unstructured, stored in databases, spreadsheets, files, etc. Data analytics is the science of examining the data ...
0 Responses


Upcoming Live Webinars



Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC