Re: Practice: Weekly Cycle

On Wed, 24 Nov 2004 23:22:56 -0500 (GMT-05:00),
mfeathers-mn4gwa5WIIQysxA8WJXlww@xxxxxxxxxxxxxxxx 
<mfeathers-mn4gwa5WIIQysxA8WJXlww@xxxxxxxxxxxxxxxx> wrote:
> -----Original Message-----
> From: William Wake <william.wake-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>
> When you have two-week iterations, I'm curious what that means:
> - do you have twice as many stories "in process"?
> - is your typical story unable to be completed in a single week?
> - or is a story the "usual" :) size, but you have "wait time" within it?
> - do you tie releases to the iteration length at all?
> - ... (the other 20 reasons I'm not clever enough to make up here)
> 
> I'm curious about the question behind all of this.  What problem are 
> we trying to solve?  

If the question is "solve by having shorter iterations in all cases",
I don't think I know. If the question is "solve by answering these
questions", it's really to help me understand better the pressures
teams feel & how they deal with it.

I'd say I've seen often enough that a shorter iteration can help
teams, by teaching them things like "parts of stories are often
valuable" or "actually delivering something today is worth a lot of
talk about how great it's gonna be" or "smaller stories have fewer
bugs" etc.

But I've often heard argument that the iteration (or the release
cycle) "oughta" be longer - (in one case, arguing against quarterly
releases in an IT shop).

-- 
   Bill Wake  William.Wake-HInyCGIudOg@xxxxxxxxxxxxxxxx  www.xp123.com


------------------------ Yahoo! Groups Sponsor --------------------~--> 
$9.95 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/J8kdrA/y20IAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~->