2929RE: [scrumdevelopment] What to do with "loose ends"
- Mar 9, 2004Absolutely. Anything that is at all consequential we route back as story to
be estimated and scheduled in. If it's "hot" then we have to redo a bit of
the sprint planning we'd already "finished." Otherwise, it just comes in a
later sprint. We're doing 2-week sprints so a delay is rarely a problem.
Author of User Stories Applied for Agile Software Development
From: Ron Jeffries [mailto:ronjeffries@...]
Sent: Tuesday, March 09, 2004 12:33 PM
Subject: Re: [scrumdevelopment] What to do with "loose ends"
On Tuesday, March 9, 2004, at 10:34:27 AM, Mike Cohn wrote:
> I'm at a company where we have to do our sprint planning a few hours
> we do the sprint review of the prior sprint. A bit backwards but we make
> During the sprint review we always come up with a few tiny
> 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
> 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.
If I were to have an issue with this, it would be that it might encourage
the customer to be a bit too careless. As long as the stuff is a few hours'
worth, I'd not be troubled.
My advice is to do it by the book, get good at the practices, then do as
you will. Many people want to skip to step three. That's OK too.
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to:
Yahoo! Groups Links
- << Previous post in topic Next post in topic >>