Re: Change Management

Connor,

Hopefully they mean "emergency data fix" followed by a "routine code fix". If not, in my opinion, they don't understand ITIL. My understanding of ITIL is that it is never meant to get in the way of "doing the right thing". Usually "do the right thing" accompanied by "ensure all the right people were notified and contributed some wisdom." To merely bandage the problem and leave it at that would imply that their implementation of ITIL has degraded their system quality.

Dennis

On 9/4/08, Yechiel Adar <adar666_at_inter.net.il> wrote:
>
> BANG
>
> Adar Yechiel
> Rechovot, Israel
>
>
>
> Connor McDonald wrote:
>
> ITIL gone mad....I'm currently at a client where a report was
> producing results in the wrong order (because an ORDER BY had been
> omitted from the driving SQL).
>
> But (at this client)..."code fix" is rated more serious (in the ITIL
> world) than "data fix", namely, requires more red tape and more
> approval...
>
> So management opted to hack the data to fix the problem than the fix
> the offending code...
>
> Someone shoot me please...
>
>
> On Thu, Aug 21, 2008 at 3:17 AM, Niall Litchfield<niall.litchfield_at_gmail.com> <niall.litchfield_at_gmail.com> wrote:
>
>
> Hi,
>
> This sounds to me exactly like what an ITIL based organisation would
> describe as a standard change.
>
>
>

--
http://www.freelists.org/webpage/oracle-l