Re: Practice: Weekly Cycle

-----Original Message-----
From: William Wake <william.wake-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx>

All -
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?  I know Scrum teams that have four week sprints and they work fine 
for them.  Teams I work with tend to have 2 week iterations.   There are two 
reasons why I occasionally  try 1 week iterations: 1) to develop more practice 
discipline, and help people learn how to work in smaller increments,  2) to 
give the customer more control.  But, generally these are not long term 
concerns.

I do see the benefit of shorter iterations, but to me it should be tied to a 
concrete problem.  Otherwise, aren't we optimizing something that may not need 
to be optimized?


Michael Feathers
http://butunclebob.com/ArticleS.MichaelFeathers.TheNewGuy








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