I heard of a project with a similar restriction on deployment to
production. They ended up setting up a mirror of production. The
mirror was in effect live, so it was using the same database as
production, etc. It was a scaled down version, so not capable of the
same load as real production though.
At the end of each iteration they deployed the new version to it and
asked the customer to take a look at it for them.
The customer ended up using it in preference to the build in
production as it had the new features and was just as stable.
The key is confidence. If you can get the customer to be confident
that the builds you produce are stable, then the fear that is stopping
them deploying to production is removed.
>From what I heard the customer then ended up being the advocate to the
rest of the company for releasing more often. I think it had
something to do with the customer seeing how much money the company
were loosing each day by not having these features in the users hands.
cheers
Nigel
On Sun, 24 Oct 2004 17:42:03 -0400, Victor <[EMAIL PROTECTED]> wrote:
>
> Hi Tony,
>
> I am glad you found a job. I would say that the important part for your
> issue is not necessarily the release time, but whether you have a customer
> (proxy) available to determine the validity of what you are doing. I know,
> for some government jobs even that is not available, but sometimes it's more
> available than it seems, so it's worth to keep trying. Worst case, you can
> always use this as a learning experience.
>
> Victor
>
> ===================================
>
>
>
> ----- Original Message -----
> From: "Tony Nassar" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Sunday, October 24, 2004 3:11 PM
> Subject: RE: [XP] XP and high-risk projects [was: BRUF]
>
> >
> > I realize this thread had died, but...
> >
> > > I am not sure that BRUF can be given the full blame for it, but in all
> > > our internal evaluations we score very low on requirement accuracy.
> > > Also, the start-up of new projects seem to last forever. It feels
> > > wasteful and demoralizing to the developers. (At least on my team)
> >
> > I'm on a contract right now at a gov't agency, and there's a reason that I
> can only realease to production every 6 months: the stakeholders won't allow
> it, because they regard releases as destabilizing. This is to say, of
> course, that they would be horrified by the very idea of continuous
> integration. Somehow, they find pages and pages of BRUF reassuring; I won't
> belabor how perverse that is.
> >
> > So what does one do? Well, I'm not going to work for 6 mos. w/o even
> knowing if my code does what I think it ought to, or what I've told them
> it's going to. That means retrofitting tests to legacy code, because I also
> can't work without knowing what the existing code base does. The BRUF
> culture of my current workplace doesn't require me to work in the BRUF way
> (i.e., waste countless hours pretending that I know what nonexistent code
> does, or how it will pass nonexistent tests). In fact, it more or less
> forces me to do as much XP as I am able with the few developers who will
> pair with me, so that *I* don't have to wait six months to find out what
> I've been doing.
> >
> > I concede that this necessitates a certain amount of duplicity, but it's
> committed in good faith!
> >
> >
> >
> > To Post a message, send it to: [EMAIL PROTECTED]
> >
> > To Unsubscribe, send a blank message to:
> [EMAIL PROTECTED]
> >
> > ad-free courtesy of objectmentor.com
> > Yahoo! Groups Links
> >
> >
> >
> >
> >
> >
> >
>
> To Post a message, send it to: [EMAIL PROTECTED]
>
> To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
>
> ad-free courtesy of objectmentor.com
> Yahoo! Groups Links
>
>
>
>
>
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
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:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
