By changer
via rgoarchitects.com
Published: Jan 11 2008 / 11:13
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
-
Passing data objects between CICS Java environments: Part 3: Transporting Java data objects from a CICS transaction Java client program to a CICS TS Java program
-
Stealing Your Address Book
-
Spring and Scala talk: slides, video and source code
-
Notify Property Weaver extension for Visual Studio 2010 and Visual Studio 11
-
HTML5 made easy with HTML5 Cheat Sheets for tags, event handler attributes, and browser support
-
On my Internship at Khan Academy
Add your comment
