Show Planned vs. Actual

[REDesigner09]

Hi,

I'm developing the WBS & Gantt & trying to show planned vs. actual. Does a baseline need to be established first? If so, I am not able to do so because the project plan never seems to get finalized or fully approved.

Somehow, I still need to show planned vs. actual. How can this be done?

Thanks

 

[IRstuff]

You seem to be nullifying yourself. How can you compare to the "plan" if it ISN'T the baseline? There's nothing stopping you from re-baselining, over and over. If you have something that you think is the "plan" then you've baselined it in your mind, and its fluidity is tomorrow's problem.

TTFN
faq731-376

 

[Yjoshi]

Dear Red, I understand that it can not exist a "planned" with out a baseline. Just create a baseline and when the project plan is approved, create a new baseline

Regards

 

[REDesigner09]

Hi Guys,

Thanks for the feedback. I will create a baseline for this modified plan.

 

[ierland]

If needed you can save several interim baselines. I often copy first the most recent baseline into one of the baseline1 to 10 and after having updated my plan [manually and/or by Tracking, Update Project..., Reschedule) set a new baseline.

Why an easy solution if you can make it complicated?
Greetings from the Netherlands

 

[REDesigner09]

Hi Everyone,

Thanks for the great tips or suggestions. Part or maybe, the main problem is that team likes to plan as they go. This is partly because they don't know what they truly want to do or they can't get the right decision makers to authorize certain aspects of the projects.

Even though it may be doable to save several baselines, I don't think it's good practice & question if how accurate the project plan is.

Any suggestions for this type of situation?

Thanks

 

[ierland]

My motto is: If your project has finished exactly according the original plan, it is most likely that you had made the wrong plan.

Planning, better think of scheduling, is both a profession and an art. On the other hand it is no rocket science, although it may have to do with rockets. Just using your brains, gut feelings and an occasionally calculated guess [called gamble by others], together with the most important people motivator skills, are primary factors for success.

Just updating the project plan, moving to the Status Date of unfinished (parts of) tasks that should have been completed change your plan. Adding resources or sometimes even taking resources off some tasks in order that the remaining can work more efficient and quickly is again a change. Allow tasks to run in parallel or have overlaps that were initially scheduled sequentially, even skip certain (gold plated) tasks. That all together makes the job of a project manger interesting and at the same time threatening. Because if you have bosses that believe a project plan to be cast in concrete, your life will become a misery. Better change jobs in such an environment. MS Project is a TOOL in order to see work at hand, Deadlines that will be violated if no measures are taken. If you work with resources it can help to stop overloading, allowing levelling, monitoring and showing status, generating reports, allowing many views on your giant database with project data and much more. The problem is that many people use it only to draw Gantt bars, just with constraints [if possible cast in concrete with some MUST] rather than really using it as a scheduling tool which requires constant updating and amendments.
The Baseline is required to see momentary changes, thus to spot if there are slipping tasks or even tasks that finished earlier than planned. [These miracles may happen in a good plan or happen regularly in a plan that was set-up with much too much ÿou-never-know-how-fast-it-goes-just-let's-take-in-each-task-some-extra-time-to-satisfy-that-ignorant-boss]
So, contemplate these thoughts, stop nagging and start updating your plan as often as required. Success with your efforts!

By the way. There is also a new trend to use Monte Carlo simulations in order to have a better insight in Early Finish and Late Finish of your project, including taking into account of probabilities that a major machine might break down and that type of worries for a project manager and the bookkeepers. In real life those bookkeeper are usually the people most wasting money by abiding to their budget headings, always seeking the cheapest supplier, having never heard of quality, maintenance costs [that are nowadays often part of a lump sum contract] and lean building/constructing that may speed-up the project at higher article costs but lowering considerably labour costs and interests to be paid during the project.
MS Project has, at least in the older versions, a simple tool Pert Analysis to get an idea about Early, Realistic and Pessimistic Task Duration.

Why an easy solution if you can make it complicated?
Greetings from the Netherlands