Re: Practice: Weekly Cycle

we know we're half done if about half of our current iteration's
stories are implemented and passing their acceptance tests.


On Wed, 15 Dec 2004 09:04:16 -0800, Kent Beck 
<kentb-ihVZJaRskl1bRRN4PJnoQQ@xxxxxxxxxxxxxxxx> wrote:
> 
> The problems to be solved are:
>   * Having a sense of progress
>   * Having an accurate measure of progress
>   * Delivering efficiently
>   * Tracking changing needs
>   * Building a trust-based relationship inside and outside the team
>   * Enabling the team to offer accountability
> 
> One of my principles is working with human nature, including natural time
> cycles. One week and one month are common cycles. That's why I'm suspicious
> of two-week iterations--fortnights aren't nearly as widely used as either
> weeks or months.
> 
> I have a question for those using two week iterations. After the first week,
> how do you know if you are half done? Is this even an interesting question?
> 
> Kent Beck
> Three Rivers Institute
> 
> -----Original Message-----
> From: mfeathers-mn4gwa5WIIQysxA8WJXlww@xxxxxxxxxxxxxxxx 
> [mailto:mfeathers-mn4gwa5WIIQysxA8WJXlww@xxxxxxxxxxxxxxxx]
> Sent: Wednesday, November 24, 2004 8:23 PM
> To: xpbookdiscussiongroup-hHKSG33TihhbjbujkaE4pw@xxxxxxxxxxxxxxxx;
> xpbookdiscussiongroup-hHKSG33TihhbjbujkaE4pw@xxxxxxxxxxxxxxxx
> Subject: Re: [xpe2e] 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 Links
> 
> 
> 
> Yahoo! Groups Links
> 
> 
> 
> 
> 


-- 
----
C. Keith Ray
<http://homepage.mac.com/keithray/blog/index.html>
<http://homepage.mac.com/keithray/xpminifaq.html>
<http://homepage.mac.com/keithray/resume2.html>


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