Skip to main content

Six Reasons to Read the Microsoft Operations Framework (MOF)

The Microsoft Operations Framework (MOF) is a well written, meaningful, asset-rich framework that is often overlooked in favor of its higher profile cousins ITIL, Cobit and ISO/IEC 20000.   Unfortunately, the big "M" that stands in front of the framework has created the perception that MOF is only relevant to Microsoft environments.  Nothing could be further from the truth - Microsoft has invested a great deal of resource and effort in creating MOF intellectual property and assets - giving it all away for free for anyone, in any environment, that is interested in learning more.  In fact, Microsoft considers you a Microsoft customer if you are working at a desktop or laptop running a Microsof operating system.

Microsoft's goal in developing MOF was to improve the effectiveness and efficiency of IT service providers, thereby enabling those providers to get a better return on their infrastructure, applications and tools.  

Here are six good reasons to consider learning more about MOF:
  1. It is compatible with ITIL.  You can "cherry pick" the guidance that makes sense from both frameworks.   If you are already down the ITIL path, some of the guidance, assets and templates may help you overcome some of your bottlenecks and challenges.  MOF may also help to clarify some of the more complex ITIL concepts such as service models - MOF's service maps are easier to understand
  2. It is much more prescriptive and offers up scripted questions at the task or activity level
  3. It uses familiar IT vocabulary - do your clients want "utility and warranty" or do they want "reliability".   
  4. There are many job aids and templates available.  Microsoft has invested quite a bit in creating MOF assets as part of its' Solution Accelerator program.
  5. It is tool independent.  Microsoft does not tie MOF back to any of it's products or services.
  6. It's free - need I say more?

Comments

Unknown said…
Thanks for sharing this. I had unfairly dismissed MOF as a useful resource.

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 th

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem