Kommentare zu: Methodik: Use Cases, User Stories und Akzeptanztests http://blog.coldewey.com/agile/2008/01/15/methodik-use-cases-user-stories-und-akzeptanztests/ Agile Software Entwicklung, Berichte, Anmerkungen und Politisches Fri, 10 Sep 2010 00:27:25 +0000 http://wordpress.org/?v=2.2.1 Von: Alistair Cockburn http://blog.coldewey.com/agile/2008/01/15/methodik-use-cases-user-stories-und-akzeptanztests/#comment-24 Alistair Cockburn Wed, 16 Jan 2008 02:06:55 +0000 http://blog.coldewey.com/agile/2008/01/15/methodik-use-cases-user-stories-und-akzeptanztests/#comment-24 Nice summary, Jens - I like your description of user story as the "title/heading" of a scenario. I have always said, "A reminder for a conversation", except that begs the question "about what?" ... which is answered by, "about the scenario for which this is the title!" The two points to draw from your well-phrased sentence are: - the user story covers ONE scenario; the use case covers MULTIPLE scenarios - the user story describes the title only, rarely not the scenario itself; the use case describes each scenario (abstractly). More importantly, the reason I keep introducing use cases to people is that I keep running across project suffering from three things: 1. No notion of "what is the size of this thing we're building" (missing any concept of "completeness") 2. No context for each story 3. No look-ahead as to what needs early research to get answers in good time. Use cases answer these 3 problems in a way that nothing around user stories or features or product backlog items do. So I find myself re-introducing use cases to agile teams to save them from these problems. This is written up in more detail at http://alistair.cockburn.us/index.php/Why_I_still_use_use_cases Nice posting, thanks, Alistair Nice summary, Jens - I like your description of user story as the “title/heading” of a scenario. I have always said, “A reminder for a conversation”, except that begs the question “about what?” … which is answered by, “about the scenario for which this is the title!”

The two points to draw from your well-phrased sentence are:

- the user story covers ONE scenario; the use case covers MULTIPLE scenarios

- the user story describes the title only, rarely not the scenario itself; the use case describes each scenario (abstractly).

More importantly, the reason I keep introducing use cases to people is that I keep running across project suffering from three things:

1. No notion of “what is the size of this thing we’re building” (missing any concept of “completeness”)

2. No context for each story

3. No look-ahead as to what needs early research to get answers in good time.

Use cases answer these 3 problems in a way that nothing around user stories or features or product backlog items do. So I find myself re-introducing use cases to agile teams to save them from these problems. This is written up in more detail at http://alistair.cockburn.us/index.php/Why_I_still_use_use_cases

Nice posting, thanks,
Alistair

]]>