Академический Документы
Профессиональный Документы
Культура Документы
Presented by
Dave Deleske
Agenda
Discuss Objectives
LSS Overview
ITIL and LSS
DMAIC Tool Set
Review Project Selection Criteria
Review Define Phase and Tools
Problem Statements and Business Case
Review Benefits and Concerns'
Objectives
Start on time and stay on schedule
Encourage support of LSS through
understanding and open communication
Provide a foundation and tool set for
measureable Improvements of Service for
the University
Incident Management
Project Management
Change Management
Application Development
Config Management
Server Deployment
Any Process
Incident Management
Problem Management
Change Management
Release Management
Config Management
Processes Work Flow Variation and
Time
Incident Management
Problem Management
Change Management
Release Management
Config Management
Processes Work Flow Variation and
Time
Error
Opportunities
Incident Management
Problem Management
Change Management
LSS
Lean = Is to Trim rework,
waste, delays
Sigma = Is to Reduce
Variables / Deviations
Release Management
Config Management
Processes Work Flow Variation and
Time
DEFINE
ANALYZE
IMPROVE
MEASURE
CONTROL
DEFINE
MEASURE
ANALYZE
IMPROVE
CONTROL
Activities
Identify Problem
Complete Charter
Develop SIPOC Map
Gather Voice of the
Tools
Pareto Charts
Project Selection Tools
Project Management
Various Financial Analysis
Charter Form
Stakeholder Analysis
Communication Plan
SIPOC Map
High-Level Process Map
VOC and Kano Analysis
Quality Function
Deployment (QFD)
RACI Charts
Thought Process Map
MEASURE
Identify Key Input, Process and
Output Metrics
Develop Operational Definitions
Develop Data Collection Plan
Validate Measurement System
Collect Baseline Data
Determine Process
Performance/Capability
Validate Business Opportunity
Map Business Process
Map Value Stream
SIPOC Map
Operational Definitions
Data Collection Plan
Statistical Sampling
Measurement System Analysis
ANALYZE
Propose Critical Xs
Prioritize Critical Xs
Conduct Root Cause
Analysis on Critical Xs
Validate Critical Xs
Estimate the Impact of
Each X on Y
Quantify the Opportunity
Prioritize Root Causes
Pareto Charts
Affinitization
C&E Matrix
C&E/Fishbone Diagrams
Brainstorming
Detailed As-Is Process Maps
Basic Statistical Tools
Non Value-Added Analysis
Confidence Intervals
Hypothesis Testing
Non-Parametrics
FMEA
Box Plots
Interaction Plots
Multi-Vari Charts
Logistic Regression
One-way and Two-way ANOVA
ANOM
Box-Cox transformation
QFD-2
Scorecards
Excel Analysis Tools
IMPROVE
Develop Potential Solutions
Develop Evaluation Criteria &
CONTROL
Develop SOPs, Training Plan
Implement Process
Brainstorming
Benchmarking
Solution Selection Matrix
Process Improvement
Control Charts
Standard Operating
Techniques
Process Balancing
Process Flow Improvement
Queuing Theory
Design of Experiments (DOE)
Replenishment Pull
Poka-Yoke
FMEA
To-Be Process Maps
Piloting and Simulation
Response Surface Methodology
QFD 3
Crystal ball Simulation
Scorecards Gap Analysis
Owner
Identify Project Replication
Opportunities
Calculate Financial Benefits
Procedures (SOPs)
Training Plan
Communication Plan
Implementation Plan
Visual Process Control
Process Control Plans
Project Commissioning
Project Replication
Plan-Do-Check-Act Cycle
Scorecards
Dashboard
Project Selection
Some things to watch for when
assessing a projects suitability for
DMAIC:
Is data available or easy to obtain?
Does leadership support exist for improving this process?
Is DMAIC really needed or is this a just do it: a problem
with a known solution that should just be implemented?
Is the team trying to boil the ocean or is the scope
reasonable for chartering as a DMAIC project?
Is the process directly related to a key outcome such as
profitability, customer satisfaction, or employee
satisfaction?
Uses DMAIC
Addresses each phase
Includes some of the tools
Involves 1-3 people
In an area you control or influence
Can be done within a month
Provides a measurable benefit
Define Objectives
Six Sigma calls for unmistakable, measurable results, the
goal of the Define phase is to clearly identify and articulate
the problem in a clear and measurable way.
The basic steps to the Define phase of DMAIC are
Define Tools
The tools most commonly used in the Define phase are:
- Voice of the Customer
- Critical-To-Quality (CTQ) tree
- Affinity Diagram
- Process map
- Project Charter
- Suppliers, Inputs, Process, Output, and Customers
(SIPOC) - Kano Model
- Stakeholder analysis
CTQ
Good
Customer
Service
Friendly
Timely
General
Hard to Design To
Specific
Easy to Design To
Process Mapping
Document
client request
/
requirements
Perform
required
Tasks or
attempt to
resolve Issue
Classify
Incident
Service
Request
Close Ticket
or Assign ISR
to
appropriate
Support
Group
Client Requests
Systems Events
System Changes
Select
Service Type
4 items
Select
Product
Categorizatio
n
300 Items
Select
Operational
Categorizatio
n
15 Items
Select
Support
Group
60 Groups
Close Ticket
or Assign ISR
to
appropriate
Support
Group
Client Requests
Systems Events
System Changes
Inputs
Support Center
Operations
Tier 2 and 3
Process
Incident Service
Request
Categorization
Support
Categorization
Design
Applications
(Remedy)
Configuration
Enter client
information
Document
client
request /
requirements
Perform
required
Tasks or
attempt to
resolve Issue
Outputs
Customer
Detailed Activity
Business
Reports
Service Request
Cycle Time
Accurate / Reliable
Information
Service Metric
Owners
Service Owners
Problem
Management
Management
Classify
Incident
Service
Request
Close Ticket
or Assign ISR
to
appropriate
Support
Group
Date:
Deployment Manager:DaveDeleske
Business Impact
Whyshouldwedothis?Inaccurateinformationbeingenteredintoourcurrentservicerequestsystemisrestrictingourabilitytomeasureand
managetechnicalissuesrelatingtoclientservices.UCITneedsacompleteunderstandingofallrequestsandissuesbeingaddressedin
astructuredandconsistentformat.
Whatisthebenefit?Theabilitytoanalyzereportandmanageincidentsandproblemswithhighprioritybasedonfrequencyandimpact.
ServiceLevelManagement,IncidentManagement,ConfigurationandProblemManagementrequireawelldefinedcategorizationschema
thatisusedandconsistent.Improvementstoworkflowandrework.
Whatisthequantifiedvalueoftheproject($$$)?
Howdoesthisprojectalignwiththebusinessstrategy?CSIforITSMandourservicedelivery.Metricsaroundservice
Project Scope
Whataretheboundariesoftheinitiative(startandendstepsoftheprocess)?
OperationalCategories,ProductCategories,ResolutionCategorization
Whatauthoritydowehave?TheseImprovementswilleffectConfigurationandIncidentManagement.Theyalsohaveadependencytoall
otherITSMinitiatives.TheprojectteamconsistsofboththeBusinessOwnerandServicesOwnersofeachareaimpacted.Theprojectteam
includestheownersoftheclassificationteamandthesupervisorofthefirstlinestaff.
Whatisnotwithinscope?ImprovementsorchangestoanyotherfeatureswithinRemedynotrelatedtoClassificationorCategorization.E.g.
Scripting,Templates,DecisionTreesetc
Team Selection
Whoaretheteammembers?Whatistheirrole?Howmuchoftheirtimewillbededicatedtotheproject?
Core Team:
IanWhitehead-IncidentManagementServiceOwner,ProjectLead
DaveDeleskeConfigurationManagementServiceOwner,BusinessAnalystLSSLead
IvanRunionsApplicationSupport
Extended Team:
CherylNealonConfigurationCoordinator
SimonSharpeBusinessOwnerITSM,Remedy
Problem Statement
Business Case
What are the compelling business reasons for embarking
on this project?
Is the project linked to key business goals and objectives?
What key business process output measure(s) will the
project leverage and how?
What are the rough order estimates on cost
savings/opportunities on this project?
Goal Statement
What is the goal or target for the improvement team's
project?
Do the problem and goal statements meet the SMART
criteria (specific, measurable, attainable, relevant, and
time-bound)?
Has anyone else (internal or external to the organization)
attempted to solve this problem or a similar one before?
If so, what knowledge can be leveraged from these
previous efforts?
How will the project team and the organization measure
complete success for this project?
Review
Benefits and Concerns
Benefits
Concerns