One of the goals I had when I first came to the Frameworks team at Microsoft was to open up the dialogue between the people writing the guidance and the people consuming the guidance - our customers, our partners, and our field. Over the past 18 months, we've been trying different ways of reaching out to see what sticks with you. This is our latest attempt.
This year, our team is going to be doing a significant overhaul to the core MOF IP. For our initial release, we will be focusing on the infrastructure lifecycle, IT Governance, and the activities of the IT pro. As part of this, we will also be revisiting the existing Process Model to reformat, sort, add, and remove SMFs as needed. As we work through the Process Model, we will also be identifying requirements and dependencies between the Process Model and the Team Model to prepare it for a new release as well. One of our goals for the new release of the Team Model is to use it to answer the "Who questions" the Process Model invariably raises. For example, every time we identify a specific task that needs to be done in the process model, we intend to identify the role that should be performing that task as well. Lastly, the current MOF Risk Management Methodology is under intense examination at as part of our focus on IT Governance.
For MOF to be successful, it truly needs to be a collection of best-practices culled from a wide audience. For our team to deliver that, we need your involvement. Please discuss, share your opinions, thoughts, and concerns below.
Let's not lose sight of the fact that several role clusters in the Team Model may be represented in SMF-activities from the Process Model. In fact, everything in the Changing and Suporting quadrants *should* include every role cluster, with the exception of Service Desk.
I would like to reemphasize on the “People” aspect. In the current version of MOF, there is a great focus on the process aspect, and nearly neglecting the execution arm: People. A clear connection should be made between those processes defined and people who are held responsible and accountable for the execution and improvement.
One of the difficulties faced during process implementation project is the IT team maturity. They are not able to realize the value of processes because they are always in fire fighting mode and want to have their job done. If roles and responsibilities are well defined, and the who-does-what matrix is in place, then we can definitely expect fruity results when it comes to processes work. This leads to the right implementation approach of processes supported by more mature IT team.
Great to see more MOF blogs ;-)