How do we track the details of a user story? [closed]

Question

So if a user story is a something nebulous like:

As a sales rep, I would like to capture the contact information so that I can follow up later on.

I'm not even sure if that's a valid user story but I'm sure it's close enough.

Then there are details/tasks for implementing that user story. And I'm sure "The sales rep should be able to tab from one textbox to another." is one of the requirements. How do we capture/track this? Is this part of the user story or is it something that's to be considered separately?

Answer 1

A user story captures the essence of a feature, not the details, a story is a support for the discussion.

So, to answer your question, details are transmitted orally during a discussion, because face to face discussion is the most effective communication media. If you feel the need, details can be captured as notes on the back of the card (if you are using cards) or... in a "notes" field if you are using an electronic tool. Actually, I usually use a "how to demo" field too to capture a high-level description of how this story will be demonstrated at the sprint demo and use very brief "notes" for any other info, clarifications, references to other sources of info, etc (credits to Henrik Kniberg's famous Index card generator). If find this very handy, especially when using executable specifications.

PS: your story is perfectly valid and its a good practice to include the benefits in your template ("As a role, I want action so that benefits").

Answer 2

User stories should be short statements in 1 to 3 sentences.

http://en.wikipedia.org/wiki/User_story

I want to be able to tab from one textbox to another is another user story.

You can track these things in a tool like www.rallydev.com, or just any type of task tracking tool (SharePoint, Excel even ... etc.).

Next thing you do is prioritize.

Answer 3

Just taking a rough stab...

As a sales rep,
I want all data entry and navigation to be accomplished using the keyboard
so that I don't have to take my hands off the keyboard
(and so that we comply with accessibility guidelines).

Or

As a business,
We want all our products to be fully usable using only keyboard input
So that we can sell to customers who require accessible software.

Answer 4

The first part belongs to a "business requirements" document (usually written by a business analyst). The first generations of this document are quite high level, but the final versions (several iterations later) are pretty detailed.

http://www.tdan.com/view-articles/6089

The second part (about tabbing) is part of another document - "UX spec" (shows all screens and describes user interaction). This one is usually written by a different person/team (Product or UX team).

http://uxdesign.com/ux-defined-2

http://www.uxmatters.com/mt/archives/2007/05/sharing-ownership-of-ux.php

Answer 5

Yes, that is problem we also have a lot. On the one hand, user stories need to be conscise, on the other hand all the nitty gritty details must be put somewhere.

We use XPlanner, and we solve this by putting the short description into the text body of the user story. Then we use XPlanners "notes" feature (arbitrary text or files that can be attached to a user story) for the details.

That way we can add as much information as necessary to a user story, without cluttering up the user story text itself. You can also refer to external documentation, if you don't want to have everything in XPlanner.

This approach works quite well for us.

Answer 6

Agree with others, that this is viable story, but capture the (derived) requirements may be better captured elsewhere.

Software Developers and Business types are familiar with different terminology some what may simple to understand by one (data structures) may mean nothing to another. The User Stories is a tool or a means by which business user can convey a message as a starting point which is expanded on (with tests, details, etc).

Oral Communication can be effective, but the effectiveness is dependent on the receivers ability to hear and comprehend the meaning of the message. This is where oral communication can fail. Different types of communication offerring more or less formal forms of communication. Vocal communication is an "informal form of communication" which risks the message being misheard, misinterpretted, and misunderstanding. Just like the game played as a child, where one child whispers a message to another child, who tells another, until all have heard it...When the last child tells the message to the group it usually has been misinterpreted then misinterpretted again, causing a degraded message.