Professional Documents
Culture Documents
50217A-ENU Powerpnt 08
50217A-ENU Powerpnt 08
50217A-ENU Powerpnt 08
Organizational Analysis
1
Lesson objectives
Understand the different role types needed
in the organization
Define Personas for Service Manager
2
Team Service Management
Function Overview
Goals of the TEAM SMF
Accountable: ensures that required IT work gets
done
Responsible: identifies who will do required IT
work through:
Creating role types and roles
Establishing principles and best practices
Identifying who is best for each role
Flexible: built around agile physical and virtual
teams
Scalable: able to meet the needs of different-sized
organizations
3
Role Types and Responsibilities
Each accountability has a set of role types associated with
it, and each role type has a set of responsibilities and goals
associated with it
Accountabilities can be described in the following way:
Accountability = Who (owner)
Advocacy for quality = Why
Responsibility = What (details)
Tasks/activities = How
4
Role Types and Responsibilities
The following will be described
Support
Operations
Service
Compliance
Solutions
Management
5
Role Types and Responsibilities
Support Accountability
Role Type Responsibilities Goals
Customer Service Handles calls Help the customer
Representative
Is first contact with user
Investigates
Resolves
Incident Coordinator Responsible for incident from Solve incident as quickly as
beginning to end (quality possible
control)
6
Role Types and Responsibilities
Support Accountability
Role Type Responsibilities Goals
Problem Analyst Investigates and diagnoses Find underlying root causes of
the incidents
Customer Service Accountable role for the goals of Effectively and efficiently
Manager
support decrease incidents and incident
solution time
Covers incidents and problems
Increases effectiveness of
resolutions and reduces costs
7
Role Types and Responsibilities
Operations Accountability
8
Role Types and Responsibilities
Operations Accountability
Role Type Responsibilities Goals
Monitoring Manager Responsible for Service • Ensure needed monitoring
Monitoring and Control (SMC) information is generated
SMF tasks
Administrator Executes tasks that are not well Ensure predictable results
defined, requiring a deeper level
of knowledge
10
Role Types and Responsibilities
Compliance Accountability
Role Type Responsibilities Goals
Risk and Compliance Owns risk management, Organization does not violate
Manager
compliance roadmap, laws or regulations
enforcement, and measurement
Risks are identified and
managed
discovered
11
Role Types and Responsibilities
Compliance Accountability
Role Type Responsibilities Goals
Internal Control Manages internal control Effective control environment
Manager
environment, document control documented with audit trails
objectives, and control design
Appropriate retention of
Retains evidence of control control operating evidence
activity
Legal Analyzes regulations and Policy reflects desired response
determines policy impact to regulation
13
Role Types and Responsibilities
Solutions Accountability
Role Type Responsibilities Goals
Program Manager Drives design, schedule, and Ensure that individual projects
resources at the project level run smoothly, and build the
Tester Tests to accurately determine the Ensure all known issues are
quality of solution development resolved before release
14
Role Types and Responsibilities
Solutions Accountability
Role Type Responsibilities Goals
Release Management Evaluates the solution design Ensure a stable solution is
deployed to the production
Documents operations
environment
requirements to ensure that they
are met by the design
Assurance and Validates design and operating IT organization constantly
Reporting
effectiveness of IT organization, under review and continually
processes, and control being improved
environment
Board and shareholders
Recommends changes for confident in management
improvement decision and resulting
processes 16
Role Types and Responsibilities
Management Accountability
Role Type Responsibilities Goals
Change Manager Manages the activities of the Change that is planned and
change management process for understood, with risks that are
the IT organization managed
Configuration Tracks what is changing and its Configuration changes are
Administrator
impact recorded
17
IT Management
Niels
Projects Security/US
Klaus Greg
Legend
Accountability Color
Support
Operations
Service
Compliance
Architecture
Solutions
Management
18
IT Management
Niels
Projects Security/US
Klaus Greg
Service Management
TBD
Legend
Accountability Color
Support
Operations
Service
Compliance
Architecture
Solutions
Management
19
No Accountability
Microsoft Role Model
Financial
Portfolio Service Level Manager Change
Managers Manager Manager
Resource
Account Planner
Managers
Supplier Architecture Manager
Managers Service Capacity Manager
Skills Manager
Architects
Security Officer Security Infrastructure
Compliance Builders
Auditors Testers
Test Manager
Partner Release Configuration Manager
Release Manager
Release Coordinators
Service Desk
Operations Support
Operators Manager
Problem
Administrators Manager
Operations Incident
Area Managers
Manager Call Handler Incident Manager
Scheduling Monitoring Coordinator
Manager Manager Incident Problem
Resolver Analyst
20
The Team SMF throughout MOF
Plan Phase:
Determine who is
involved in creating IT
strategy
Deliver Phase:
Determine who is part
of the project team and
how do they work
together
Operate Phase:
Determine what roles
and responsibilities are
needed to keep
Operations and
Customer Service
running smoothly
22
Out of the Box User Roles
End Users* (Global scope)
Read-Only Operators (Global scope)
Incident Resolvers (Global scope)
Change Initiators (Global scope)
Change Owners (Global scope)
Activity Implementers (Global scope)
Advanced Operator (Global scope)
Authors (Global scope)
Workflows*
Administrators*
Administrators* [Data Warehouse]
25
Contoso, Ltd.
26
Contoso, Ltd.
Jeff Ford has decided not to change the
organization to much, but wants to make sure it
aligns with the roles in the MOF TEAM model
Reviews the roles described in the next 2 slides
MAP the roles to the people working at Contoso IT
today
Verify if they are used in the right way and if the right
responsibilities are given.
Which roles could be added (are messing) and who
would be the right people to own them?
Which roles do you see as conflicting?
27
Contoso, Ltd.
The following Team roles should be assigned
to the IT staff at Contoso:
Customer Service Representative
Consoto Staff Name:
Incident Resolver
Consoto Staff Name:
Incident Coordinator
Consoto Staff Name:
Problem Analyst
Consoto Staff Name:
Problem Manager
Consoto Staff Name:
Customer Service Manager
Consoto Staff Name:
28
Contoso, Ltd.
The following Team roles should be assigned
to the IT staff at Contoso:
Operator
Consoto Staff Name:
Administrator
Consoto Staff Name:
IT Policy Manager
Consoto Staff Name:
Change Manager
Consoto Staff Name:
Configuration Administrator
Consoto Staff Name:
Release Management
Consoto Staff Name:
29
Contoso Scenario Personas
Name Face Title Responsibilities
30
Contoso Scenario Personas
Name Face Title Responsibilities
31
Contoso Scenario Personas
Name Face Title Responsibilities
32
Contoso Scenario Personas
Name Face Title Responsibilities
33
Summary and Class Discussion
Identify Role Types needed for Service
Manager
Class Discussion
34
Organizational Analysis Review
Questions
Goals of the TEAM SMF
35
Real life example!
TECH SUPPORT: "O.K. Bob, let's press the control
and escape keys at the
same time. That brings up a task list in the middle
of the screen. Now type
the letter "P" to bring up the Program Manager."
CUSTOMER: "I don't have a 'P'".
TECH SUPPORT: "On your keyboard, Bob."
CUSTOMER: "What do you mean?"
TECH SUPPORT: " 'P' on your keyboard, Bob."
CUSTOMER: "I'm not going to do that!
36
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not
be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
37