You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

March 6, 2013

Basic demo/introduction:
I. General overview of change management

  • what is it and why do it?
  • the aim is to minimize the number and impact of any related incidents upon service (minimize risk)
  • to have the ability to trace incidents and problems back to a particular change (triage and root cause analysis)

II. Remedy overview

  • we have licensed the tool
  • it is currently used by DITR and Server & System Administration
  • demonstrate how to enter a change
  • demonstrate approvals and when they are triggered
  • show case reports and what information is available

III. Discussion and designation of the "service advocate"

  • this is the person on the team who will take the lead on making sure the changes have the right amount of info and that changes are actually being documented (maintenance mode)

Merchant Services update:

  • Tim socializing with the group
  • demo to be scheduled end March

RAFT update:

  • RAFT team in the middle of a sprint
  • demo postponed until April
  • Sherene will be joining group

Network Operations update:

  • demo for whole team 3/7
  • select service offerrings from there
  • Sophie will be joining group

Project management update:

  • Sophie will manage Network roll outs

Prototype update:

  • still in negotiations
  • next revision due 3/8

Meeting schedule:

  • go to once a month during roll outs
  • regular updates on prototype and demos
  • No labels