RE: [scrumdevelopment] Scrum pages
- I save the stories. I don't really understand why XP advocates ripping
them up. I've been playing with writing test cases directly from the
stories and then using those test cases as "requirements" for the
system. I have been involved in too many systems that succeed and are
successful for 5+ years and then need to be rewritten (usually for a
technology reason and you can't refactor something that big very
easily). I think the stories and their associated test cases (each test
case described initially as one sentence) do a good job of capturing
interesting and potentially useful information. Most projects won't ever
need them again but the cost of retention is minimal.
Yes, the numbers on the sprint backlog always reflect the most recent
thinking about the tasks. I used to collect those numbers in our daily
scrums and I didn't like how that was going--it made the meetings seem
too much about updating me with status information rather than about
making commitments in front of and to your teammates. Jeff Sutherland
set me straight on that with an email about how he used Gnats to track
tasks and developers just updated things there. Now our Daily Scrums are
back to being the 3 standard questions and we never talk about hours at
all. There are still sentences in these meetings like "I'll be done with
the analysis module today and should be able to start on its UI" (which
implies something about hours) and I'll still ask people about their gut
feel for whether they think they'll finish everything in the sprint (it
helps regain commitment and if we're going to miss I owe it to the
Product Owner to tell her asap).
From: Jonas Bengtsson [mailto:jonas.b@...]
Sent: Monday, October 14, 2002 6:25 PM
Subject: RE: [scrumdevelopment] Scrum pages
> 1) Ideally and most recently I've been using XP stories as Productexpansion
> Backlog items. I "move" them to the Sprint Backlog in the sense that I
> delete them from the Product Backlog and add them as one or more tasks
> in the Sprint Backlog. I consider this a "move" rather than an
> because I literally move the task (story) and then the team expands itgets
> into tasks but that usually starts happening a day or two into the
> sprint--not at the first moment. But, yes, the Product Backlog item
> expanded into 1 or more Sprint Backlog items.Ok. Now I got another question: do you save the userstories when you
moved them to the Sprin Backlog, or do you just use the tasks?
> 2) I'm not sure what you mean by "Where is the progress recorded inthe
> Sprint Backlog?" I used to use Excel but have been experimenting witha
> defect tracking system. Results are mixed so far. Each person on thebecause
> team updates any items in the sprint backlog they think have changed
> (either gotten smaller because they worked on it, gotten smaller
> of new knowledge, or perhaps gotten bigger because of new knowledge).I
> have simple reports that sum things up for me in various ways. Somelike
> teams like seeing burndown charts, others don't care--they're in the
> middle of it and know if they're on track. Project sponsors always
> the burndown charts. Let me know if I didn't answer your question.Hmmm... let me refrase:
In the example Sprint Backlog there are estimations of how 'big' the
are. Are those numbers estimations of the /remaining/ time or are they
estimations of how 'big' the tasks are /in total/ (i.e. disregarding
progress). The numbers of some of the tasks are decreasing as time
Is that due to work being done or reestimation/renegotiation?
I guess they show the remaining time, but that wasn't clear to me when I
first read it (the fact that I'm rather tired might have some impact :-)
> 3) When I added the PowerPoint presentation I realized I hadn'tNice!
> mentioned the sprint goal in the web pages and I need to add it. It's
> definitely important--in fact it's vital but it's one of those things
> that is easy to forget to write about. Thanks for pointing it out and
> I'll add it.
> Thanks again, Jonas, for taking the time to look at it and thensending
> me corrections and your thoughts.My pleasure!
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to:
Your use of Yahoo! Groups is subject to