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

Re: [scrumdevelopment] Requirements Issues

Expand Messages
  • Ron Jeffries
    ... Mistake. They should have been marked done. I m serious. Ron Jeffries www.XProgramming.com The central e in Jeffries is silent ... and invisible.
    Message 1 of 3 , Aug 8 9:58 AM
    • 0 Attachment
      On Friday, August 8, 2003, at 11:17:58 AM, stanky_buddha wrote:

      > The business driver does attend the pre-sprint planning meetings and
      > at the last one (for which I wasn't the scrummaster yet) watched on
      > as high priority items were taken off the product backlog, put into
      > the sprint backog and estimated on. When the developers tried to
      > start the task(s) they realized there were no requirements for them
      > to work with on about 30% of the items and when they went to the
      > business driver it was discovered that the product owner wanted the
      > item in name but no idea what they wanted from the item. Since the
      > items were mostly reports you kind of need something to go with so
      > the tasks with no requirements were taken of the sprint backlog and
      > placed back in the product backlog.

      Mistake. They should have been marked done. I'm serious.

      Ron Jeffries
      www.XProgramming.com
      The central "e" in "Jeffries" is silent ... and invisible.
    Your message has been successfully submitted and would be delivered to recipients shortly.