Nigel et al.,
> 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.
If the agilist can bring about this kind of situation, even where it doesn't yet exist
(i.e., the "mirror" I have to use is currently corrupt, but I'm working on it) then he
can indirectly persuade the client to trust him: his code, his understanding of the
requirements, his methods. No manipulation is necessary.
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/
