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

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

Expand Messages
  • Steven Gordon
    Mar 9, 2004
    • 0 Attachment
      Yes, but is it not true that these low priority "loose ends" tend to stay in the "Product Backlog" forever? That was what I understood to be the original question.

      -----Original Message-----
      From: dhostick [mailto:dave@...]
      Sent: Tue 3/9/2004 7:58 AM
      To: scrumdevelopment@yahoogroups.com
      Subject: [scrumdevelopment] Re: What to do with "loose ends"

      We are currently using SCRUM and XP. Development is managed using a
      tool called XPlanner, where Sprints are referred to as Iterations.

      We create an Iteration called "Product Backlog", with other iterations
      named after their "Sprint Goal".

      During a Sprint, if anyone should want to raise a change (idea, bug --
      anything), a task is either added to an existing (and appropriate)
      User Story (Sprint Item) within the current sprint (with a low
      priority), or is added to the Product Backlog (to an existing or new
      User Story).

      At the end of the Sprint, the "loose ends" are moved to the Product
      Backlog and are prioritised accordingly for inclusion (or not) in the
      next Sprint. In XPlanner, you can continue or move Tasks and User
      Stories to other iterations (Sprints).

      This is also a really neat way of managing changes (requested by
      anyone) to the product - never say "No" if you can say "Low" (priority).

      Dave Hostick
    • Show all 26 messages in this topic