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

2920RE: [scrumdevelopment] What to do with "loose ends"

Expand Messages
  • Mike Cohn
    Mar 9, 2004
      I'm at a company where we have to do our sprint planning a few hours before
      we do the sprint review of the prior sprint. A bit backwards but we make it

      During the sprint review we always come up with a few tiny things--rephrase
      this, can you make that more prominent, etc.

      After the sprint review is over the team looks at that list and almost
      always pulls those items into the sprint they've just planned. Our feeling
      is that we can't estimate accurately enough that at the start of a sprint we
      can say "nope, that 3 hours of small trivial stuff will push us over the
      feasibility edge." So, we bring it in and it almost always gets done.

      --Mike Cohn
      Author of User Stories Applied for Agile Software Development

      -----Original Message-----
      From: dennis [mailto:dennistodd@...]
      Sent: Tuesday, March 09, 2004 5:30 AM
      To: scrumdevelopment@yahoogroups.com
      Subject: [scrumdevelopment] What to do with "loose ends"

      We have been running SCRUM for about 5 months know. We have been successful
      at delivering functionality in each of the Sprints we have put together. The
      business is very pleased at the results as well.

      There is one nagging issue that has seemed to slowly expand over time. At
      the end of a Sprint as we are testing and demo'ing to the business, we
      identify several small items that need to be "fixed": move this button here,
      change the color of this field, etc. All of these things end up on a "loose
      ends" list. They accumulate in a spreadsheet where we try to track them.

      The issue is that because they aren't attached to a requirement anymore,
      they don't seem to get the priority they should in a sprint. Yet they are
      things that need to be resolved.

      My question for the group is, does anyone else have a similar list at the
      end of a Sprint? If so how do you handle them? What process do you use to
      track them? Where do they fit in the priority of everything else? Should
      they be a separate Sprint or be at the top of the list at the beginning of
      the Sprint?

      Part of these I think I know the answer to, but I'm looking for experiences
      of others in this group and how they have handled it in the past.

      Thanks to all!


      Dennis Todd
    • Show all 26 messages in this topic