FI - 28 June 2005 1 FI - Focus Improvement system Step 0 Team Charter Step 1 Mapping the current process Step 2 Identify defects Step 2 5 Why Analysis.

Slides:



Advertisements
Similar presentations
Project Management Concepts
Advertisements

Keerti Bhusan Pradhan Faculty-LAICO Aravind Eye care System, India
Project leaders will keep track of team progress using an A3 Report.
1 Discipline, Capability and Grievance resolution: for those with responsibility for others Jessie Monck, PPD, Human Resources Division.
EvalS Application User Guide version September 17, 2011.
Tree Diagrams 1. Learning Objectives Upon completing this module, you will be able to:  Understand the purpose and use of a Tree Diagram (TD)  Construct,
A practical tool for driving customer-focused change.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Standard Work Standard Operations Training Pack. Aims & Objectives Target Audience Production staff, ME & Training personnel Aim To give attendees the.
Motivation Helen Walker.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Task analysis 1 © Copyright De Montfort University 1998 All Rights Reserved Task Analysis Preece et al Chapter 7.
Engineering Design Process
APPLIED LOGISTICS The Productivity Improvement Program for Warehousing and Transportation.
Implementation of Project Governance at the Center Level
Sharif University of Technology Session # 4.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
Release & Deployment ITIL Version 3
Introduction to Quality, Cost & Delivery
Sense of Initiative and Entrepreneurship This project has been funded with support from the European Commission. This [publication] communication reflects.
Lecture 10 Human Resources Looking after the human side of the business. It is the set of activities that must be done to acquire.
LESSON 8 Booklet Sections: 12 & 13 Systems Analysis.
Achieving Quality: Involving clients, staff and other stakeholders in quality audits Claire Tuffin, Head of Business Excellence.
Value Analysis/ Flow Analysis
2011 PK Mwangi Global Consulting Forming a Strategy for your Business. Strategy refers to the plan that needs to be put in place to assist the business.
Basic Cost Concepts COST ACCOUNTING Chapter One. LEARNING OBJECTIVES  To understand the meaning of different costing terms  To understand different.
Quality Directions Australia Improving clinical risk management systems: Root Cause Analysis.
Goal Setting The foundation of a plan for success includes goal setting and the achievement of goals.
The Audit Process Tahera Chaudry March Clinical audit A quality improvement process that seeks to improve patient care and outcomes through systematic.
Lecture #9 Project Quality Management Quality Processes- Quality Assurance and Quality Control Ghazala Amin.
CP methodology adapted to UNFCCC Swedish International Development Agency S ESSION 9.A United Nations Environment Program Division of Technology Industry.
1. 2 IMPORTANCE OF MANAGEMENT Some organizations have begun to ask their contractors to provide only project managers who have been certified as professionals.
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
Project design & Planning The Logical Framework Approach An Over View Icelandic International Development Agency (ICEIDA) Iceland United Nations University.
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
1 How to make the GEOSS Data CORE a reality Part 1 Max Craglia Presented on behalf of Max by: Alan Edwards, EC Stefano Nativi, CNR.
Participate in a Team to Achieve Organizational Goal
© Mahindra Satyam 2009 Configuration Management QMS Training.
 Job evaluation is the process of systematically determining the relative worth of jobs to create a job structure for the organization  The evaluation.
Building Human Resource Management SkillsNational Food Service Management Institute 1 Delegating and Empowering Objectives At the completion of this module,
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
WHY DO WE DO THIS? WHY DO WE DO THIS? WHAT WILL WE DO? WHAT WILL WE DO? WHAT WILL WE ACHIEVE? WHAT WILL WE ACHIEVE? Quality Consultants NAME OWNER AND.
Introduction to Kaizen Introduction Kaizen Facilitation.
© RAN ONE Inc Page 1 J.R. HAY & COMPANY INC. CHARTERED ACCOUNTANTS Is this you? Don’t know what your vision is? Are you achieving it? Are you making.
APPRAISAL OF THE HEADTEACHER GOVERNORS’ BRIEFING.
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
BSBPMG404A Apply Quality Management Techniques Apply Quality Management Techniques Project Quality Processes C ertificate IV in Project Management
Implementing Strategy Chapter 7. Objectives Upon completion of this chapter, you should be able to:  Translate strategic thought to organisational action.
The Implementation of BPR Pertemuan 9 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
The Nature of Organisation Chapter 2, page 55. Structure of Part 1: The Nature of Organisations The concept and role of organisations Elements of an organisation.
Quality Assurance. Define Quality (product & service) Exceeds the requirements of the customer. General excellence of standard or level. A product which.
Six Steps To Problem Solving A simple systematic approach to problems and issues faced by students By MK NKWANE g15N7271 TUESDAY GROUP.
Scrum Overview. Agenda What is scrum…and what it isn’t Scrum’s Characteristics The Scrum Process Scrum Phases Measurements Key Practices Backlogs Sprint.
BUDGET 4Distribution of budget per phases of the project; 4Itemization of budget; 4Division of budget per source of contribution; 4Division of budget between:
1. WELCOME Project Management Cycle (P.M.C.) What is a project? : What is project management?: Project management life cycle : Phase 1 st : Phase 2 nd.
Forming a Strategy for your Business.
Problem Solving Sheet Guidelines
ROLE of a BLACK BELT CANDIDATE
Engineering Processes
Guidance notes for Project Manager
The Two Most Common Types of Contemporary Planning Techniques
Plan the implementation of change
Fundamental Test Process
Unit 09 – LO3 - Be able to Implement and Test Products
CATHCA National Conference 2018
FUNCTION OF MANAGEMENT
Portfolio, Programme and Project
Management By Objective – Dashboard Management
The Two Most Common Types of Contemporary Planning Techniques
Presentation transcript:

FI - 28 June FI - Focus Improvement system Step 0 Team Charter Step 1 Mapping the current process Step 2 Identify defects Step 2 5 Why Analysis Step 2 Agreeing the action plan Step 3 Mapping the desired Process Step 4 Action completion Step 5 Identify training needs Step 5 Mapping the finished process

FI - 28 June What is this?  What is an FI?  What can it do?  What can it offer me?

FI - 28 June FI – In the spotlight What is an FI?What is an FI?  A FI is a systematic way of looking at a work process. What can it do?What can it do?  A FI gives a structured method of making improvements to a current work process. What can it offer me?What can it offer me?  A FI can offer cost reductions, more efficient work processes, waste elimination and healthier results.

FI - 28 June How does it work?  The FI system is a series of steps, methodically placed to form a logical path to Process Improvement success.  Each step will define a critical part of the FI system, and is completed in order.  Each step has tools to guide you in the facilitation of the system.  A weekly meeting is set up to discuss and review the progress of the FI.  Below is a representation of how all the steps fit together in the system. Step 0 Team Charter Step 1 Mapping the current process Step 2 Identify defects Step 2 5 Why Analysis Step 2 Agreeing the action plan Step 3 Mapping the desired Process Step 4 Action completion Step 5 Identify training needs Step 5 Mapping the finished process

FI - 28 June The importance of a weekly meeting.  A weekly meeting should be set up between the agreed FI team at a time that everybody can achieve.  The importance of the meeting is such that it will keep the momentum of the FI going.  The weekly meeting will be the forum for discussion, review, and goal settings for each step.

FI - 28 June What tools are available?  A FI system check step is used to track the progress of each step as it is worked and finally completed.  Step 0 – A Team Charter is included which allows you to build the structure of the FI team, set the expectations, guidelines, agree on success criteria and which external resources you need to complete the task.  Step 2 – Includes 3 tools to help you to identify and categorise the defects in the current system. How to drill down to the root cause of the defect. What action plan is required and who will own it for each defect.

FI - 28 June How does each step work?  Each step is a unique part of the FI system.  Each step channels the team to focus on a specific area of the process to be improved.  The steps are systematic, and easy to follow to a logical conclusion.

FI - 28 June Step - 0  Building the Team

FI - 28 June Team Charter The Team Charter is your building blocks of the FI team, it is a working document that will change throughout the FI as certain doors are opened whilst others are closed. Time should be spent preparing the Team Charter as this will Guide the FI towards its goals and measures.

FI - 28 June Key Points to creating an effective Team Charter

FI - 28 June Step - 1  Mapping the current Process

FI - 28 June Process Mapping  The aim of this step is to get a detailed flow map of how the current process works.  This must be an exact replication of what is happening now, warts and all.  Include any timed functions, detail how long they take.  Detail any costs incurred in the process.  Detail the manpower required to fulfil certain aspects of the process.  Detail any points within the process where information needs to be obtained to proceed. Detail any time lag in obtaining the information.

FI - 28 June An example of a simple Process Flow map for baking a cake

FI - 28 June Step – 2  Identifying the defects.  Identifying the root cause.  Identifying the Actions.

FI - 28 June Identifying the Defects. Step 2, Stage 1 One of the tools is a defect list, this will help you categorise the type of defect present in the system. There are five categories. 1. ProcessThis defect is a part of the process that is simply not efficient, for whatever reason. 2. InformationThis defect is caused by, lack of, incorrect, insufficient, delay in receiving/giving of information either into the process or as a result from the process. 3. EnvironmentalThis defect is caused by constraints in the process that are not linked to the inefficiencies in the process, ie..(Total pallet holding in the warehouse). 4. BehaviouralThe defect identifies a manpower behaviour issue. 5. SBux MandateThis defect is caused by a mandatory requirement from Starbucks which effects the operation of the process. The FI team will debate and agree on which designations to assign the defects to, this will form the basis of the next stage of Step 2, Why – Why analysis.

FI - 28 June Identifying the Root Cause. Step 2, Stage 2 Why – Why Analysis. The theory behind why – why analysis is that asking why 5 times should lead you to the base root cause of any issue. How does it work in conjunction with the defect list? Each defect is numbered so that its progress through the FI can be tracked, also so when the FI is completed people looking back at it can see how any specific defect was solved. The FI team agree the top level root cause for each defect. Each level is reviewed and questioned, this will assign the next level, so on and so forth until you cannot question any further. This is the base level root cause. The base level root cause forms the Action for the next stage of step 2.

FI - 28 June Identifying the Actions. Step 2, Stage 3 Action planning and Owner assigning. Your FI actions will have been assigned from stage 2. These will be the base level root cause for each of the defects. The FI team will agree an owner for each action, this would usually be the person(s) whose area of duty within the process is affected by this action. The FI team will agree if any resources are needed to complete the actions. The FI team will agree a time frame for completion of the action.

FI - 28 June Step - 3  Mapping the desired process.

FI - 28 June The Ideal process During this step the FI team will map the desired process. This will be the process that will come about once all present actions have been completed in full. Whilst performing this action you may identify defects within this process that were not thought of during the initial process appraisal.(Upon this, further investigation in Step 2 must be made to establish, Defect, Why-Why, and Action plan.) (The Ideal process may or may not form the actual finished process configured from the FI investigation.)

FI - 28 June Step - 4  Action completion.

FI - 28 June Action completion.  There will be some actions that will not be able to be completed for what ever reason.  Upon discovery of these an alternative action will be agreed and assigned by the FI team.  This new action will then be completed by the relevant owner.  During the weekly meetings action completion will be reviewed.

FI - 28 June Step - 5  Mapping the finished process.  Identifying training needs.  Setting review measures and targets.  Agreeing an Audit review period.

FI - 28 June Mapping the finished process.  Once all actions and alternative actions have been completed the improved finished process can now be mapped.  The FI process is now nearing it’s closure.

FI - 28 June Identifying training needs.  The new improved process will invariably need some people to be trained in some of the improved areas.  The FI team should agree on the training needed, and set up a training matrix to ensure the completion of the training.  The training should wherever possible be ‘on the job’.  The training matrix should be reviewed at every FI audit to ensure that all users of the process are trained in the process.  All new employees moved into the process should be included in the training matrix and the appropriate training given.

FI - 28 June Setting review measures and targets.  The FI team will set the output measure goals as agreed in the Team Charter.  The FI team will set the In-Process measures goals as agreed in the Team Charter.  The FI team will agree a success time line and review the results after this period.  Any failures in the process after this review period can be tweaked.

FI - 28 June Agreeing an Audit review period  The audit review is not the same as the success time line review.  The audit will not only be reviewing the results, but will also review the steps in the process and the compliance of the people to adherence of the steps.  The audit will be carried out by an Original FI team member plus another non FI member to ensure an unbiased review.  Upon the results of the review will be determined the need to re-address the process in its entirety or part.