Project%20Recovery%20in%2048%20Hours%20An%20Application%20of%20TOC

1

JVG Consulting Inc. Value Based Consulting
Guaranteed ROI
Project Recovery in 48 HoursAn Application of
TOC John Gardner, CMC Managing Partner
2
Introduction

• John Gardner, CMC
• Managing Partner, JVG Consulting Inc.
• Practice Leader, Deloitte
• Interim CIO Economical Insurance
• Assistant Director, PriceWaterhouseCoopers
• Assistant Director, DMR Consulting Group

3
Agenda

• Background Context
• Premise
• Overview
• Diagnostic Maps
• Feature Cases
• Measurements
• Breakout Session Goal Map
• Breakout Session Problem Map
• Breakout Session Feature Case Map
• Breakout Session Sizing
• Breakout Session Action Plan

4
Background Context

• 85 of Projects are
• Late
• Over-budget
• Ship with reduced functionality
• Defect Rates are 53 with
• 11 Severity 1
• 14 Severity 2

5
Premise

• Your project is in crisis
• Management wants to save it
• You are prepared to change

6
Overview

• TOC is a method that integrates several
  disciplines into a holistic, unified framework
• TOC simplifies and extends the Theory of
  Constraints with Statistical Process Control,
  Object Oriented Analysis, Function Point Analysis
  and Agile methods
• TOC implements a set of key measurements that
  significantly improves management control

7
Overview Continued
Theory of Constraints (TOC) 30 years
Object Oriented Analysis (OOA) 30 years
Function Point Analysis (FPA) 30 years
Statistical Process Control (SPC) 80 years
Agile (Scrum/FDD) 10 years
8
Overview Continued

• TOC applies the following steps for a Project
  Turnaround
• Identify the Project Goal and Conditions
• Identify the Undesired Effects (UDE)
• Identify the Necessary Conditions (NC) for each
  UDE (3 5) x 5 Why
• Identify the Core Problems (3 5)
• Identify Feature Cases (5 7) x 5 Why
• Size the Change
• Create Action Plan
• Execute

9
Diagnostic Maps

• One or more types of maps may be created during a
  TOC engagement
• Situation Map
• Goal Map
• Problem Map
• Conflict Map
• Solution Map
• Feature Case Map

10
Feature Cases

• An extension to traditional business use cases
  and system uses
• Feature cases are truly object oriented
• Feature cases document process and data
• Feature case descriptions are rigorous
• Feature cases can be used as a development
  specification

11
Measurements

• Only a handful of key measurements are required
  to implement full management control on a
  project
• ROI, T, I, OE
• Size, Demand, Capacity, WIP, DIP and RIP
• Delivery Rate (DR)

12
Breakout Session Goal Map

• Review the Case Study
• Identify the Goals
• Identify the Necessary Conditions
• Build the Goal Map
• 10 minutes

13
Breakout Session Problem Map

• Review the Case Study
• Identify the UDEs
• Identify the Necessary Conditions
• Build the Problem Map
• 10 minutes
• Discussion about Conflict Maps

14
Breakout Session Feature Case Map

• Review the Case Study
• Identify the Feature Cases
• Business
• Technical / System
• Build the Feature Case Map
• 10 minutes
• Discussion about Feature Cases

15
Breakout Session Sizing

• Review the Case Study
• Review the Feature Case Map
• Perform the Feature Count
• 10 minutes
• Discussion about Measurements

16
Breakout Session Action Plan

• Review the Case Study
• Review all Maps
• Group and sort Feature Cases by Value
• Build Action Plan Monthly Delivery
• 10 minutes
• Discussion

17
A Standing Offer

• Project Intervention
• Establish Goal Problem Maps
• Resolve Conflicts
• Create Action Plan
• Service provides guaranteed ROI

18
Contact Information

• John Gardner, CMC
• Managing Partner
• JVG Consulting Inc.
• John.Gardner_at_jvgconsulting.ca
• 905-933-7607