Sunday, 9 December 2012

Classes or Categories of User Stories

Please see below. I couldn't easily find a site that has all of these definitions together in one spot. 


Epics are large user stories, typically ones which are too big to implement in a single iteration and therefore need to be chunked into smaller user stories at some point before the effort required to complete them can be reasonably estimated. 


A theme is a collection of related user stories.  For example, for a university registration system there might be themes around students, course management, transcript generation, grade administration, financial processing. 

Themes are often used to organize stories into releases or to organize them so that various subteams can work on them.   


The purpose of a spike is “to figure out answers to tough technical or design problems”. Spikes are considered useful when a more accurate time (and cost) estimate is required for an upcoming piece of work. 

Foundation development, investigation work and the set-up of a lab environment so it's ready for use when a software build becomes available for testing are all good examples of spikes. 

User Stories 

A user story is a high-level definition of a requirement, containing just enough information so that the developers and testers can produce a reasonable estimate of the effort, potential risks, key complexities, etc that need to be considered and are required to implement it. 


Tasks are single units of work such as checking out a code branch or installing a build in a test lab. 

Would you like this elaborated upon further? Just let me know. 

No comments:

Post a Comment