Re: Re: Practice: Weekly Cycle

Andrew McDonagh wrote:

>
>
> > -----Original Message-----
> > From: Ben Hogan [mailto:bwhogan-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx]
> > Sent
> > >  When have a few large stories, the effect upon our over all 
> velocity is
> > >  greater when stories are not finished.
> >
> > Indeed, when your stories are small enough, the impact on your
> > velocity would be minimal as you suggested, meaning you would have
> > little incentive to rush at the end.
> >
>
> Yeah, its the incentive to rush at the end that then causes other 
> problems -
> code smells, untested code, acceptance tests not run...yada yada yada...
>

That's a practice I use with teams.  I call it "ease off"    If it's the 
last day of an iteration you should either be pleasantly pleased about 
what you've gotten done and perhaps slightly sad about what you 
couldn't, but you shouldn't be agitated and trying to get things done.  
If you are, you need to find a way back to the other state.  Learning 
how to "ease off" is very important.

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





------------------------ 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
--------------------------------------------------------------------~->