W trakcie analizy

give names to stories

Michael Terkowski 13 lat temu Ostatnio zmodyfikowane przez Rob Scott 10 lat temu 10
As a product owner, I would like to be able to give a name/title to a user story, so I could identify, relate and communicate them easily.

For example, the above story could be named "give names to stories" rather then GNA1.
Thanks for the suggestion.

We've toyed with this idea quite a bit, and we're really just not sure we should be introducing yet another field into the already crowded space.  What we have thought about however, which may solve your problem, is to allow a user to either enter a story using the as a, I want to, so I can strict format, or they could simply enter what they like in freeform manner.  That way, the story could be described using either the full story or the freeform text you use.  Would that work?  If so, we are considering introducing this in the coming weeks/months anyway, although a fixed date to deliver this has not been set as it's not been asked for very often.
I have a suggestion for a slight alternative. What if, instead of a name or title,we had a way to mark part of the story with some markup, and that becomes the title?

Pur team typically underlines the most important two or three words in a story on a physical card. For example:

As a user of X, I want a graphical test runner so that I can blah blah blah

("graphical test runner" is underlined when I type this, but it's not showing up when I click save...)

What if you allowed me to write a story like this:

As a user of X, I want a *graphical test runner* so that I can blah blah blah

... and then you bold everything between the *'s, and use that as the title. This cuts down on redundant data entry yet still makes it possible to have a short description for a longer story.
Hi Bryan

As mentioned in http://easybacklog.userecho.com/topic/100491-i-would-like-to-be-able-to-collapse-stories/, we are quite reluctant to bring a new micro format that people need to be trained on.  How would it work if someone did not use this micro format, what fall back would we have?  Also, what are titles needed for?  This is probably more important, trying to understand what the motivation is for the addition of titles.
Why not have the option to allow admins to add custom fields.  Keep the main fields, but allow the option for two custom fields.  We also use Title's to identify the process for that user story. 
For example;
Title: Fitness Test - Infrastructure
Title: Fitness Test - Calculation
Title: Fitness Test - Processing
Unfortunately custom fields are really quite difficult.  We would need to reconsider the entire interface to allow these custom fields, and at present I find it hard to find a space where they could go without reverting to an interface where some of the content is in fact hidden behind a dialog box.  We'll give this some thought, but unfortunately not many people have asked for custom fields so it's not high on the priority list.
Hi Matthew! Here is my answer to "what are titles needed for.

I love how easy you guys make it to enter user stories and I like having my backlog items as user stories. but the user stories are difficult to scan. Some of that is our fault as we're new to user stories but we spend a lot of time in our stand-ups  looking at the posted stories and asking "which one is that?" 

Having a title (which we're currently putting in the description field) would remove the mental conversion of "As a content manager I want to have social media links on the home page so I can promote our social media participation" to "Add social media links to footer".

Of course our particular use case could be solved by tasks too since we could save the plain language for the tasks and leave the stories more general.

Thanks for your input Sunshine.  We will certainly consider how to incorporate this moving forwards as we plan further development of easyBacklog.  I understand why this is needed for some people and why it would be useful.
I would like to echo the other comments for the need of this feature.  Having been an eXtreme Programming style agile practitioner for over a dozen years, I find the lack of a "User Story Headline" to be almost a showstopper for using your otherwise outstanding service.

All the other features that look like additional fields to user stories can be argued as more or less critical depending, on one's particular flavor of agile; however, the "headline" idea, in addition to the user story ID, is what enables most conversations around a user story to have a context.  It's the name we use to "hang the conversation" on -- I hope that makes some sense.

I love how ID's can be converted by changing the prefix for the theme.  I love how the tabbed completion mechanism streamlines the ability to write a story fast.  Basically, I love it all.  I the only hitch is the lack of headlines.

One more side comment.  With the addition of a headline field, quite a few of the other suggested features could have work arounds by simply following an convention in the headline usage.  For example, suppose one has a client that needs an "epic" identifier for some cross section of stories, a story headline might be "[EPIC: Security] New security role for team-leads" and so on.

Thanks for create a great product.
To me, having a separate name for a user story is a "smell." It may mean that the user story is too complex and needs to be broken up.

On the other hand, there is clearly a need for being able to easily scan the titles of stories. One idea I had was to reformat the user story structure into just ROLE + "wants to " + WANTTO onto a single line.