using standardized green-normal/red-critical bars layouts is the best way to discourage colleagues to actually use your schedules, as no-one but the planner really knows what’s going on in it. i’ve been using colors extensively for years to provide heads-up on the tasks content; for example, using color-code based on work packages or main equipment will immediately provide additional information and save readers the trouble of looking up the detailed description of all tasks. so agreeing with the team of a particular color code (even a completely rainbowy-one) at the beginning of the project will definitely add value to the schedule. (obviously avoid modify it once everyone is accustomed to it)
and indeed, since i spend 10h a day meddling with thoses rectangular little bars, i’d rather have them looking lively and funky than boringly dull monochromatics. two birds down with one stone.

leveling works great in the right context. putting in imposed false logic creats problems during execution and prevents the usage of risk analysis simulations

linda,
thanks for the comments. i’m with you – i think leveling is a feature that is grossly overstated – users expect the software to do the detailed work of analyzing overallocations and correcting them one at a time. i’ve only ever seen it used properly on plant shut-down projects using a particular scheduling technique. perhaps i’ll have to revise at add leveling as #12.

i would add a 12th item to the list: depend on primavera to completely level your project. i’ve been using primavera (and other programs) for over 25 years and i’ve never seen leveling work properly. i’m not saying it won’t work; i’m saying i’ve never ever seen it work, and i quit using it after i saw my mentors fail miserably (and embarrassingly) at it over and over. now i see the fresh-out-of-expensive-training-noobs insisting it’s the only way to go, only to see their schedule crash and burn on day 3 of the project. i’ve found that a properly detailed, well thought out and correctly tied schedule doesn’t need much leveling. i hope the new planners take your 11 commandments to heart.

mr. ratheesh,
after changing the schedule to l5 set it as secondary baseline and your previous l3 as primary baseline.

good one. thank you charles!

i know it’s limiting. i’m working on a proof, but i’ve been told by experts that p6 has bugs in date calculations when using multiple calendars.

a space in your schedule table may represent a business or project process that was not completed. treat blanks as flaws in your schedule, code assignments, steps, expenses, udfs, resource units etc. ask every column as a question against every activity / wbs, it may help you develop more meaningful schedules, with fewer activities, which are easier to manage…

hi samuel. you can either do what’s in this tutorial for large projects https://www.plannertuts.com/primavera-p6-calendars-biggest-problem/ or you can reenter your durations so they are proper after a calendar change. happy to answer questions about workshops in the forums on our premium site – best to post your questions there.

thanks once again for publishing this article.

jeremy, you’re welcome to cut and paste it into word doc for the time being. i’m considering converting to slides. m

maybe i’ll draft that convincing-them article, but it might be a book!

my pleasure joel. thanks for the comment.

these are the common mistakes if a planner will fail to look at details in developing his schedules. at times when i was asked for my opinion or comments i often encounter most of these errors. even the experienced planners will benefit from this article. common planning pitfalls and how to fix them.

thanks for publishing these pointers. it will be a great help for the aspiring planners. nice one.