pmi powerpoint template maximum 2 lines, arial 28pt bold · houston, tx, usa | 5–8 november 2017...

26
HOUSTON, TX, USA | 58 NOVEMBER 2017 #PMOSym PMO17BR404 Lessons Observed, Lessons Learned or Lessons Used? Wayne Kremling, PMP, Sr. Project Manager Boeing

Upload: doankhue

Post on 20-Apr-2018

220 views

Category:

Documents


6 download

TRANSCRIPT

HOUSTON, TX, USA | 5–8 NOVEMBER 2017

#PMOSym

PMO17BR404

Lessons Observed, Lessons Learned or Lessons Used?

Wayne Kremling, PMP, Sr. Project Manager

Boeing

Copyright © 2014 Boeing. All rights reserved.

Education

BA Business Management

– Western Washington University

Credentials

GWU Certified Project Manager

Stanford Certified Project Manager

Project Management Professional (PMP)® certified in 2005

Work History

Boeing – Since 1985

Inventory Analyst

Buyer – BCA Systems and Equipment, Engines

Program Manager – BCA Propulsion Systems Division

IT Project Manager

Project Manager – 777 Baseline Management

Lead Project Manager – BCA Electrical Tech Center

For Fun

Leader of the Boeing Project Management Community of Excellence PMP® Exam Prep

Family

See next page

Instructor – Wayne Kremling, PMP

Copyright © 2014 Boeing. All rights reserved.

Life-Long Project

3

Wayne

Bryn

22 yrs

20 yrs

Court

-ship

10 wks

Engage-

ment

6 mos

Marriage

35 yrs and counting

Lauryn

Cyd

32 yrs and counting

28 yrs and counting

Start

1959

Finish

Chachi

Lenaborn 5/10/13

MarriageEngage-

ment

Heidiborn 2/22/16

Retire-

ment

Josiah

Engage-

mentMarriage

Copyright © 2014 Boeing. All rights reserved.

PMI®, PMP® and PMBOK® Guide are registered marks of Project

Management Institute, Inc.

Project Management Institute A Guide to the Project Management Body of

Knowledge (PMBOK® Guide) – Fifth Edition, Project Management

Institute, Inc., 2013. Copyright and all rights reserved.

Copyright Disclosure

4

Copyright © 2014 Boeing. All rights reserved.

Gain knowledge on the sources of lessons

Understand how to leverage the lessons to take advantage of their value

Understand methods of capturing and sharing lessons across an organization

Learning Objectives

5

Copyright © 2014 Boeing. All rights reserved.

This presentation introduces, at an overview level, ways

to get value from lessons learned in projects by

replicating those lessons throughout an organization.

Purpose of the Presentation

6

Copyright © 2014 Boeing. All rights reserved.

Feel Free to Raise Your Hand

At Any Time

Questions?

7

Copyright © 2014 Boeing. All rights reserved.

From Wikipedia…

“Lessons Learned is the sixth studio album released by country music artist Tracy

Lawrence. It was also his last album for Atlantic Records before the closure of Atlantic's

Nashville division in 2000. This album produced three singles for Lawrence between 2000

and 2001: the title track, ‘Lonely’, and ‘Unforgiven’, which peaked at #3, #18, and #35,

respectively, on the Billboard country singles charts. ‘Lessons Learned’ was also Lawrence's

first Top Ten country hit since ‘How a Cowgirl Says Goodbye’ in 1997.”2

What Is a Lesson Learned?

8

Copyright © 2014 Boeing. All rights reserved.

PMBOK® Guide…

“Lessons Learned. The knowledge gained during a project which shows how

project events were addressed or should be addressed in the future with the

purpose of improving future performance.”3

Boeing

A lesson learned is compilation of knowledge gained by experience, observation

or insight that includes a description of the situation that drove it, the outcome

and any pertinent recommendations that may improve future company

performance…

What Is a Lesson Learned?

9

Copyright © 2014 Boeing. All rights reserved.

“Purpose”

We need to focus on the purpose of everything we do

Start all meetings with: “The purpose of this meeting is to…”

Ask the question: “How does this satisfy the purpose?”

Make sure your WBS and activities satisfy the purpose of the project

Key Word

10

TIP

Copyright © 2014 Boeing. All rights reserved.

Stop calling it a Lessons Learned Review

Get away from the passive wording

“After Action Review” tells you in the name there is action

AARs:

Have a process to follow, they aren’t random discussions

At the end you have actions to take, when they are followed and re-

used, you have value

LessonsLearnedReview

11

After Action Review

Copyright © 2014 Boeing. All rights reserved.

In a recent LinkedIn survey…

A lot of ad hoc use of lessons learned

A lot of “this is what should be done…”

Only three out of 32 replies actually said they have an organizational

process

What Others Are Doing – Organizationally

12

Copyright © 2014 Boeing. All rights reserved.

In a recent inSite survey…

…what I'm looking for is an actual documented process for how your

organization conducts lessons learned that can be tailored to use any

template or repository

The first couple responses were similar to the LinkedIn responses

Then…

Through inSite at Boeing

13

paydirt!

Copyright © 2014 Boeing. All rights reserved.

“The Common Bomber Process to Collect and Document Lessons Learned” – uses ClearQuest as a repository

“Defining and Applying Airplane Safety Lessons Learned”

“Documenting Engineering Lessons Learned”

“After Action Review Process”

“Capture and Incorporate BT&E Lessons Learned” – Uses the enterprise Lessons Learned wiki as a repository

Alan Vaughan provided the Enterprise process designed around using the Enterprise Lessons Learned wiki

inSite Results

14

Copyright © 2014 Boeing. All rights reserved.

“Many enterprises may have good data, but because they are

working in silos . . . these data are not available to end users

when they require it.”

“Enabling change on an enterprise scale requires buy-in from a

wide range of staff, from directors to operational delivery teams.”

“The main effort is understanding and articulating the benefits

and cultural change required and making the change happen.”

Learning to Share – Ed Wallington4

Project Leadership, Lessons from 40 PPM Experts on Making the Transition from Project

Management to Project Leadership

15

Copyright © 2014 Boeing. All rights reserved.

Enterprise Lessons Learned Process

Defines a standard enterprise lessons learned process that promotes the

seeking, contributing, reuse and implementation of lessons learned at the

enterprise level

Makes use of the Enterprise Lessons Learned wiki

Lesson Learned Criteria:

Has impact on cost, performance or schedule

Is factual and technically correct

Identifies a specific design, process, decision, or includes as much information

as is available that addresses the cost, performance or schedule impacts

At Boeing

16

Copyright © 2014 Boeing. All rights reserved.

Example Process Flow

17

Team Member

Team Member

Team Member

Copyright © 2014 Boeing. All rights reserved.

Things to consider

Retrievable by the masses

Categorize – Organization/Product/Project Type/Phase

Searchable

How to use

Project teams need to discuss the lessons

Take actions on the lessons – update processes, templates, etc…

Require projects to review before planning a project or phase

Lessons Learned Gathering, Use, Storage and Retrieval

18

Copyright © 2014 Boeing. All rights reserved.

AARs are detailed reviews with specific questions

Defines your organization’s lessons learned process at the

organizational level

Should be held after each major project event/gate/phase

Evaluates the project’s successes and failures

Provides specific actions that need to be completed

Drives process change/improvement

May take multiple sessions

After Action Reviews

19

Copyright © 2014 Boeing. All rights reserved.

High-Level Process Flow

20

1.0 – Plan Out AAR – Determine necessary participants and schedule the session(s)

2.0 – Conduct AAR – Hold the AAR meeting(s) following the ground rules in this process

3.0 – Follow-up actions

4.0 – Close-out actions

1.0 – Plan Out

AAR 4.0 – Close Out

Actions

2.0 – Conduct

AAR

Execute & ControlPlan Close

3.0 – Follow Up

Actions

Copyright © 2014 Boeing. All rights reserved.

PM/F

PARTICIPANTS

2.0 Conduct AAR – Detailed

21

Return to Table of Contents

2.1 –Introduction

2.2 – What was

supposed to happen?

2.3 –What did happen?

2.4 –Why did events

happen?

2.6 –Summarize and Record

2.5 –How to improve

?

Execute & Control ClosePlan

3.0 – Follow Up

Actions

2.0 – Conduct

AAR

4.0 – Close Out

Actions

1.0 – Plan Out

AAR

Copyright © 2014 Boeing. All rights reserved.

Ground Rules

22

Copyright © 2014 Boeing. All rights reserved.

Template

23

Project Name: -

# Cat. Name What did we set out to

do?

What actually

happened?

What should we do

differently next time?

What do we want to

repeat next time?

Action Assigned To

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

Copyright © 2014 Boeing. All rights reserved.

Hope is a good thing to have in our lives

Hope has no context in a project plan

Do not use “Hope” when reporting on project status

Speak with confidence and strength as a project manager

Using the word “Hope” in a status report tells the audience that you

don’t have confidence in your plan and processes

“Hope”

24

TIP

Copyright © 2014 Boeing. All rights reserved.

Questions?

25

Copyright © 2014 Boeing. All rights reserved.

1. Ilene W. Jones, PMP® Study Group Student, class of 2013

2. Wikipedia - http://en.wikipedia.org/wiki/Lessons_Learned

3. A Guide to the Project Management Body of Knowledge

(PMBOK® Guide) – Fifth Edition, pg 544

4. Ed Wallington quoted in Project Leadership, Lessons from

40 PPM Experts on Making the Transition from Project

Management to Project Leadership, David Rogelberg,

editor; pg 9.

References

26