User Stories Should Be *Valuable*

Agile User Stories Should Be ValuableI recently quoted the ‘Invest’ acronym as a way to remember and assess what makes a good User Story.

The *V* in ‘Invest’ stands for *Valuable*.

It is often said by people in the agile community that User Stories should be of value to the user.

Whilst that is mostly true, some User Stories are not of value to the user, but rather of value to the customer or owner of the system.

Therefore it is more accurate to say that, “User Stories should be of value to the user, or owner, of the solution”.

A good example of this is advertising space on a public web site. Ads can be of value to the user, if they are highly relevant and positioned in a place sensitive to the user experience. For example on Google. On the other hand, very often the ads on a web site are of little value to the user and interfere with content, creating a poor user experience. Of course I would never advocate creating a poor user experience, but regardless of the debate about value to the user, they are certainly of value to the owner of the solution.

User Stories should be focused on features – not tasks. And written in business language. Doing so will enable business people to understand and prioritise the User Stories.

For example, a User Story to ‘comply with OWASP security standards’ should be written something like this: ‘As a user, I want my data to be secure, so I can use the system without my personal information being misused’.

This brings me to the question of non-functional User Stories that in effect span all other User Stories. For example the above story about security, or maybe a user story about the solution’s performance. These can be captured as User Stories to ensure the requirement is not lost. But actually these requirements are possibly better served by writing a series of standard test cases to be applied to all User Stories.

So let’s take a look at my recent Example of a User Story in terms of being Valuable to the user or owner of the solution? An agile consultant saw this example and said it was not a good example because logging in to the solution is of no value to the user.

But in this case I disagree.

It is of value to the user, because only by logging in can they gain access to features and content that are available to subscribers only. And it’s also of value to the owner, as it prevents people from accessing premium areas of the solution unless they have paid to subscribe.


Share on facebook
Share on twitter
Share on linkedin

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Posts

Six Actionable Nuggets of Advice for Becoming a First-time Technology NED

If the pandemic has taught companies anything it’s that tech is not something that you put off and think about ‘later’. The last year has seen organisations go through huge digital transformations, whether planned or otherwise. And for those that aren’t technology-based companies, getting the right board-level advice can not only be hard to find, but the difference between success

Read More »

Culture, Skills, and Capabilities // How to become a more data-driven organisation

In our whitepaper “How to become a more data-driven organisation”, we wrote about the five steps that an organisation would need to take, which are: Outcomes: Defining goals and metrics to ensure clear and measurable outcomes Analytics: Implementing and sharing the analytics to improve data-driven decision making Innovation: Testing assumptions through hypothesis testing and learning Data Platform: Gaining new insights

Read More »

Data Platform // How to become a more data-driven organisation

This is the fourth article in our series on “How to become a more data-driven organisation”, and we are going to be focusing on Data Platforms. It is at this point that most people start to dive deep into the technical aspects of Data Lakes vs Data Warehouses, but we want to bring us back up a level and ask

Read More »

Search the Blog

Agile Management Made Easy!

All About Agile

By Kelly Waters

“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. is one of the most popular blogs about agile on the web. ”

Kelly Waters

Agile 101 is available to purchase. GAME ON!

Agile 101

Emma Hopkinson-Spark

“Whilst there are lots of ways you can vary the game depending on the teams you have and the learning outcomes you want, the basic flow of the game play is common to all.”
Emma Hopkinson-Spark

Why did we make the game?

How to play the game?


101 Ways Limited
145 City Rd
United Kingdom


101 Ways BV
Weesperstraat 61-105
1018 VN Amsterdam

Contact Us

If you would like to get in touch with one of the team at 101 Ways, then please fill out the form below or email us at