*>>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...*
How about auditor asks for centralized update of changes, and now a bunch of people need to generate mail dumps? You can store change management in your incident/bug tracking system, which will still allow them to get their emails, while you get a centralized repository. *ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market...* On Tue, Oct 28, 2014 at 1:09 PM, 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 > > > > >
