Link Details

A while ago I wrote about use cases and user stories and how I use both, starting with user stories for ease of estimation and manageability and expanding them into use cases as a way to elicit more requirements. I just read a recent blog (wiki) entry by Alistair Cockburn (of "writing effective use cases" fame) called "why I still use use cases". Alistair explains that he sees (with companies he consults to) three main problems with user stories: 1. lack of context (what's the largest goal) 2. sense of completeness - that you covered all bases relating to a goal. 3. no mechanism for looking ahead at upcoming work