developing a project plan

48
Basic Principles of Project Management RLDC 1 Barry Cordero SHPE National VP Principal Project Engineer, Medtronic Inc. Master Black Belt: Lean Six Sigma

Upload: barrycordero

Post on 13-Nov-2014

512 views

Category:

Documents


2 download

DESCRIPTION

Short overview of how to identify a problem, gather buy-in, develop consensus and plan a meaningful project... too short for the amount of material... Much leveraged from LEI

TRANSCRIPT

Page 1: Developing a Project Plan

Basic Principles of Project Management

RLDC 1Barry CorderoSHPE National VP

Principal Project Engineer, Medtronic Inc.Master Black Belt: Lean Six Sigma

Page 2: Developing a Project Plan

“It takes as much energy to wish as it does to plan”

Eleanor Roosevelt

Page 3: Developing a Project Plan

Project Management

• Goals/Obj• Tasks/Owners• Resources• Deadlines

Plan

• Manage Critical Path

• Solve Problems• Adjust Plan• Phase Reviews

Execute • Control Plan

• Schedule

Control

Page 4: Developing a Project Plan

Importance of Planning

Page 5: Developing a Project Plan

The Project Planning Cycle

Background

Current State

GoalFuture State

Plan of Action

Page 6: Developing a Project Plan

Other Project Cycles

Define

Measure

Analyze

Improve

Control

Plan

Do

Check

ActLeanSix - Sigma TPS

Page 7: Developing a Project Plan

Essential Components of Planning

GoalObjectives

SMART

TasksSpecific itemsOwnersDeadlinesResources

Background

Current State

GoalFuture State

Plan of Action

Page 8: Developing a Project Plan

DEFINING THE PROBLEM(BACKGROUND AND CURRENT STATE)

Page 9: Developing a Project Plan

9

PM RoleIs the role of the PM to describe your ideas and plan in order…

-- to convince?

-- or to engage?

Convince means to “sell” or “get buy in”

Engage means to “become part of”-- to invite to take part in the thinking-- and the experiment based on it

Page 10: Developing a Project Plan

What is our natural tendency?

Perception of a

Problem

The SOLUTIO

N

Impressions &

AssumptionsTheoryFACTS

BLACK

HOLE

Page 11: Developing a Project Plan

How can we be more effective?Ask questions to help ourselves see:

What is Actually Happening?What do I actually know?

11

The Real or

Main Problem

A SOLUTIO

N

Impressions &

Assumptions

Theory

FACTS

FACTS

FACTS

FACTS

Page 12: Developing a Project Plan

3 Common Mistakes in Problem Solving1. Assuming you know what the

problem is without seeing what is actually happening.

2. Assuming you know how to fix a problem without finding out what is causing it.

3. Assuming you know what is causing the problem without confirming it.

In other words - Not Grasping the Situation.

(And where do we grasp the situation? At the gemba!)

12

Page 13: Developing a Project Plan

Maintain a Questioning Mind

• What do you actually know? How do you know it?

• What do you need to know? How can you learn it?

13

• Avoid acting on assumptions or jumping to conclusions.

Page 14: Developing a Project Plan

Keys to a good problem statement

Purely a problemExplains why problem is relevant to business/chapterDoes not include a solution

Avoid “lack of” statements

Avoids assumptionsCan be visual

Page 15: Developing a Project Plan

Example Bad Problem Statements

“lack of professional development opportunities causes low member retention”“Company x minority representation is poor.”“process z yield is low due to inattention to detail by process inspectors”

Page 16: Developing a Project Plan

Example Good Problem Statements

“member retention is very low, minimizing the strength of networking and the ability to develop chapter leaders”“technical Hispanics at company x stay for an average of 3 years. This attributes to low Hispanic representation at all levels in the company.”“process z yield has dropped from 98% to 92% over the past year, resulting in increased cost of goods and additional labor”

Page 17: Developing a Project Plan

CLASS EXAMPLE

Page 18: Developing a Project Plan

EXERCISE: WRITE A PROBLEM STATEMENT

Page 19: Developing a Project Plan

Writing your A3: BackgroundWhy are you solving this problem?

Why is this problem important? How is it contributing to the company’s need?

Keep it simple

Page 20: Developing a Project Plan

DESCRIBING CURRENT STATE

Page 21: Developing a Project Plan

Describe your Current State/Gap

Be visual Show process map Show graphs Show charts

Page 22: Developing a Project Plan

“A Problem Clearly Defined Is Half Solved”

What do we mean by “clearly defined”?

• Gap between what is actually happening (current condition) and what should/needs to be happening described in performance terms.

• Gap broken down to concrete, observable conditions (smaller problems in the gap or in the related work processes) that are contributing to the Gap & can be investigated first hand?

22

Page 23: Developing a Project Plan

23

CausedGAP

Created

GAP

A GAP: 2 types of Gaps

Page 24: Developing a Project Plan

SWOT Analysis

Provides clarity as a boardProvides opportunity to reach out to your stakeholdersDrives your strategic planProvides platform for goal making

Page 25: Developing a Project Plan

SWOT Analysis  Strengths Weaknesses

Internal

Factors

- Strong relationships with…..- Large membership base- Tradition of….- Only engineering society for Latinos

- Small Budget- Unknown Academic….- Programs are inconsistent

  Opportunities Threats

External

Factors

- Neighboring town X has high Hispanic population

- Company X,Y,Z has shown interest in chapter programs

- Partnership interest from NSBE chapter locally

-   

- Current sponsorships teetering- Economic environment- Programs are inconsistent  

Page 26: Developing a Project Plan

Example

Page 27: Developing a Project Plan

SHOW EXAMPLEEXERCISE: DEFINE YOUR OWN CURRENT STATE

Page 28: Developing a Project Plan

Writing your A3: Current Conditions

Describe the current situation vs the desired situation and quantify the gap

Page 29: Developing a Project Plan

SETTING MEASUREABLE GOALS

Page 30: Developing a Project Plan

Write your Goal/TargetConsider SMART

SpecificMeasurable

• Numbers oriented, can tell if you achieved it

Attainable• Within you or your team’s scope of influence

Relevant• Related to the problem statement or gap

Timely• If you are ready, assign a date to it (by when?)

Avoid words like “Create, Implement, Develop”

Goals/Targets

What specific outcomes are required to close the gap?

What is the target condition?

Is your goal S.M.A.R.T?

Page 31: Developing a Project Plan

Goal/Target

IS

SMARTAddresses a problem in performance“Will prevent the bearing from wearing out too frequently”

Stated as SMART as possible“Increase performance from 50 hours to 300 hours without wear 100% of the time”

Is NOT

Restating your solution“Workers will oil the machine daily”

A statement of a possible countermeasure“Implement standard work”“Implement Robust Design”

Page 32: Developing a Project Plan

EXERCISE: WRITE A GOAL STATEMENT

Page 33: Developing a Project Plan

ANALYZE THE PROBLEM

Page 34: Developing a Project Plan

34

Page 35: Developing a Project Plan

Choosing the right Analysis ToolWhat tool might you choose for:

Quality issue?

Delivery Issue?

Productivity Issue?Cost Issue?

Consider:

– SPC, Pareto, Six Sigma project guide

– VSM, Process Map, Flow Chart, PFM, SOE, Lean Project Guide

– Balance chart, pareto

– Pie chart, fishbone, swim lane

Page 36: Developing a Project Plan

AnalyzeTechnical Problems

Perform hypothesis testingDo experimentsCollect dataDetermine root cause

Business ProblemsRoot cause analysisShare with stakeholders

Page 37: Developing a Project Plan

COUNTERMEASURES

Page 38: Developing a Project Plan

Problems and Solutions and Countermeasures

The Solution?

To solve = to find the answer…..the One correct answer

A Countermeasure?

To resolve = to find and try out an action that seems likely to reduce the problem condition (the GAP)• A temporary measure “fixes” a problem by blocking or

working around its impact• A permanent countermeasure eliminates a problem by

removing its cause 38

Page 39: Developing a Project Plan

What to look for in Recommendations for Countermeasures

1. Do I see the link between your proposed countermeasures and the causes they are intended to address?

2. Do I feel you have considered all the options for addressing the causes?

3. Do your recommended countermeasures make sense as the way to address the causes and resolve the problem?

4. Am I confident these countermeasures will accomplish your goals and achieve your purpose for addressing the problem?

39

Page 40: Developing a Project Plan

Countermeasure Evaluation

Page 41: Developing a Project Plan

COUNTERMEASURES TO PROJECT PLANS

Page 42: Developing a Project Plan

Drive backward: Networking Diagram

Each completed countermeasure as a milestoneUse mind mapping to determine predecessors to completed milestonesBuild dependenciesAdd in dates and task owners

Page 43: Developing a Project Plan

Networking Diagram: Example

Professional Development

Workshops Monthly

Develop Program

Survey Members on needs

Place Bids

Acquire Location Survey members for free locations

Page 44: Developing a Project Plan

Convert to Project Plan

Use MS Project if you wantOr use Excel

Page 45: Developing a Project Plan

Excel ExampleDates: June 1-7 June 8-17 June 15-21 June 22-28 Jun29-Jul5 Jul 6-13

DEFINEAgree on charterGather more VOCDefine Phase ReviewEnter project in QTRAK

MEASUREDevelop Project StrategyMSABaseline CapabilityProcess Map / VSMFishbone (C&E Diagram)C&E MatrixXIAData Collection PlanCollect dataUpdate Charter, if neededOptional M Phase Rev.

ANALYZEAnalysis planVerify Key X'sFinalize CharterAnalyze Phase Rev.

IMPROVEDefine ImprovementsOptimize ImprovementsImplement ImprovementsOptional I Phase Rev.

CONTROLDevelop Control PlanProcess Owner sign-offFinal capabilityFinal ReviewClose project in QTRAK

Page 46: Developing a Project Plan

The Plan In Place

Half of work should be done

Now it’s time to manage

Page 47: Developing a Project Plan

Thank You

Questions?

[email protected]

Page 48: Developing a Project Plan

References

Lean Enterprise Institute“Managing to Learn” John Shook

Project Management Book of Knowledge (loosely)