Re: Practice: Weekly Cycle

I'm one of those who's tended to making the PlanningGame on the 
Tuesday.
* Most bank holidays occur on Mondays
* Users often have busy mail boxes and can't make monday.
* Mondays tend to be high volume days in banking.
* You don't get peoples excuses until Monday morning.

In the spirit of XP this was killing us, so we tried Tuesday and it 
worked.

----

Two week cycles were requested twice in 2 years at WDS, the users 
were certain they wanted something we said would take two iterations 
(maybe they didn't want another planning meeting). Each time, one 
week in, a new planning game was called and half finished work was 
thrown away.

If we'd done it in one week iterations we'd atleast have something.

Now I'm at JP Morgan Chase and trying to sell agile again.
I'm insisting that we need to atleast aim for one week cycles.

People's objections
* "It's shorter than the budget approval process"
* "It's shorter than the change approval process"
* "It's shorter than people can technology can possibly imagine"

IMHO people often ask where the "Extreme" comes from. XP isn't a 
bandwagon it's a Ferrari. Unless you're atleast prepared to imagine 
the incredible effort it's going to take delivery functionality to 
users closer to when they ask for it, then XP isn't for you.

PS You'll still be a week later than users actually need this stuff.

OliBye





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