Loading ...
Sorry, an error occurred while loading the content.

34851Re: User Stories vs. Agile Use Cases

Expand Messages
  • peterstev
    Dec 1, 2008
    • 0 Attachment
      Lady & Gentlemen,

      Yes, I have learned a lot from this discussion as well, including the
      value of well equipped tool box ;-)

      Kind regards,

      Peter

      --- In scrumdevelopment@yahoogroups.com, "aacockburn" <acockburn@...>
      wrote:
      >
      > Good points, Tom.
      >
      > This sort of discussion gets me to note that the workers working on
      > my house have a belt sander and also a chisel. I've seen them use
      > both. I've not yet seen them argue over, "Should we get rid of the
      > belt sander and only keep the chisel, or vice versa?"
      >
      > I also can't see the workmen saying, "I'm not going to learn how to
      > use a belt sander - this chisel works fine for me."
      >
      > The way of phrasing the question about use cases versus user stories
      > already presupposes that an either/or choice is appropriate.
      >
      > They are both tools. Learn them both. We are all professionals -- it
      > behooves us to know the tools available to us.
      >
      > Alistair
      >
      >
      > --- In scrumdevelopment@yahoogroups.com, "Tom Mellor"
      > <tom.mellor.c5t2@> wrote:
      > >
      > > Alistair makes good points. We find use cases more valuable when
      > we are
      > > producing a new system and we want to see the flow, the pre-
      > conditions,
      > > post-conditions, assumptions, etc. Obviously we don't try to drive
      > out
      > > the requirement details for the system in use cases, but rather we
      > use
      > > them to tie the components of the system together for a big picture
      > > view. In existing systems that we are upgrading, rewriting, etc.,
      > we
      > > typically only compose user stories, even if use cases for the
      > system
      > > have not been created. One thing about use cases that is
      > potentially
      > > unfavorable is that they decay over time unless they are properly
      > > updated for changes. Therein lies the problem - who takes the
      > > responsibility and realizes they need to be updated. User stories
      > don't
      > > typically decay as readily.
      > >
      > > Tom Mellor
      > > Certified Scrum Trainer
      > > tom.mellor.c5t2@
      > > 309.846.4899 (Work and Cell)
      > >
      >
    • Show all 15 messages in this topic