back to top

our blog


agile user stories

How Detailed Should Tasks Be in a User Story?

by Kelly Waters, 06 August 2012

This is a guest blog post by Joe Woods from VersionOne… When I first started using agile project management, my stories didn’t have enough detail. In my office we use Agile to manage our marketing department with 2 week iterations. Even from the beginning, I could see the value of bite size goals that you […]

Tell me more >
Independent Interpretation

by George Dinwiddie, 19 September 2011

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 [...]

Tell me more >
Themes in Agile Software Development

by Kelly Waters, 03 March 2009

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, whilst also trying to minimise dependencies. Naturally, though, as you break User Stories down smaller, they become increasingly inter-dependent. Like most things in software development, it’s […]

Tell me more >
User Stories versus Use Cases

by Kelly Waters, 03 February 2009

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 loved the fact they gave such a clear description of a feature, and the fact that each Use Case could stand alone. They […]

Tell me more >
Role Storm

by Kelly Waters, 01 November 2008

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 great! When you first start a project, you need to build out the initial Product Backlog. Role Storming would be a great […]

Tell me more >