Thanks for the feedback everyone.
Fortunately budgeting isn’t an issue, and we only rolled out this change management process two weeks ago and we’re still refining it. Knowing how momentum works, I’d rather change this now than try to change it six months from now when I’ll hear “how will we being everything over?” and “but everyone is used to this process now…”. From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Chenault Sent: Tuesday, October 28, 2014 10:17 AM To: [email protected] Subject: Re: [NTSysADM] Change Management process and documentation We use Salesforce for ticketing which has a change control process within it. I'm guessing budget is limited. Perhaps a PF? On Oct 28, 2014, at 10:11, "Dave Lum" <[email protected]> wrote: We are defining a new change management process at %dayjob%. The current consensus is to do it all via email, which for reason’s I can’t fully explain gives me fits. I’ve been asked why not email and I can’t come up with anything more useful than “new engineer starts and has no way to review previous changes”. Kind of a weak argument… %dayjob% is a smallish company (~250 employees) that does have to worry about HIPAA but currently shows no interest in following ITIL guidelines. What do you guys use and if not email, why not? Dave Lum \\ I.T. Garage [email protected] \\ 503.267.9764 (voice/text) www.theitgarage.com
