Re: Practice: Weekly Cycle

Andrew wrote:

 > Thanks Paul,
 >
 > Thats a great idea and as we are having a Retro today, I
 > think I try it...

Please let us know what happens.

 > > If the team doesn't know how to answer "comfortably complete,"
 > > or can't agree on the criteria, that's another issue to visit.
 > >
 >
 > Agreeing upon the criteria will no doubt be a problem, as
 > there are differing opinions as what 'complete' means.  The
 > amount of refactoring and the amount of code TDDd, how to
 > test, etc, varies amongst the team members - which is
 > currently cause some 'friction'.

I think a common agreement across the team (everyone, not just
the developers) of what "complete" means is so important that I
now include a "What is complete?" exercise as part of my agile
transition approach.  It's often useful to do a little overall
value stream mapping along with it to provide a context to make
sure all the important aspects of "done" are considered.

A team can reach an agreement on "complete" over time via their
iteration retrospectives, but I find that a little up-front
discussion, and a little ceremony around the agreement, can get
everyone on the same page more quickly, they know what to expect
from each other, and then they can refine things over time.

Paul
-----
Paul Hodgetts -- CEO, Principal Consultant
Agile Logic  -- www.agilelogic.com
Consulting, Coaching, Training -- On-Site & Out-Sourced Development
Agile Processes/Lean/XP/Scrum -- Java/J2EE, C++, OOA/D, UI/IA, XML



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