User Stories Should Be *Small*

This content is syndicated from by Kelly Waters. To view the original post in full, click here.

Agile User Stories should be SmallUser Stories should be small.

This is what the *S* stands for in the the 'Invest' acronym; a way to remember and assess what makes a good User Story.

Not too small. But certainly not too big. So what is the right size for a good User Story?

First of all, let's get one thing straight. This statement is slightly misleading. More accurately, it should read: "User Stories Should Be Small, by the time you plan to include them in a Sprint".

Because until you come to Sprint Planning - until you're ready to include the feature in the next iteration - User Stories can be big. In fact, they can be huge. Humongous even! It's completely reasonable for User Stories that are further down the Product Backlog to be rather large and fuzzy.

As long as they are broken down before it's time to work on them, that's fine. They are still effective placeholders. So it's okay to have a User Story further down the backlog like: "As a user, I want a new system, because the old one no longer meets my needs".

These big User Stories are known as Epics.

Anyway, back to the point in hand. What's a good size for User Stories when they are ready to be developed?

Let's take my recent Example of a User Story. This could have been: "As a user, I want to register, log in and manage my details online". But I think that's too big to be a good User Story. Perhaps it started life like that, as an epic, further down the backlog. That would be fine. But at the time of Sprint Planning, a story like this should be broken down.

So let's say it's broken down into 3 stories: register, login, and manage details. The login story could potentially be broken down further, into another 3 stories, for example: login, forgotten password, remember me. In my opinion that's a nice size. The stories are very focused. Small. But still each story is still functional and fulfils its own purpose. And they're still fairly Independent.

Now let's say the login story is broken down even further. For example: "As a user, I want to enter my user id", "As a user, I want to enter my password", "As a user I want to push the login button", "As a user, I want a clear error message when my login fails", etc. Then I'd say it's gone too far. These stories are too detailed. At this level, even a small project would end up with hundreds of stories, and be very hard to manage.

In the end, there's really no right or wrong here - you need to do what feels right for you and your team. Nevertheless, I hope my comments offer some useful guidance, even if it's just as a starting point for your team to debate...


Leave a Reply

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

eleven − 3 =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”



To explore how we can help you, please get in touch