Project Management

Essentials of Successful Project Schedule Planning: Part II

From the Voices on Project Management Blog
by , , , , , , , , , , , , , , , , , ,
Voices on Project Management offers insights, tips, advice and personal stories from project managers in different regions and industries. The goal is to get you thinking, and spark a discussion. So, if you read something that you agree with--or even disagree with--leave a comment.

About this Blog

RSS

View Posts By:

Cameron McGaughy
Lynda Bourne
Kevin Korterud
Conrado Morlan
Peter Tarhanidis
Mario Trentim
Jen Skrabak
David Wakeman
Wanda Curlee
Christian Bisson
Yasmina Khelifi
Sree Rao
Lenka Pincot
Soma Bhattacharya
Emily Luijbregts
cyndee miller
Jorge Martin Valdes Garciatorres
Marat Oyvetsky
Ramiro Rodrigues

Past Contributors:

Rex Holmlin
Vivek Prakash
Dan Goldfischer
Linda Agyapong
Jim De Piante
Siti Hajar Abdul Hamid
Bernadine Douglas
Michael Hatfield
Deanna Landers
Kelley Hunsberger
Taralyn Frasqueri-Molina
Alfonso Bucero Torres
Marian Haus
Shobhna Raghupathy
Peter Taylor
Joanna Newman
Saira Karim
Jess Tayel
Lung-Hung Chou
Rebecca Braglio
Roberto Toledo
Geoff Mattie

Recent Posts

Is Planning Predictive or Persuasive?

5 Ways to Up Your Mentorship Game

Lessons Learned on Digital Transformation

Murphy's Law: It’s a Call to Action, Not an Excuse

Emergent Strategy: How To Lead Now


Categories: Project Planning


In my previous post on project schedule planning, I referred to a five-step approach to setting up a schedule planning framework.

In this post, I offer seven tips on creating a schedule for any project:

  1. Focus on action. A project schedule is all about how deliverables will be produced. So after you break down work packages and deliverables, use active verbs to describe the smaller work tasks. For example, say "design webpage" instead of just "webpage designed."
  2. Keep tasks simple and compact. For a clear, clean project schedule, make task names short. If necessary, go into more details in an appendix or separate document to elaborate on each task and its outcomes.
  3. Create context. Also in a separate log, briefly document assumptions and constraints that accompany tasks. This helps in sequencing, linking and managing the tasks. For instance, if you know that a task needs to be executed in a certain timeframe, then you can better link, sequence or parallelize tasks.  
  4. Diagram. A visual illustration of the task sequencing and relationship will help the team understand the task dependencies and anticipating when these dependencies should kick in. Additionally, a visual breakdown can help identify tasks that can be done in tandem (i.e., those that have no dependencies).
  5. Use the critical path. Apply information gleaned from the critical path to the schedule. The critical path is most helpful in monitoring delays or identifying opportunities to accelerate the schedule. If a task located on the critical path slips, the project can be delayed. If a task on the critical path can be shortened, the project schedule can get shorter. If the critical path's duration exceeds the project deadline, then reduce scope, reassess durations, improve estimates or increase team resources. 
  6. Assess duration properly. When estimating task duration, distinguish between effort, duration and required calendar time to complete a task. The effort relates to the actual work required to complete the task (i.e., How many hours?). The duration refers to how many work periods are required to complete the effort (i.e., How many work days?). The required calendar time means mapping the work days on a calendar that includes holidays and vacation periods.
  7. Combine duration methods. Related to the sixth tip, combine multiple methods to assess duration. Take into account estimations from past projects and apply parametric estimation. For instance, if you use the three-point estimation (i.e., pessimistic, optimistic and most likely), find the theoretical estimation based on current expectations — but in addition, incorporate estimates from similar past tasks or projects.
What other tips help you when building a project schedule that can apply to any project?

Posted by Marian Haus on: May 21, 2013 09:39 AM | Permalink

Comments (4)

Please login or join to subscribe to this item
Good one Marian. Few other things i would add are, checking for 100% rule.. that is the entire scope is complete and not missed any activities. A schedule will be developed top down and verified bottoms up. It is important the teams don't get too optimistic or biased while assessing the duration. Due to consideration should be given to project risks and have a schedule contingency in the end.
Create Context is a key one too... any schedule should always be read in combination with this document.

Really good one....thanks.

Thanks for sharing.

Great insight. Thanks!

Please Login/Register to leave a comment.

ADVERTISEMENTS

"Too bad all the people who know how to run the country are busy driving taxis and cutting hair."

- George Burns