Profile

IBM used to (and may still) use the IMAC lettering for service requests: Install/Move/Add/Change. There's not much that falls outside of these buckets. At UBC, we track Information Requests separately from Service Requests as if we can get a handle on the volume of IRs, we can assess the quality of our ...

Hi Sarah, In a previous role, my team and I used the following criteria to determine eligibility for a Standard change. Definition of a standard change: A standard change is a change that is recurrent, well known, has been documented to follow a pre-defined, relatively risk-free path, and is the ...

Hi Lucas, I've shared the blank template in the library as you suggested. For anyone contacting me directly, I am sharing additional context based on my own experience of how UBC IT has used the CIR as part of its broader Change/Incident Management processes. Thanks, David. ------------------------------ ...

Please find the Critical Incident Review template used by the University of British Columbia.

Sure thing Marcus - please PM me your email and I'll send on the info. David ------------------------------ David Johnston The University of British Columbia ------------------------------

Hi Sarah, In my past life as a CAB chair, the UBC IT CAB community and I took care to keep the weekly CAB meeting strictly focused on forward-looking changes, and leaving to BRMs, technical teams and affected business units the tasks of reviewing of changes which had turned out to be unsuccessful or ...

Hi Mitch, Your audience may be much wider but I have a very small use case that I think I may as well share. We run a weekly CAB meeting in our IT org. Although our meetings were well-attended, with representatives from every major service, we were noticing an apparent lack of engagement within the ...