ITIL Process Dependency metrics - Need your comments

[hasanbs2k]

ITIL Process Dependency
ITIL Processes SS SD ST SO CSI
SPM DM FM SG SCM AM SLM ISM SRM ICM CapM KM CM ConM RDM TPS SVT Eval EM IM PM RF AcM CSM CSR CSI
SS
SPM ü ü ü ü ü ü ü ü ü ü ü
DM ü ü ü ü ü ü ü ü ü
FM ü ü ü ü ü ü ü ü ü ü ü ü ü
SG ü ü ü
SD
SCM ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü
AM ü ü ü ü ü ü ü ü ü ü ü ü
SRM ü ü ü ü ü ü ü ü ü ü ü
SLM ü ü ü ü ü ü ü ü ü ü ü ü ü ü
ISM ü ü ü ü ü ü ü ü ü
CapM ü ü ü ü ü ü ü ü ü
ICM ü ü ü ü ü ü ü ü ü
ST
KM ü ü ü ü ü ü ü
CM ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü
ConM ü ü ü ü ü ü ü ü ü ü ü ü
RDM ü ü ü ü ü ü ü
TPS ü ü ü ü ü ü ü
SVT ü ü ü ü ü ü ü
Eval ü ü ü ü ü ü
SO
IM ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü
PM ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü
EM ü ü ü ü ü
RF ü ü ü ü ü ü ü
AcM ü ü ü ü ü ü
CSI
CSI ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü
CSM ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü
CSR ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü ü

Definitions
SPM Service Portfolio Management
FM Financial Management
DM Demand Management
SG Strategy Generation
SCM Service Catalog Management
CapM Capacity Management
AM Avaialbility Management
ITConM IT Continuity Management
ISM IT Security Management
SRM Supplier Relationship Management
SLM Service Level Management
KM Knowledge Management
CM Change Management
ConfM Configuration Management
RDM Release & Deployment Management
TPS Transition,Planning and Support
SVT Service Validation & Testing
Eval Evaluation
IM Incident Management
PM Problem Management
EM Event Management
RF Request Fulfillment
AccM Access Management
CSM Continual Service Measurement
CSR Continual Service Reporting
CSI Continual Service Improvement

[hasanbs2k]

Suggestions to improve

[Diarmid]

I haven't a clue what you are on about.

Are you trying to make it look more like Prince2?

I don't believe ITSM lends itself to abstracted structural rules. By this I mean that the relationships between components are complex and will vary from one adoption and adaptation to another. I cannot give examples because your table does not display properly and I cannot therefore interpret it.

I find a large number of people who start out in fairly technical IT roles, want to boil down complex management processes to (still complex) mechanical formulae (just like a program or an operating system) and use these to drive their service management. This inevitably, and disastrously, distorts the management focus and obstructs proper understanding.

Just an opinion, as always.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718

[RobRoy47]

Your message brought up one of the biggest mistakes in ITIL. We talk about being customer and user oriented, then abbreviate every term in ITIL so that no one can read any documents we produce. Rob's rule:never abbreviate any ITIL term unless it is well understood by non ITIL people without having to go to the appendix.