--- In extremeprogramming <at> yahoogroups.com, "aacockburn"
<acockburn <at> a...> wrote:
> --- In extremeprogramming <at> yahoogroups.com, Jeffrey Fredrick 
> <jeffrey.fredrick <at> g...> wrote:
> > 
> > I always thought the point was that at the end of each iteration you
> > could release, that you had the ability to do so, even if you didn't.
> 
> I would have to place in the vast MINORITY of projects I've ever seen 
> where they had that property in place. 

Really? That's a bit disturbing. 

We release to live every Wednesday, and we do so automatically unless
a customer at the preceeding Friday's demo vetos the release. Our
iterations are the period between a Monday (where the customers get
the opportunity to change priorities in the backlog, and the Friday
when new or changed functionality is ok'd to go live the following
Wednesday. This happens every week (barring acts of God).

As developers we'd be happy to release to live every day (there are
new tested features avilable literally every day), but the folks in
operations who'd get called out in the middle of the night if  we
inadvertently released a defect insist (quite properly) on a change
control process that takes two days (Monday and Tuesday) to execute.

So far as I can see, everybody wins with this process: devs get rapid
feedback, customers get to steer at a fine enough grain without a huge
overhead, ops get not to be tripped up. 

I can't imagine not working this way, how does your majority (of
self-described agile teams, right? Or not?) who don't do this, the
"iteration is planning window" folks, justify themsleves?

Your mention of "agile machismo" in the article is interesting though.
Every now and again some of our guys go to at Agile events and come
back pumped up after conversations whereby other folks try to impress
them with tails of rapid deployment only to have the wind taken out of
ther sails by the news that we deploy to live more frequently than
they do to UAT.

But note that bragging rights isn't the reason we do it (agreeable
though they may be): we've arrived at our process by trying a range of
variations over several years, and this is what (currently) works for us.

Keith

To Post a message, send it to:   extremeprogramming <at> eGroups.com

To Unsubscribe, send a blank message to: extremeprogramming-unsubscribe <at> eGroups.com

ad-free courtesy of objectmentor.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/extremeprogramming/

<*> To unsubscribe from this group, send an email to:
    extremeprogramming-unsubscribe <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/