Agile User Stories
Many organizations segregate their programmers and testers in order to achieve independent validation of requirements. If the system is tested according to an independent interpretation of the requirements than used for implementation, then errors in those interpretations may be detected.
This course of action is obviously prudent when the requirements are handed down to the development organization...
read more
I want to show a real easy way to put user stories in a spreadsheet-based product backlog. I wrote this after seeing someone tweet a screen capture of a product backlog I made 9 years...
read more
A recent comment on one of my blog posts asked about the difference between agile user stories, themes, epics, and features, and about the relationship, or hierarchy, between these...
read more
Agile software development teams often use User Stories as a simple and concise way to express user requirements.
Ideally these User Stories are broken down as small as possible,...
read more
Scott Sehlhorst from Tyner Blain is one of my favourite bloggers. He's written an excellent post about User Stories versus Use Cases.
When I first used Use Cases, I loved them...
I...
read more
I was very interested to read this blog post from Ron Jeffries about burning down user stories rather than tasks. Excuse the pun, but this is a hot topic for me at the moment :-)
If...
read more
Joe Ocampo ('AgileJoe') has recently written about a concept he calls 'Role Storming'...
I'm not sure I like the name - sounds a bit buzzwordy - but I think the concept is really...
read more
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...
read more
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...
read more
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...
read more
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...
read more
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...
read more
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...
read more
