logo       

Re: Practice: Slack: msg#00070

programming.extreme-programming.xp-explained2

Subject: Re: Practice: Slack


On Tue, 28 Dec 2004 20:44:03 -0500, Ron Jeffries
<ronjeffries-hPI1FfVg2TpDlFalPvvQyA@xxxxxxxxxxxxxxxx> wrote:
> This is somewhat stronger, it seems to me, than some people's
> interpretation of the XP Planning Game. I've seen teams deliver
> absolutely nothing in an iteration, and then want to have that be
> OK: "Well, I guess our velocity was zero." I think this relates back
> to Kent's comments on accountability: it's really not OK to commit
> to something and deliver nothing.

No, it's really not OK - but what if it happens? Presumably with a
too-short iteration, it is possible that all of the tasks really did
need more time than was available. So, scolding and recriminations
aside, what DO you do in that case? Surely you cannot use "yesterday's
weather" to predict that you will not accomplish anything in the next
iteration, can you?


------------------------ 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>
Google Custom Search

News | FAQ | advertise