Problem Management CAB

[nzmoko]

Hi all, new to the forum.

We are going down the ITIL PM road and want to govern changes made to our internal processes/documentation.

Should we do this via an internal PM CAB or is it better to have the docs as CI's and create a normal RFC to have the process and associated documentation discussed, agreed and changed?

Appreciate your views.

[UKVIKING]

What about the other processes ?

There should be some method / process where the documentation is reviewed and approved

it depends on whether the CAB members are the right people to sign off on the PM process
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[bennyboy]

[Diarmid]

Changes to processes are no different to any other changes.

They have a reason (mostly resolving problems, improving service or reacting to changed circumstances).

They have a specification.

They have an implementation plan (including back-out)

They have cost and risk associated with them.

Approval, evaluation, scheduling, implementing and reviewing all have to be done by the people best placed (by competence, interest and authority).

It makes sense to manage these changes under the same umbrella because there is the same conflict resolution and information management to control and one universal process has obvious benefits. But other approaches should work as long as communication is good and everyone has good understanding of what they are doing in the big picture.

By the same reasoning, and irrespective of how you manage process change, there is much to be said for holding processes and their documents in the CMDB. After all services have dependencies on processes.
_________________
"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