InfoQ

News

New User Story Format Emphasizes Business Value

Posted by Chris Sims on Jun 19, 2008 05:29 PM

Community
Agile
Topics
Customers & Requirements
Tags
User Stories
Since the early days of agile, user stories have been a common way of capturing requirements. These short bits of documentation, often only a sentence or so written on an index card, capture the essence of the desired functionality. A conventional format for these stories has been:

As a <type of user> I want <some functionality> so that <some benefit>.

Elizabeth Keogh suggests that business value is more important than user role and presents a revised template for writing user stories, which she credits to Chris Matts. The traditional format emphasizes the importance of the user, mentioning them first. The newly proposed variation switches the emphasis to the business value:

In order to <achieve some value>, as a <type of user>, I want <some functionality>.

The change may be subtle, but it is likely to resonate in a value-focused environment.  Elizabeth goes on to describe how the focus on value carries over to planning a software release:
The word 'release' is more meaningful. There's some untapped money out there - some market share, some cost saving, some battle against a competitor. All the features we produce go towards releasing that value for our customers to use - and it's the value we're releasing, not the features.

Would refocusing users stories on business value make a difference in your environment? Leave a comment and share with the community.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.

2 comments

Reply

I like it. by Karl Scotland Posted Jun 20, 2008 5:05 AM
Some views on the format by Ajay Danait Posted Jun 23, 2008 4:24 AM
  1. Back to top

    I like it.

    Jun 20, 2008 5:05 AM by Karl Scotland

    I blogged about it here.
    I think the new format gives a clearer way of managing the relationship between the small incremental functionality pieces, and the larger value pieces.

  2. Back to top

    Some views on the format

    Jun 23, 2008 4:24 AM by Ajay Danait

    These are some views from my manager on this format :

    In order to [achieve some value] As a [role] I want [some feature].

    i feel
    #1 - it is heavy, and not so natural (more written language than oral one)
    #2 - takes only the 'value' perspective, and hides the 'risk mitigation' side

    -> in the product backlog, we found great to consider priorities on 2 axis : value creation vs risk mitigation

    => good thing when you talk to a end-users in our business, especially it will emphasize the 'OR' sensitivity

    As a I want so that . should be turned into :-

    #A - As a [type of user] I want [some functionality] to avoid [some operational risk, process weakness, ...]

    #B - As a [type of user] I need [some functionality] to get/maximize/fasten/point.... [some benefit].

Exclusive Content

Typemock: Past, Present and Future

Eli Lopian of Typemock answers a few questions on Typemock origins and where Typemock is headed.

Agile in Practice: What Is Actually Going On Out There?

Scott Ambler talks about actual data resulting from surveys made during 2006-2008, showing how Agile is perceived and implemented within organizations.

Building Smart Windows Applications

From QCon 2008, Daniel Moth presents on using Visual Studio 2008 and .NET 3.5 to create compelling rich Windows applications.

Joshua Kerievsky about Industrial XP

Joshua Kerievsky, founder of Industrial Logic, talks about Industrial Extreme Programming which extends XP by including practices dealing with management, customers and developers.

Jeff Barr Discusses Amazon Web Services

Amazon Web Services (AWS) Evangelist Jeff Barr discusses SimpleDB, S3, EC2, SQS, cloud computing, how different Amazon services interact, origins of AWS, AWS globalization and the March AWS outage.

More Than Just Spin (Up) : Virtualization for the Enterprise and SaaS

Cloud services have helped bring virtualization to the forefront. Its full power however, also includes other benefits such as high availability, disaster recovery, and rapid provisioning.

Ruby Beyond Rails

John Lam talks about his path to dynamic languages, some of the problems of making IronRuby run fast, and how the DLR helps with implementing languages.

VMware Infrastructure 3 Book Excerpt and Author Interview

VMware Infrastructure 3: Advanced Technical Design Guide and Advanced Operations Guide provides a wealth of practical insights into setting up virtualization in todays corporate environments.