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

7649Re: [scrumdevelopment] Re: Requirements for Mission Critical systems

Expand Messages
  • Mike Cohn
    Jun 1, 2005
    • 0 Attachment
      I see no reason at all not to write stories where another system is the
      user. I've done that many times.


      Mike Cohn
      Author of User Stories Applied for Agile Software Development
      www.mountaingoatsoftware.com


      On 6/1/05 7:55 AM, "David A Barrett" <dave.barrett@...> wrote:

      >
      >
      >
      >
      > I wanted to go back to the original question; because I thought it was
      > interesting in itself and I'm not sure that the point of it wasn't missed.
      >
      > To me, the key factor was that the system was very low in user interface.
      > This makes it difficult to write User Stories because so much of the
      > specific things that need to happen are out of control of the user, or are
      > hidden from them.
      >
      > So I was wondering, do the "users" in User Stories need to be people?
      > Could you write a User Story that treats external systems and internal
      > modules as "users"? Something like, "In order to notify the dispach
      > processor of a completed request, the xyz system can send a request for a
      > routing priority when the abc module is fully commited"?
      >
      > Am I crazy?
      >
      >
      > Dave Barrett,
      > Lawyers' Professional Indemnity Company
      >
      >
      >
      > To Post a message, send it to: scrumdevelopment@...
      > To Unsubscribe, send a blank message to:
      > scrumdevelopment-unsubscribe@...
      > Yahoo! Groups Links
      >
      >
      >
      >
      >
    • Show all 26 messages in this topic