Class 5: Chapter 3S Process Mapping 7 Analysis Class 5 Plan Roster feedback News of Note Chapter 3 Key Terms An Overview of Chapter 3S –Learning objectives.

Slides:



Advertisements
Similar presentations
Internal Assessment Your overall IB mark (the one sent to universities after the IB test) in any IB science course is based upon two kinds of assessments.
Advertisements

Copyright © 2014 McGraw-Hill Higher Education. All rights reserved. CHAPTER 3 SUPPLEMENT Process Mapping and Analysis McGraw-Hill/Irwin.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
Process Mapping. Why Flow Chart? To understand a process or system To (visually) depict all key steps in a process or system To compare existing and ‘ideal’
Overview: Plan-Do-Check-Act Cycle.
Attribution of Haze Phase 2 and Technical Support System Project Update AoH Meeting – San Francisco, CA September 14/15, 2005 Joe Adlhoch - Air Resource.
Chapter 15 Application of Computer Simulation and Modeling.
Planning and Strategic Management
Copyright © 2011 Pearson Education, Inc. Publishing as Prentice Hall Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall.
Chapter 9 Describing Process Specifications and Structured Decisions
Chapter 9 Describing Process Specifications and Structured Decisions Systems Analysis and Design Kendall & Kendall Sixth Edition © 2005 Pearson Prentice.
Chapter 9 Describing Process Specifications and Structured Decisions
1 Process Mapping BA 339 Mellie Pullman. 2 Objectives Service Process Differences Little’s Law Process Analysis & Mapping.
Effective systems development requires a team effort from stakeholders, users, managers, systems development specialists, and various support personnel,
© 2005 Prentice Hall3-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Fundamentals of Information Systems, Second Edition
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
ACCESS – CHAPTER 4 ZNANATEJ PANGA October 27, 2014.
IT Project Management, Third Edition Chapter 11 Chapter 1: Introduction to Project Management.
Chapter 6, Process-Flow Analysis
Chapter 13: Designing the User Interface
1 Value Stream Mapping Sustainable Operations Professor Mellie Pullman.
Barry Murash MBBit Nortel 2007
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall 9 Kendall & Kendall Systems Analysis and Design, 9e Process Specifications.
Delmar Learning Copyright © 2003 Delmar Learning, a Thomson Learning company Nursing Leadership & Management Patricia Kelly-Heidenthal
Operations and Supply Chain Strategy
Program Participants: Department Managers, Project Leaders, Senior officers, Black Belt candidates and anyone who desires an understanding of Lean Six.
Team Skill 1 Analyzing the Problem Business Modeling (6) 1.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
Day 3: Rubrics as an Assessment Tool. "There are only two good reasons to ask questions in class: to cause thinking and to provide information for the.
Data and Process Modeling
Auditor's report Document prepared by the auditors appointed to examine and certify the accounting records and financial position of a firm. It must be.
Striving for Quality Using continuous improvement strategies to increase program quality, implementation fidelity and durability Steve Goodman Director.
Chapter 9 Describing Process Specifications and Structured Decisions
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Strategic Planning Document – Confidential and Proprietary – Preliminary Draft – For Discussion Purposes Only. The opinions, interpretations, and conclusions.
Business Analysis and Essential Competencies
PowerPoint Presentation by Charlie Cook The University of West Alabama Copyright © 2005 Prentice Hall, Inc. All rights reserved. Operations Management.
Z26 Project Management Introduction lecture 1 13 th January 2005
Requirements Engineering CSE-305 Requirements Engineering Process Tasks Lecture-5.
Describing Process Specifications and Structured Decisions Systems Analysis and Design, 7e Kendall & Kendall 9 © 2008 Pearson Prentice Hall.
5 1 Chapter 5 Normalization of Database Tables Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
A simple performance measurement framework A good performance measurement framework will focus on the customer and measure the right things. Performance.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 3 Identification and Selection of Development Projects.
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
BISM 8470 Issues in IRM Topic: Software Project Management.
STAKEHOLDER MEETING Selecting Interventions to Improve Utilization of the IUD City, Country Date Insert MOH logoInsert Project logoInsert USAID logo (Note:
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.
Value Stream Mapping at NCS Presented to: Gunnison Date: 4/2/2014.
McGraw-Hill/Irwin Copyright © 2011 by the McGraw-Hill Companies, Inc. All rights reserved.
PROJECT NAME EMPIRE BELT(S) Month Day, Year. 2 Agenda Lean Overview Introduction to the Project & Team The Process Next Steps.
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System A Use Case Primer Organizing.
1 Text Layout Introduction (1-4) Team Skill 1 – Analyzing the problem (5-7) Team Skill 2 – Understanding User and Stakeholder Needs (8-13) Team Skill 3.
Module 4: Systems Development Chapter 13: Investigation and Analysis.
Chapter 16 Managing costs and quality
Some of these slides were excerpted from: Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey A. Hoffer.
IT-465 Introduction to Lean part Two. IT-465 Lean Manufacturing2 Introduction Waste Walks and Spaghetti Charts Outcomes Understand what a waste walk is.
Chapter 3 – The Process Approach 1 Process Approach Auditing 14-April-2009 QUESTIONS FOR USE DURING YOUR PROCESS AUDITS.
Copyright © 2011 Pearson Education Process Specifications and Structured Decisions Systems Analysis and Design, 8e Kendall & Kendall Global Edition 9.
Canberra Chapter July PMI Chapter Meeting July 2007 PMCDF Competence Framework A presentation by Chris Cartwright.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
A Quick Review of the Components THE DMAIC CYCLE.
LEAN SIX SIGMA PROJECT TEMPLATE
Elaboration & Negotiation Process
REQUIREMENTS ANALYSIS
LEAN SIX SIGMA PROJECT TEMPLATE
LEAN SIX SIGMA PROJECT TEMPLATE
Chapter 11 Describing Process Specifications and Structured Decisions
Presentation transcript:

Class 5: Chapter 3S Process Mapping 7 Analysis Class 5 Plan Roster feedback News of Note Chapter 3 Key Terms An Overview of Chapter 3S –Learning objectives

News of Note The need for precision Obama has a Kenyan Post-Colonial view Moslem confusion New threat—natural gas New Products Rick Rescorla—9-11 Hero –Plus the hundreds of first –Responders who gave theirl lives, –Note that many Korans were destroyed in prayer rooms at the WTC and the Pentagon.

1.Work through various process mapping steps 2.Assess processes 3.Determine type of activity a processes represents 4.Understand when and how to apply process mapping tools 5.Change a process for increased productivity 3S–3 Learning Objectives

“Process” of Process Mapping 1.Determine desired process outcomes and metrics 2.Identify and bound the critical process 3.Document the existing process (“current state” map)—much will be learned 4.Analyze process and priorities improvements 5.Recommend changes (“future state” map) 6.Implement changes and monitor process 3S–4

1. Identify Desired Outcomes What should the process achieve? –Reduced cost –Shorter lead time –Improved quality—what aspect of quality –More reliable deliveries –Other? 3S–5

2. Identify and Bound Critical Process Critical processes typically are one of the following: 1.A bottleneck 2.Visible to the customer 3.Consumes largest amount of resources 4.A shared process—can we make changes? 5.Highest level of variance 6.A unique skill or core competency 7.Point of problems/issues to the firm 3S–6

3. “Current State” Map Current State: the ‘as is’ of the processes A process map is a diagram of the process activities 3S–7

3. “Current State” Map Identify minimum acceptable level of detail on map Use display formats as need to depict complete processes Watch for ‘hidden’ steps Capture relevant data 3S–8

3. “Current State” Map Process Flow Table: record of process activities, key attributes and sequence 3S–9

Table 3S - 2 3S–10

3. “Current State” Map Physical Layout Diagram: documents horizontal and vertical movements 3S–11 Figure 3S-2

4. Analyze and Improve Value Adding Activity: moves a item closer to the form or location desired by customer Necessary but not Value Add: needed but doesn’t directly add value Waste Generating: consumes resources without adding value Question Mark Activity: not easily categorized, keep asking “why?” to get to root reason for these activities 3S–12

4. Analyze and Improve Disposing: what should be done with a specific activity –Keep: leave intact –Combine: merge an activity with others that are similar –Rethink: modify to improve value add –Eliminate: appropriate for waste activities Repositioning: where to position an activity in the overall process 3S–13

5. “Future State” Map Prioritize identified process improvements: 1.Make change immediately 2.Postpone change pending resources 3.Determine if change is not desirable or feasible 3S–14

6. Implement and Monitor Improvements Process Improvement is often iterative, and may require trial and error Significant changes require careful monitoring and stakeholder support 3S–15

Process Mapping and Analysis Summary 1.Process mapping and analysis is a multi-stage process 2.Processes can be characterized into six basic activities 3.Multiple tools, including graphs, help to document the ‘current state’ and ‘future state’ of processes 3S–16

Key Chapter 3S Terms Tools –Process flow diagrams& tables –Value stream mapping –Service blueprinting—line of visibility Actions –Combine –Dispose –Eliminate wasteful activities –Note that it is a value adding activity –Note that is necessary but not value adding –Reposition and/or rethink