Beruflich Dokumente
Kultur Dokumente
Presented by
Jeff Connie, IBM, IT Infrastructure Principal
jconnie@ca.ibm.com
403-539-3308
IBM Global Services
Process
Clearly defined
Standardized, roles and
federated, IT Service responsibilities
accessible Information Management People
provide a sound
information decision-making
framework
Technology
Service Delivery
Capacity Mgt Performance
Service Level Mgt Availability Mgt Management
SERVICE Financial Mgt
ENTRY
POINT
Service Continuity
Security
Demand Mgmt.
Operations IT Infrastructure
Filling the design and implement gap will require adopting and
adapting ITIL best practices with a phased and structured
approach
Pilot
Develop/Test
Design
Plan
Sy em e IT
Relation-
an rp v
ag a tu
M nte Pro
In
em t
e nd re
st en
ships
IT
E
efforts – which can lead to
Support IT
Services and
Manage IT
Business
Significant rework
Solutions Value
Unwanted items
Costly duplication
l
es a
Re utio
So
ic on
Se per er
al ns
O eliv
l
rv ati
iz
e
D
Deploy
Solutions
Scope creep
ITIL
SEI CMM
Cancellation
A.S.L.
Lot’s of education
A.D.E.
The good news! This is not new and there is an extensive library of
ITIL based templates to facilitate rapid assessment and design
available in the market
• Change Management will control all changes to all Configuration Items (CIs) in the
managed environment by:
• Ensuring standardized methods, processes, and procedures are used for all
changes from the request for change to the post-implementation review
• Facilitating efficient and prompt handling of all changes
• Minimizing the impact of Change-related Incidents upon service quality thus
improving the day-to-day operations of the organisation
Maintain a proper balance between the need for Change against the impact of the
consequently to improve the day-to-day operations of the organization.
ITIL Service Management Guide • Maintain open channels of communication in order to promote smooth transitions
when Changes take place.
• The process starts with the recognition of the need to put in place and define a
ITIL Metrics •
management system to control Change, including procedures and policies; it ends
with the change being installed and activated.
The process includes managing changes from the creation of a request, its
•
Management Surveys
The process of Change Management is principally managing the Change.
• The process does not include the technical design and testing of the Change
• The process does not include the actual implementation of the Change, but
ROI Calculator Tool manages and coordinates the implementation of the Change may also be
performed by the calling process, e.g. Release Management.
• Typical in scope changes include:
Workshop Materials • Hardware, Communications Equipment and Software, System Software, Live
Application Software, All Documentation and procedures associated with
Project Plans
running, supporting and maintaining the production environment
• Changes to ongoing projects are out of scope.
Accept & Much confusion over Clear entry point(s), but Good enforcement of Clear entry point(s); Change entry is
Classify the change entry authorization process required information; authorization works automated and process
process, or there are unclear, and known to be tools/database used (evidence of some rules enforced as a
Changes multiple (possibly frequently bypassed. effectively; "informal" "rejects" or requests that result - lead times,
changing) entry points. Required information is authorization process, need to be resubmitted process path,
IT gets involved late in not known by all. possibly with some due to insufficient authorization
the cycle -- no notion of "rubber stamping". Some information). requirements etc. are
authorization to request RFCs are rejected early Change Manager always correct.
changes on if data is missing or confirms all priorities and Emergency RFCs are
there is an obvious categories. RFCs are always justified and
conflict of dates. Many always sent to the correct handled correctly
RFCs are classified as areas for assessment.
ly
Emergency and allowed Some Emergency RFCs
On
through the process are due to poor planning
tra
Changes via the evaluation criteria: criteria and required includes risk assessment. balance struck between based on criteria that
Ex
not information; process Lead times defined for all process standardization adapt to practical usage;
Change agreed/communicated known to be frequently changes, but not (automation) and organisation feels
Advisory with the change bypassed. Little or enforced. Change types meeting varied positive about using the
Board (CAB) / process participants, ineffective risk are defined but do not departmental needs. change management
Emergency and possibly changing assessment. Lead times include all changes. CAB Risk assessments always process; feedback loop
depending on the defined for major / EC sometimes limited to done. Lead times in place. All change
Committee assessors. There is no changes. Regular CAB those affected by the required for all changes types accepted and
(EC) CAB. meetings with a large change. RFCs sent out are enforced. Change controlled. CAB / EC
group of people electronically for CAB types defined for all frequently consider
preview changes. Membership of RFCs electronically
CAB / EC always varies, without the need for
depending on the RFCs physical meetings.
being reviewed. Business Relevant business areas
areas may be always involved in CAB /
represented on CAB EC decisions
Each phase of
Strategy
Technology Data
this lifecycle are
influenced by the
Assessment Processes Organization
following factors:
Selection
High level design Infrastructure &
Organizational
Complexity
Customization
Requirements
# of Physical
Detailed Design
Operation Locations
Development
Manage Delivery
Deployment
Phase 1: Strategy
And Assessment
Visions and
Where do we
business
want to be? Strategy
objectives
Planning to Implement
Assessment
Selection
Where are we
Assessments
now?
How do we get
where we want Process Change
to be
How do we
know we have Metrics
arrived
Overall Rating
What is healthy?
Maturity
Effectiveness
Identifies specific improvements improvement
programs
Information
Information Services
Services People
People
Strategy
PILOT
es
Selection
n Teachers
o
st Customized & tested
ile t enabling technologies
m en
r
le
a
g em
c a
es , an Acquire people
tiv ct M
DEV
a
Detailed Design
i
it oje
Develop curriculum
in Customize and test tools
Pr
Development
ed
as
Ph
Deployment
DETAILED
Define jobs & staffing
DESIGN
Workflows Phase 3: Implement Solution
Tool customization requirements
Select and install base tools
DESIGN
Define tool requirements
MACRO
Process definition based on best practices Technology Data
Governance model Processes Organization
Guiding principles
Compelling reason to act High level design
Detail Design
ESM Lifecycle Phase 2 Architecture Data ESM Lifecycle Phase 3
Design the Processes Organization Develop Implement the
Solution Deploy
Solution
High Level Design
Outsourcing Solution
Service
Provider
Offering
How long it takes to design and implement a management solution is based on the need or desire for customization
Process Guide
Definition
Process Team Process Team Process Team mission
#1 #2 #3 scope
inputs& outputs
activities
Define IT Services measurements
2
1
Task Name
Start Stage III
Intranet
3 Reconfirm Project Scope, Objectives, Assumptions , Dependencies
4/8 4/8
x x x x x x x x x Elements
4 Set Up Project Environment
4/8 4/8
5 Develop Project Plan
Implementation Plan
7 Meet with Tivoli project manager
4/29 4/29
8 Meet with Remedy project manager
4/29 4/30
9 Refine Tasks
4/30 5/2
10 Refine Schedule
5/2 5/3
11 Refine Resource Plan
5/3 5/6
Internet
x x x
12 Document Project Success Criteria
x x
5/6 5/7
13 Review Project Plan
To Be Managed
5/9 5/9
17 Conduct Project Kick Off with Aurora
5/10 5/10
18 Conduct Project Kick Off with AD building participants
4/8 4/8
19 Document Success Criteria
Office Suite
20 Success Criteria for Processes
4/8 4/8
25 Develop Costs
E-mail
x x x x x x x x x
If a phase 1 assessment has not been done, a fast design based assessment is required to gather the information needed at the
beginning of the project to ensure a rapid successful completion
ES ign or orts ld
Select & procure tools
OC es d W Rep , Fie
Jo
s
PR el D taile def, mes
ow
Configure software and hardware
Re cript el D LE
Cu urc
De gh-le EO
k fl
a
so
rri e A Staf
enlot N
Hi
s
cu
Physical data model
re Pi en
ion es
v
P
Po nts, y, S
, T sitio Lev
Organization S
s, ign
ra n
e
e g
-le D
ini
em lo
P
ur no
gh s ,
ng
Define jobs and roles
v
Hi licie
as ech
Me , T
TOOLS
els
me du
High-level Design
Skill gap analysis
Na roce
Orientation
Training Materials, TTT Pilot Team
Testing
Develop test cases
Test every aspect Unit test
cases
User
Integration System
Unit Test Acceptance
Test Test
Unit test Test
System Integration cases
test cases test cases
tsJo
Re esc gh-l
en
b D Hi PEO
so rip eve
em
Organization
Tr
ur
OC sig sur
ce ions De
ain quis affin
PR el D Mea
ing itio
Ac , S sign
ws s
t
gh Flo dure
Train people on the new system
or roce t
P Pi l o
SS
,
e
E
l
t
n
PL
ev
Validate staffing levels, roles and
k
-L
gL
W
ev
Hi
TOOLS
,
responsibilities
ies
els
lic
High-Level Design
Po
Tool Selection & Installation
Technology Tool and Data Customization
Pilot
Validate tool functionality
Pilot Objectives
Populate data Process and Organization Effectiveness
Workflow is logical and understood by participants
Appropriate information is captured
Meaningful reports are generated
Month 2 Identified roles and staffing levels are valid
ID Task Name Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8
1 Responsibilities are understood
2
3
Process is perceived to add value
Multiple location concept is supported Example
4 Documentation and Training Effectiveness
5 Documentation is of high-quality
6
Training provided is sufficient to use the tools and the process
7
Tool Functionality and Usability
8
Tools are easy to use for all participants
9 On-line help is sufficient
10 Performance is within acceptable ranges
Problems and changes are automatically routed to correct assignees and approvers
Tools adequately support the process
Tools support central coordination and distributed functionality and control
7
PILOT
Technology
8
10
6
Process
7
8
DEPLOYMENT
9
10
CI’s Problems
Incidents Changes Releases
Relationships Known errors
Configuration management database
Service Desk
Release HLD
Problem HLD
Incident Detail Design
Phase 3
Implement Configuration Detail Design
Technology
9 Planned implementation
9 Structured approach
Process