back to top

our blog


agile user stories

Putting the *Analyst* into Test Analyst

by Kelly Waters, 20 June 2008

For years, I’ve given Software Testers in my teams the official job title of Test Analyst, or something along those lines. Yet (informally) I’ve always referred to them as Testers. Only in more recent years – and especially since adopting Agile Software Development and User Stories – have I really discovered how to put the […]

Tell me more >
Writing Good User Stories

by Kelly Waters, 10 April 2008

Over the last few weeks, I’ve written alot about writing good User Stories – you can see them all here: User Stories. User Stories are a simple way of capturing user requirements throughout a project – an alternative to writing lengthy requirements specifications all up-front. As a guide for people writing User Stories, they can […]

Tell me more >
User Stories Should Be *Testable*

by Kelly Waters, 06 April 2008

The *T* in the the ‘Invest’ acronym (a way to remember and assess what makes a good User Story) stands for Testable. The most common forms of User Story that are not testable are big User Stories, known as Epics, or non-functional User Stories… An Epic can be a User Story that really comprises multiple […]

Tell me more >
User Stories Should Be *Small*

by Kelly Waters, 01 April 2008

User 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 […]

Tell me more >
User Stories Should Be *Estimatable*

by Kelly Waters, 28 March 2008

User Stories should be possible to Estimate. If you follow the other aspects of the ‘Invest’ acronym, chances are they will be. The *E* in ‘Invest’ stands for Estimatable; another useful way to measure whether a User Story is good or not. So what are the potential barriers to a User Story being Estimatable? Too […]

Tell me more >
User Stories Should Be *Valuable*

by Kelly Waters, 25 March 2008

I 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 […]

Tell me more >
User Stories Should Be *Negotiable*

by Kelly Waters, 19 March 2008

User Stories are not a contract. They are not meant to be precise, detailed specifications of a feature. They should not be fixed in stone. I recently quoted the ‘Invest’ acronym as a way to remember and assess what makes a good User Story. The *N* in ‘Invest’ stands for Negotiable. A User Story is […]

Tell me more >
User Stories Should Be *Independent*

by Kelly Waters, 13 March 2008

In my last entry, I quoted the ‘Invest’ acronym as a possible way to remember and assess whether or not User Stories are good. The *I* in ‘Invest’ stands for Independent. Ideally a User Story would be as small as possible, without making it dependent on other Stories. I recently posted an Example of a […]

Tell me more >