Lukas.joe

Common Scheduling Mistakes and How to Avoid Them Used with permission Joe Lukas, PMP, PM, CCE Vice-President 609-575-9306 (c) 888-762-3683 (w) [email_address]

What Will Be Covered? ,[object Object],[object Object]

Topic #1: Common Scheduling Mistakes ,[object Object],7. Confusing Duration and Work 10. Not using the project summary task, header, footer and legend 9. Not Using Start & Complete Milestones 8. Linking Summary Tasks 6. Misuse of Constraints

Topic #1: Common Scheduling Mistakes ,[object Object],1. Lack of Scheduling Knowledge 4. Lack of Schedule Contingency 5. Presence of Hangers 3. Incorrect Schedule Logic 2. Inappropriate Level of Detail

Scheduling Mistakes: #1 Lack of Scheduling Knowledge ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Scheduling Knowledge Check ,[object Object],[object Object],[object Object],[object Object],[object Object]

[object Object],[object Object],[object Object],[object Object],[object Object],Scheduling Knowledge Check

Scheduling Mistakes: #2 Inappropriate Level of Detail ,[object Object],[object Object],[object Object]

Scheduling Mistakes: #2 Inappropriate Level of Detail Includes the Structure of Project Tasks and Proper Naming of Deliverables & Activities Defined as “tasks” in scheduling software Use 20/80 Rule ,[object Object],May not be needed for small or medium projects, probably >1 level for large projects ,[object Object],Lowest level for control ,[object Object],Steps needed to create the deliverable ,[object Object]

Scheduling Mistakes: #2 Inappropriate Level of Detail ,[object Object],[object Object],[object Object],[object Object],Deliverables are written as a noun! ,[object Object],[object Object],[object Object],[object Object],Activities are written as an active verb-noun combination!

Scheduling Mistakes: #3 Incorrect Schedule Logic ,[object Object],[object Object],[object Object],[object Object],[object Object]

[object Object],[object Object],[object Object],[object Object],[object Object],Scheduling Mistakes: #3 Incorrect Schedule Logic

Scheduling Mistakes: #3 Incorrect Schedule Logic ,[object Object],[object Object],A 5 Day Duration B 7 Day Duration SS +3 ~ 10 Days Start-to-Start With 3 day lag Original Plan Actual

Scheduling Mistakes: #3 Better Schedule Logic ,[object Object],[object Object],A 5 Day Duration B 7 Day Duration FF+5 10 Days Finish-to-Finish With 5 day lag Original Plan Actual

Scheduling Mistakes: #3 Checking Schedule Logic ,[object Object],[object Object],Default Task Box Style Recommended Task Box Style ES EF LS LF ID Duration

Scheduling Mistakes: #4 Lack of Schedule Contingency ,[object Object],[object Object],[object Object],Task P Schedule Contingency 11 days Project Complete Task Q ~ ~

Scheduling Mistakes: #4 Lack of Schedule Contingency ,[object Object],Project Timeline 5 10 15 Days Nov Dec Jan Oct Feb Mar Apr May Schedule Contingency Start = 15 days 001 002 003 004 Status Date 8 days EAC = 0 days 5 10 15 005

Scheduling Mistakes: #5 Hangers Activity H is a Hanger – an unintended break in the network path ,[object Object],[object Object],B C D E F H Project Complete Project Start

Scheduling Mistakes: #5 How to Check for Hangers ,[object Object],[object Object],[object Object],Hangers These are NOT hangers – see schedule mistake #8

Scheduling Mistakes: #6 Misuse of Constraints ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Scheduling Mistakes: #6 Misuse of Constraints ,[object Object],[object Object],[object Object],[object Object]

Scheduling Mistakes: #6 Misuse of Constraints ,[object Object],KEY POINT: You should only use an inflexible constraint if the task start or finish date is fixed by factors beyond the control of the project team! ,[object Object],[object Object]

Scheduling Mistakes: #6 Misuse of Constraints ,[object Object],[object Object],[object Object],[object Object],[object Object]

Scheduling Mistakes: #6 Misuse of Constraints ,[object Object],[object Object],[object Object]

Scheduling Mistakes: #6 Misuse of Constraints ,[object Object],[object Object],Not showing reality!

Scheduling Mistakes: #6 Misuse of Constraints ,[object Object]

Scheduling Mistakes: #6 Misuse of Constraints ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Scheduling Mistakes: #6 Use Deadlines ,[object Object],[object Object],[object Object],Deadline

Scheduling Mistakes: #7 Confusing Work & Duration ,[object Object],[object Object],[object Object],[object Object],Definitions

[object Object],[object Object],[object Object],[object Object],Scheduling Mistakes: #7 Confusing Work & Duration Duration and Work Relationship

Duration and Work Relationship: ,[object Object],[object Object],[object Object],Scheduling Mistakes: #7 Confusing Work & Duration

Scheduling Mistakes: #7 Confusing Work & Duration ,[object Object],[object Object],[object Object],[object Object]

Scheduling Mistakes: #7 Confusing Work & Duration ,[object Object],[object Object],[object Object],Example - For Fixed Duration: If the task type is: Units Work Work Work Units Duration Fixed Units Fixed Duration … and you change the … then schedule software recalculates Duration Duration Units Fixed Work Task Type Relationships: Duration Duration Work

Scheduling Mistakes: #7 Confusing Work & Duration ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],When to Use Specific Task Types:

Scheduling Mistakes: #7 Confusing Work & Duration ,[object Object],[object Object],[object Object],[object Object],When to Use Specific Task Types:

Scheduling Mistakes: #8 Linking Summary Tasks ,[object Object],[object Object],[object Object]

Scheduling Mistakes: #8 Linking Summary Tasks ,[object Object],[object Object],Planning Phase Summary Task Execution Phase Summary Task Approvals 10 days P- 4 E-1

Scheduling Mistakes: #8 Linking Summary Tasks ,[object Object],[object Object],Task E-1 start pushed back 10 days due to link between summary tasks Planning Phase Summary Task Execution Phase Summary Task E-1 Approvals 10 days P- 4

Scheduling Mistakes: #9 Start & Complete Milestones ,[object Object],[object Object],[object Object],Project Start Project Complete Schedule Contingency

Scheduling Mistakes: #10 Project Summary Task ,[object Object],[object Object],[object Object]

Scheduling Mistakes: #10 Project Summary Task ,[object Object],When you print the schedule, the legend field shows:

Scheduling Mistakes: #10 Header, Footer & Legend ,[object Object],[object Object],[object Object]

Scheduling Mistakes: #10 Header, Footer & Legend ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Topic 2: Scheduling Procedure ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Scheduling Procedure ,[object Object],[object Object],[object Object]

Scheduling Procedure ,[object Object],[object Object]

Scheduling Procedure ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Scheduling Procedure ,[object Object],[object Object],[object Object],[object Object]

Scheduling Procedure WBS deliverables become Project Schedule Tasks

Precedence Diagramming Method ,[object Object],[object Object],[object Object],[object Object],[object Object],A B FF

Scheduling Procedure ,[object Object]

Scheduling Procedure ,[object Object],Don’t change to Fixed Work until schedule is baselined!

Conclusion ,[object Object],[object Object]

Questions? Joe Lukas, PMP, PM, CCE Vice-President 609-575-9306 (c) 888-762-3683 (w) [email_address]

Lukas.joe

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (7)

Similaire à Lukas.joe

Similaire à Lukas.joe (20)

Plus de NASAPMC

Plus de NASAPMC (20)

Dernier

Dernier (20)

Lukas.joe

Notes de l'éditeur