Skip to main content

MOF Management Reviews

Let’s continue our discussion on IT Service Management Frameworks. Recently, we talked about the question based guidance in the MOF Solution Accelerators. Now, I would like to offer you additional information on the MOF Management Reviews. MOF Management Reviews will help organizations ensure that their technology services are on track to deliver expected business value. They offer guidance to help management set goals, evaluate progress and confirm results. The MOF Layer/Phase and the aligned Management Review is listed as such:
  • Manage Layer
    • Policy and Control MR)
  • Plan Phase
    • Service Alignment MR
    • Portfolio MR
  • Deliver Phase
    • Project Plan Approved MR
    • Release Readiness MR
  • Operate Phase
    • Operational Health MR
The Management Reviews can be used as checklists to ensure we have completed tasks correctly. For example, the Release Readiness document offers a comprehensive review of the deliverables produced. It delivers an assessment of the readiness of the business to employ the solution. The operability and supportability of the release is confirmed, the overall quality of the release is assessed. Addressing this milestone gives the service provider an opportunity for customers and users, operations and support personnel, and key project stakeholders to evaluate the solution and identify any remaining issues that they must address before deployment. This Management Review ends with a GO/NO-GO decision to deploy the new or changed service. This is just one example of the 6 reviews in the MOF framework.

Available for free download are detailed diagrams of all the MOF Management Reviews. The diagrams offer a one page summary of the goals, inputs, outputs, key attendees, meeting frequencies, and milestones for each of the six MOF reviews. There is some great information to be found quickly in this visual representation. I have included the link below which will allow you to download the Management Reviews and their accompanying diagrams. Go out and download the information, take a look at it. I am sure some, if not all, of the reviews can be incorporated in your service management program.

http://technet.microsoft.com/en-us/library/ff653519.aspx

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…