|
Re: Practice: Weekly Cycle: msg#00035programming.extreme-programming.xp-explained2
Kent Beck wrote: > 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 - One of the teams at Chase (that you kicked off nearly two years ago) tried iteration lengths of 1, 2, and 3 weeks. They settled on 2-week iterations because (for them) it provided the right mix of time spent planning (iteration kick-off & closure) and time spent developing. As for your "half done" question, the team tracked their daily effort (both spent and remaining, by story) compared to time planned (by team member) for the iteration. This allowed the team (and business) to know the following day if a story was taking longer (or shorter) than planned, and we could adjust as needed. And the effort to do the daily tracking was minutes per team member each day. Bob Jarvis ------------------------ Yahoo! Groups Sponsor --------------------~--> Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar. Now with Pop-Up Blocker. Get it for free! http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/nhFolB/TM --------------------------------------------------------------------~-> |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Practice: Weekly Cycle: 00035, Erik Lundh |
|---|---|
| Next by Date: | Defect Cost Increase: 00035, June Kim |
| Previous by Thread: | RE: Practice: Weekly Cyclei: 00035, Kent Beck |
| Next by Thread: | Re: Practice: Weekly Cycle: 00035, Keith Ray |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |