Process Diagrams

High-Level Change Management Stages

Trying to stick to ITIL roles and definitions.

Actor	Definition
Change Requester	the person initiating the change request
Change Owner	the person who manages a particular request through assessment and implementation
Change Implementer(s)	one or more people who implement the change
Configuration Item (CI) Technical Owner	manager of the group which has technical ownership of a particular CI (contrast w/ functional ownership)
Change Advisory Board (CAB)	group of people in charge of approving changes and monitoring the forward schedule of changes
ITSM Tool	the application providing an engine for processing & recording change requests, metrics

Pre-Approved

Object	Attributes
Change Request	Short Description, Description
Pre-Approved Change	CI Filter, Short Description, Description

Name	Aliases	Type	Derivation/Rules
Short Description		string	user supplied, or sourced from approved change
Description		multiline text	user supplied, or sourced from approved change
Proposed Date/Time		(pair of) formatted strings	default to earliest based on lead time criterion, overridable
Actual Date/Time		(pair of) formatted strings	derived from activity, but overridable
Implementation Code	Status (discouraged alias)	string, integer pairs	user provided; one of: success, partial, failed
Submission Priority		string	derived from draft date/time vs. lead time criterion: planned, latent, urgent-unplanned, urgent-emergency
Change Requester	Requested By	user object reference	derived from user who requests change
Change Type		string	one of: Minor, Significant, Major, Pre-Approved; derived from use of pre-approved changes or calculated as a function of CI Risk, CI Impact, and a user-supplied Risk/Confidence estimate.

Maybe these can be answered by running through use cases:

Assessment - do we define subtasks to deal with parallel & sequential work? What are the constraints?
Original BP recommendation was to disallow emergency changes unless solving a problem. Enforce?
What is our lead time criterion (used to determine submission priority)?
Pre-approved changes don't have to be change requests per Fruition's recommendation. How do we draw the line? how about no changes for non-CIs? (check out this random blog that happens to agree: http://itsmspot.blogspot.com/2009/03/differences-between-standard-changes.html)