pdd 2016 lee peters - lessons from a jedi schedule

15
1 Lessons from a Jedi Scheduling Master – what would Yoda teach us? Lee A. Peters, MSCE, PE and John L. Homer, MSCE, PE Introduction 1 of 6 Become a Scheduling Jedi – be more than a competent scheduler – be a Master. 3 Introduction 2 of 6 Schedulers grow and develop through a series of projects without the guidance of a Master Scheduler. Development is largely dependent on your personal ability to reflect, to analyze, and to critically examine your own performance. 4 Introduction 3 of 6 Delivering required results is brutal in our world of intense, complex, grueling projects. Come sit at the feet of Masters who follow Yoda’s example to teach lessons of victory for becoming a scheduling master. 5 Introduction 4 of 6 Explore the skills and lessons of a Scheduling Master and learn the means to develop them. 6

Upload: pmi-central-indiana-chapter

Post on 15-Apr-2017

40 views

Category:

Business


0 download

TRANSCRIPT

Page 1: Pdd 2016   lee peters - lessons from a jedi schedule

1

Lessons from aJedi Scheduling Master

– what would Yoda teach us?

Lee A. Peters, MSCE, PE and John L. Homer, MSCE, PE

Introduction 1 of 6

• Become a Scheduling Jedi – be more than a competent scheduler – be a Master.

3

Introduction 2 of 6

• Schedulers grow and develop through a series of projects without the guidance of a Master Scheduler.

• Development is largely dependent on your personal ability to reflect, to analyze, and to critically examine your own performance.

4

Introduction 3 of 6

• Delivering required results is brutal in our world of intense, complex, grueling projects.

• Come sit at the feet of Masters who follow Yoda’s example to teach lessons of victory for becoming a scheduling master.

5

Introduction 4 of 6

• Explore the skills and lessons of a Scheduling Master and learn the means to develop them.

6

Page 2: Pdd 2016   lee peters - lessons from a jedi schedule

2

Introduction 5 of 6

• Yoda is more than a Master who allows you to watch and learn as he works.

• Yoda actively encourages, teaches, preaches, and drills knowledge, skills, attitudes, and beliefs of a Jedi Master.

• Yoda also allowed failure.

7

Lesson – what do you do when you observe someone planting the sword in the ground?

Introduction 6 of 6

• Like Yoda, actively encourage, teach, and drill the knowledge, skills, attitudes and beliefs of a Jedi – a Scheduling Master.

• How do you do it?

8

LESSON – tough to teach, to coach, to mentor. Most say ‘if I am not …’

Learning Objectives1 of 3

• Hear key lessons of project scheduling success painfully learned in the battle grounds of intense, complex, tortuous projects!

9

Learning Objectives2 of 3

• Absorb, internalize, and apply these lessons to concentrate time and talent on neutralizing dangerous threats, gaining great rewards, or wining decisive challenges in your own schedules!

10

Learning Objectives3 of 3

• Use each lesson to reflect on your personal project experience to derive your own lessons of Scheduling Mastery … be victorious on your most extreme projects.

11

Narrative 1 of 7

• To produce project results reliably requires more than competence … it requires mastery.

• A Scheduling Master integrates:– fundamentals of scheduling– with leading a project team– with catalyzing the momentum of a project.

12

Page 3: Pdd 2016   lee peters - lessons from a jedi schedule

3

Narrative 2 of 7

• We focus on lessons learned from extensive experience in building, training and guiding projects to success.

• Our experience extends from the jungles of Vietnam through many types of construction projects to product development in three industries and to the organization of international sporting events.

13

Narrative 3 of 7

• The mantra of a Scheduling Master then becomes the imperatives ‘Results, Scope, Performance’.

• We continue with the core concepts of establishing a culture, an environment, surrounding project performance, influencing the entire project community.

14

Narrative 4 of 7

• Emphasize communicating, planning, measuring, and feeding back throughout the project process.

• Successful project examples describe establishing the culture, adopting objectives, measuring performance and accomplishing the results.

15

Narrative 5 of 7

• A huge number of things must go right for a project to succeed.

• Missing only one of the many opportunities necessary for success can cause catastrophic failure.

• Scheduling is the key to getting all things right!

16

Narrative 6 of 7

• Scheduling only addresses getting things done at the right time. This can be:– wrong things done right at the right time. – or the right things done wrong at the right time– OR it can be the right things done right at the

wrong time• Buried under scheduling are the right

things done right!

17

LESSON

Narrative7 of 7

• Schedulers have to focus on:– the right things done – effectiveness –

scope, work breakdown – things done right – efficiency – performance,

work methods– the right things done right at the right time –

efficacy – schedules (of many types).

18

LESSON – not just when things are done

Page 4: Pdd 2016   lee peters - lessons from a jedi schedule

4

Time is …

• Time is the ONLY PERISHABLE RESOURCE

19

.

Project Fundamentals1 of 2

• Results – the deliverable

• Scope – the work• Performance –

accomplishing the work

20

LESSON – Three Fundamentals

Project Fundamentals2 of 2

• Only in ‘performance,’ do we encompass doing the right things the right way at the right time.

• Performance completes the scope – the work required to produce the result.

• Results, Scope, and Performance– for projects, we reduce Risk – reduce uncertainty

within both positive or opportunities and negative or threats.

21

LESSON – we create certainty

Project Fundamental: Result 1 of 2

• Our mission, our purpose, and our gestalt as project teams is delivering required results.

• Success only happens with required results• (Success does not always happen with the

results but without the results, there is no success!)

22

LESSON

Project Fundamental:Result 2 of 2

• Sometimes you have to go from an end to a beginning. – Backward scheduling tends to be more prayer

than plan!• Begin with the end in sight – preach the

result and the benefits to the client, to the team, to everyone else.

23LESSON

Project Fundamental:Scope 1 of 4

• Scope is the first step in scheduling – doing the right things – effectiveness.– The scope of that work should be sufficient to

produce the required results – no more and not less.

– Work-breakdown-structure is crucial to defining scope.

– What we miss in ‘deliverable-based scope’ is the scope!

24

Page 5: Pdd 2016   lee peters - lessons from a jedi schedule

5

Project Fundamental:Scope 2 of 4

• Scope is the amount or the number of work items that has to be completed to produce the results.

• By carefully defining scope, we gain effectiveness – doing the right things and only the right things.

25

If you are …, when you are scheduling; you are going to

make a mistake• Breaking work down• Assigning crew sizes• Determining work

methods• Figuring durations• Are there others?

• Look at the Activity– It is possible to do all this

while scheduling if you are disciplined

• Then look at the relationship

• Leave tracks

26

LESSON – scheduling is both communal and communicative.

Project Fundamental:Scope 3 of 4

• Scheduling work is similar to conducting an orchestra.– In scheduling, we

move work across the resource

– or we move resource across the work.

• The art is determining– What work– How much Work– Is to be accomplished

in which way– Where– By which resource– For how long– When– In what sequence

27

Project Fundamental:Scope 4 of 4

• WBS allows us to estimate:– Team or crew is necessary to do that work in

that duration– Duration – how long the work will take– Effort – labor hours for each work item– Cost estimate – a multiple of labor hours

28

Frozen Scope

• Frozen scope and the abominable snowman are alike:– they are both myths– and they both melt

when sufficient heat is applied.

29

Measure Effectiveness 1of 4

• Effectiveness is doing right things• We ensure the piece of scope is

necessary work. • We have to be sure we only do what is

required to produce the result – nothing more.

• Just what is that work?

30

LESSON

Page 6: Pdd 2016   lee peters - lessons from a jedi schedule

6

Measure Effectiveness2 of 4

• Ask others to glean the work list.

• Measure the work-not-completed when the activity is done.

• Listen to complaints and adjust the work list.

• Review the work with team members

31

Measure Effectiveness3 of 4

• Measure changes in scope, both number and magnitude. – We can also put durations and labor hours

against each changed work item.– Measure the impact on scope

by the changed work.– Change is a measure of

the quality of scope definition and quality of work-breakdown-structure.

32

LESSON

Measure Effectiveness 4 of 4

• What is your change within a project?

• Change of more than 5% in total – labor hours– duration– number of activities– or cost

• Change is an indicator of poor project methodology.

• Change most likely caused by lack of investment in planning

• Change is a result of not taking time to plan, to schedule.

33

LESSON

Project Fundamental –Performance

• Effort and duration – efficiency • Performance is governed by the methods

or procedures of work.

34

A second time:Performance and Risk

• Only in ‘performance,’ do we encompass doing the right things the right way at the right time.

• Performance completes the scope – the work required to produce the result.

• Risk is the uncertainty within Results, Scope, and Performance– both positive or opportunities and negative or threats.– Uncertainty!– Our job is to make things certain!

35

Methods1 of 6

• Methods depend on– materials (how much value has been added to

the material as well as the technology (PVC pipe versus copper) of the material?)

– tools and equipment– skill of the people (not just the number)– supervision (quantity, quality, planning skill,

teaching skill)– information (plans, drawings, research,

procedures, technology)

36

Page 7: Pdd 2016   lee peters - lessons from a jedi schedule

7

37

Crew

Information

Materials / Parts

Tools &Equipment

Supervision

=

Management

Work

LESSON Methods2 of 6

• Change any single resource changes the method changes the performance.

• Change the performance and the duration changes.

38

LESSON

Methods3 of 6

• Methods control labor hours of work – the efficiency of doing things right.

• Methods are controlled by the mix of resources producing work at an assumed rate.

• Amount of work divided by rate of work produces duration of work.– Trouble is the rate varies within each operation

39

Methods4 of 6

• We must be certain we choose– right methods– people skilled in that

method– right resources– right expectations– to do the right work.

• Do you hear all those rights?– right way, right skills,

right expectations, right resources, and at the right time, in order to complete right work.

40

LESSON

Methods5 of 6

• Typically, project teams focus on schedule and pretend the underlying methods are not our problem.– We say people are empowered to fix problems.– But we do not enable people with resources– Or we outsource it, saying that is the sub’s

challenge• Assure that the people are enabled – given

the resources and skills to do the work.

41

Methods6 of 6

• Remember this:• much project risk – uncertainty• lurks within resource

– Quality (experience, training, skill)– Quantity (availability)– Price (value)– Productivity (rate of quality work)

42

Page 8: Pdd 2016   lee peters - lessons from a jedi schedule

8

Provisional Project Proverb

• "In preparing for battle I have always found that plans are useless, but planning is indispensable.“

• Dwight D. Eisenhower

43

METHOD PRODUCTIVITY

• Labor Hours is the Currency of Projects• What are the Assumptions for Productivity in

each Method?– Uncertainty in the Labor Plan? Probably under 25%.

• What are the assumptions for Productivity for each Method?– Are these valid?

• What is the opportunity in knowing the productivity of a Method?

44

Measuring Efficiency

• We can determine our efficiency of doing things right– actual labor hours– actual durations– actual progress– comparing actual against hours of completed

work earned and scheduled hours • earned hours (earned value) – planned hours of

completed work.

45

Scheduling is Efficacy

• Doing the right work• the right way (with right people, materials,

tools, information, sufficient time)• at the right time – per the schedule!

46

Progress Reporting

• Project teams detest progress reporting because it vividly demonstrates their lack of progress.

47

Measure and Forecast

48

Scope / Progress Labor Hours Duration

Required based on Re-casting

Labor Hours required to complete remaining Work

Time required to complete remaining Work

Required based on Variance

Work Items Remaining x Variance

Labor Hours Remaining x Variance

Time Remaining x Variance

Remaining Work Items Left to be Completed

Labor Hours Remaining Time Remaining

Earned Labor Hours Earned based on Progress

Time Earned based on Progress

Other Variances

Earned vs ScheduledScheduled vs Actual

Scheduled vs Actual

Variance Completed vs Scheduled

Earned vs Actual Scheduled Earned vs Actual

Scheduled Work Items Scheduled to be Completed

Labor Hours Scheduled to be Used

Time Scheduled to be Used

Actual Work Items Competed

Labor Hours Used Time Elapsed

Page 9: Pdd 2016   lee peters - lessons from a jedi schedule

9

Early Warning

• Be sensitive to:– Rates of Performance– Quality of Work – Labor Hours Consumed– Duration Consumed– Means and Methods Used

versus Planned– Impact of Changes –

individual and collective

– Labor Hours Remaining– Duration Remaining– Work Remaining– Labor Hours Required to

Complete– Duration Required to

Complete

49 50

Scheduling is acommunal activity.

• Schedules are more important as communication tools than as a control tool.

• Use it to communicate.• It is helpful to walk the

schedule with the players.

• Many times.

• Walk by– Area - territory– Type of work -

technology– Entity doing work -

person– Time

51

LESSON

Sticky-Path-MethodSM

• and do the Sticky-ShuffleSM

• Schedules cannot be seen in a computer. • Schedules cannot be read on paper.• Only Schedules on walls can be walked.• Schedules should be meaningful to person

52

LESSON

Do the Sticky Shuffleas a community to know:

• for each action.– What work– How much work– Accomplished which way– Where– By whom– With what– For how long– When

53

Communal

• Scheduling is a Communal Activity• 1st Corollary

– The more people involved in scheduling the more committed people are to meeting the schedule.

• 2nd Corollary– The more useable the schedule the greater

the commitment.

54

Page 10: Pdd 2016   lee peters - lessons from a jedi schedule

10

The Sanctity of the Schedule

• If you cannot meet the schedule, what schedule can you meet?

55

Master of Chaos

• Our Product – the project schedule• Our Purpose – To Make Delivery of

Required Results Predictable– To make the delivery– Of the required results– certain.

56

LESSON

Magical Organizers of Uncertainty

• Schedules Organize Chaos– to make project delivery predictable!

• Consider a project without a– work breakdown structure– schedule

57

Our Real Job

• Reduce Uncertainty– IN EACH of our 500 (or 1000) project activities

• Make– Duration (how long will it take?)– Effort (how much work will it take? labor and

equipment hours)– Cost (production cost is variable)

• Certain (within a range)!

58

59

If I had eight hours tochop down a tree, I’dspend six sharpeningmy axe.

Abraham Lincoln

Should Predict the Weather

• We have a 30% probability of finishing in eight months and a 100% probability of finishing in twelve.

• Our triple point estimates– Just what is the probability of the reasonable expectancy?– How do you know?– What is the probability for the worst case?– The best case??

• Too frequently management is so impatient to start there is not sufficient time given to plan the 500 activities once much less three times.

60

Page 11: Pdd 2016   lee peters - lessons from a jedi schedule

11

CertainWithin a Range

• Range for Duration, Effort, Cost– Reasonable Pessimistic – 90% less than (worst

case – 2 std deviations)– Reasonable Optimistic – 90% greater than (best

case – 2 std deviations)– Reasonable Expected – most likely case – 70% 1

std deviation positive. • For each of the 500 activities

– Not Normal Distributions, not even close.

61

LESSON

Time Risk

• Two components– duration (how long the activity takes) which variation

is in productivity– labor effort (hours required by the method) which

variation is also in productivity– just how much labor (and/or equipment hours) is

required or actually produces the outcome / deliverable of that activity.

• Impact costs– Duration impacts variable overhead expense– Productivity impacts labor and equipment costs

62

Search Systematically

• For Risk – for Uncertainty– Threats – Opportunities

• For Unpredictable Variation– 10 to 20% of activities with unpredictable

variation can account for 90% of total deviation – these are known activities.

63

LESSON64

Activities with

Uncertainty

Value of Activities in a million dollar

project

Amount of

Variation

Worst Case Amount of Uncertainty

Amount of Variation in total budget.

5% $50,000 +500% $250,000 57% 25%

15% $150,000 +100% $150,000 34% 15%

80% $800,000 +5% $40,000 9% 5%

5% OF ALL ACTIVITIES ACCOUNT FOR 50% OF THE RISK

Search Continuously Search Concurrently

• Throughout– Planning– Estimating– Scheduling– Procuring– Executing– Controlling– Learning

• Time Risk is everywhere.

• Remember our purpose is to create Certainty

65

The planning pay off

• Five to ten to one.• For every time unit spent is planning …• five to ten time units are saved in

execution

66

LESSON

Page 12: Pdd 2016   lee peters - lessons from a jedi schedule

12

Over Planning

• No project has ever failed from being over-planned.

• Projects have failed from being too rigid.

67

LESSON

Being too Rigid

• Projects will fail from being too rigid.

68

Possible Project Proverbon EXECUTION

• No battle plan ever survives contact with the enemy. — Field Marshal Helmuth Carl Bernard von Moltke

69

Opportunities and Threats

• When you find Uncertainty– You find Both

• Opportunity• Threat

70LESSON

Impact on Each Other

• What is the impact of uncertainty in each dimension on the other?– Does an increase in duration increase cost?– Decrease in duration reduce cost?– Decrease in quality reduce duration?– Decrease in quality change cost? – How do they change as a function of each

other and as a function of Scope.

71

Time to the Deadline

90% of the work takes place after 50% of the time to deadline has passed.

72

Page 13: Pdd 2016   lee peters - lessons from a jedi schedule

13

UnreasonableDeadlines

• You can get commitment from anyone to an unreasonable deadline, but can't bully them into meeting it.

73

Absurd deadlines

• The more absurd the deadline, the more the cost to try to meet it.

74

Failsafe Deadlines

• Create failsafe deadlines – people underestimate the amount of work required.

75

Project Fuel

• Labor hours is the currency of a project.– Hours are spent to perform work and make

progress.• Money is project fuel• Decisions are the lubricant

– Include decisions in your schedule

76

LESSON

Uncertainty in TEAMWORK

• Does each of your support team have the skills, knowledge, and attitude required to complete their part of the scope and contribute to project team work?

• How will the attitudes and competencies of the managers and supervisors impact Duration and Labor Hours?

• How will leadership of the organization and of the project impact Duration and Labor Hours

77

• The more desperate the situation, the more optimistic the project team.

78

Page 14: Pdd 2016   lee peters - lessons from a jedi schedule

14

Communicate, communicate, communicate

• No project has ever failed from over-communication.

• You can not over–communicate

• Till you are sick and then twice as much.

79

It is what we know

• It ain't what we don't know that bites us, it's what we know and don't do!

80

Incentive Time

• does the fee buy on-time delivery or just delivery?

81

Early Delivery Time

• Surprise! Surprise! The paper mill will complete four months early.

• What does it matter that the operating team will not complete their training and be ready?

82

Time is the river of project progress.

• Skillful navigation skipping from one time to the next delivers a project result in the shortest duration.

• This makes the Project Manager appear to be a river walker - a traveler on time, in time, of time, between time.

83 84

Page 15: Pdd 2016   lee peters - lessons from a jedi schedule

15

Thank you

• ProjectLEADER.com• [email protected]• 317-873-0086

85