Skip to main content

One sentence does not make a User Story

I'm working with a large client that has adopted the classic user story format for the backlog.

"As a user, I want some feature  so that I receive this benefit."


Yet, I'm sure that it is not delivering the desired shared understanding that throwing out the classic business requirements document and adopting the scrum/XP user story practice is designed to deliver.

So if your groups user stories have become just a piece of boiler plate language to satisfy some agile coach's requirement - maybe you should reflect upon the desired reason for user stories rather than requirements documentation so many years ago.  User stories do work.  But you have to tell a story.  Few authors are good enough to tell a story in one sentence.

Here Ron is pointing to one of the XP practices that were very successful in replacing the big upfront requirements documents with the concept of stories.  In XP this was the Card-Conversation-Confirmation technique.  In this technique the card and the label or title written upon the card is the place-holder used in planning.  In this way the card becomes a token for the planning game (XP practice similar to Scrum's Sprint planning).  The Conversation is the part of the practice that may be missing if your groups don't find the one sentence description (in classis form) to be sufficient to plan, estimate, design, develop, test, and deploy the user story.


Another group behavior that I've noticed is that the Confirmation aspect of these user stories may be a bullet point list of statements that are not recordings of a dialogue (as described in Ron's XP article).  To improve efficiency of requirements gathering some groups have people working independently and ahead of the development teams to write user stories and acceptance criteria.  This practice can sometimes improve communication and sometime harm the shared understanding that is required for highly productive development teams.  In the C-C-C technique of XP the team and the customer wrote the confirmation statements together, a technique for validating that a shared understand had been reached during the conversation.   This also served as reminders during their demo of the application behaviors that would be observable with working software.

Learn to Tell the Story

The common reframe today is the distinction between telling stories and writing stories. Which is your team doings?  We all are much better at telling stories than at writing stories - it's just how much individuals practice telling stories.  We start at the early age of 3 or 4 and continue to practice for our entire life.  Few of us actually practice writing stories.  Can you see the powerful distinction between these two practices?

When telling stories a great practice is to have one or more people capturing the important points and themes as the teller spins the tale of the feature and the value it will bring to your customers.

User Story Mapping
A higher level abstraction from telling stories occurs in the Story Mapping practice as described by Jeff Patton - Story Mapping is a better way to work with Agile User Stories.

"User Story Mapping is a dead simple idea. Talk about user’s journey through your product building a simple model that tells your user’s story as you do. But it turns out this simple idea makes working with user stories in agile development a lot easier."

The behavior of teams that are being helped by the practice of writing detailed user stories is quite different than the behavior of teams that are being harmed by the practice.  The great thing about Scrum is that this difference should become apparent in a short amount of time - say one or two sprints.  When the shared understanding is being communicated by the written story and the conversation and the team is delivering working tested software that meet the confirmation aspects (acceptance criteria) of the story then one can easily observe the behavior in the demonstration of the working application each sprint.  If that is not happening, then perhaps the story is not being communicated, there is more to a great story than just one little sentence.


You also may want to reconsider the format of the classic user story - because they lack the obvious title that all great stories must have.  Try this alternative format:
<What I Want>
so <Role> can <Business Value>
This format creates a nice handle or title in the "What I Want" phrase.

See Also:
Definition of Done vs. User Stories vs. Acceptance Criteria by Mark Levison of Agile Pain Relief a consultant with lot's of wise content and great practices to teach.
Names should not be needed for user stories - by Mike Cohn
Advantages of the As a User I want - user story template - by Mike Cohn
User Stories Applied - book at Amazon
10 Tips for Writing Good User Stories - Roman Pichler
Good Stories have Great Titles - Lance Kind
6 Brilliant ways to slice user stories by Dominic Krimmer

** Telling User Stories vs Writing User Stories **
A Story About User Stories - The real intention behind user stories - by Ebin Poovathany
Focus on telling user stories -  Charles Bradley
Story Mapping concepts (PDF) by Jeff Patton


Post a Comment

Most Popular on Agile Complexification Inverter

Innovation in the Automobile Industry

In the 1900s the automobile industry was the most important and innovation industry in the USA.  But one could question if this was good for our society in the long run.  And one could question if they actually innovated.

In the early 1900s there were few automobiles, very little infrastructure created to support the industry.  For example the road system was still designed for horse drawn wagons and the wagon wheel (remember a steal rim and wooden compression spoke wheel).  The future US Highways, or the 1950s Interstate Highway System at the cost of $425 billion were decades and many innovations away. There was no gas service station, there were however horse stables, farriers, and blacksmiths in each town along the roads.  There was no real "road map", there was no road naming system, like was created in 1926 - the United States Numbered Highway System.

The industry employees millions of people, and was a large factor in the economy of the USA.  It created or was created b…

Software Development terms applied to Home Construction

Let's Invert the typically wrong headed view of Software Development project management as a construction project.  We can map it the other way just to see if it works... to have some fun, to explore the meaning of phrases we toss around quite frequently.


Normally Project Management terms come from a construction domain.  We are going to apply the lexicon of modern software to the construction of a home.  We will follow the construction project and meet some of the people doing the work.

This is a very small (8 homes from $600,000 skyward) program in my 30-40 year old neighborhood.

About 6 months ago I saw the programs landing page go up.  It gives casual observers and some of the stakeholders a general idea of the intent of the program.  And most importantly who to contact for additional information if you happen to be interested in their products.

The Refuge program has 8 product projects and has them running independently.  Yet much of their DevOps infrastructure has already b…

Timeline of Social Networks -or- the Long Haul

I was listening to KERA's Think and they mentioned the concept of social networks.  It got me think...

But the book Long Haul, is its own interesting story - A Million Miles and Counting - A Trucker's Tale.

“The Long Haul: A Trucker’s Tales of Life on the Road”
Did you know 41 million people move in the US a year?  Having moved a few times in my life, sometime with the Bed-Bugger's help, this book is a great insight into that life.
Author: Finn Murphy's CB handle - "U-Turn" The radio interview noted the concept of social networks in the 21st century.  What is a highway - but a manifestation of a social network - a trail across the land.

a timeline using the Knight Lab Timeline JS tool kit.

See Also:

Social Media - Tracking its Exponential Growth video
Social media has overtaken porn as the #1 activity on the Web
List of social networking websites - Wikipedia

The World's 21 Most Important Social Media Sites and Apps in 2015



The Growth of Social Media - infog…

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

One Dark and Stormy during a Hurricane

I'm from the Carolina's where legend has it that our family commonly just hunkered down in the home on the coast and waterways than to head for inland shelter. Now that's from the old school days of barely improved (read paved) roads. They counted a storms severity by how high on the back porch steps (about 15 - top to ground) the water reached.  I don't recommend this action in todays world of long range forecast and transportation options.

I do recommend a drink or two in a hotel bar, far far away.

This is the week that Harvey came ashore in Texas.  I live on a hill in the little old town of Grapevine outside Dallas and Fort Worth.  And thank you all for letting me know that a storm is coming... I didn't get out and walk Malibu before the rain hit, so I grabbed a hat and we went anyway.  Much nicer walk with the drizzle, I'd say.

I'll raise a glass to you - if you were not smart enough to do the responsible thing, at the last responsible moment.

I do re…