Thursday, April 26, 2012 3:25 PMWhat are best practices for baselining a project schedule to receive accurate, meaningful reports within Project Server? What effects on reporting will result when baselining single tasks?
Thursday, April 26, 2012 3:43 PM
It really depends on your oragnisations processes / planning methodology. A link below has useful best practices as a guide line:
Thursday, April 26, 2012 6:51 PM
"Best Practices of Baselining a Project" as Paul said, it depends organization wise, but just to answer your question.
First of all, you should know that if you have not set the baseline you have nothing to measure against and in that case you do not have control on your project. So baseline your project is important.
Actually the baseline is just a copy of your project at a certain point of time by which you can compare the actuals at a later stage at execution time.
The right time to do the baseline is when the initial planning is done and the budget is approved. In general, after you have done your WBS and inserted the tasks, have done your resource planning, budget planning it is time for you to Baseline your project.
Friday, April 27, 2012 12:27 PM
Apart from the Paul's & Manish's sound advices: Here is an excellent article which describes all:
What effects on reporting will result when baselining single tasks?
After you set a baseline for the entire project, you can view the baseline data side-by-side with the current planned data, the actual data, and the variance. but if you use selected task, The basline action will take the snapshot of the data of the task(s), you can get all EV analysis data only for the task of the project which may not be sufficient for you for Project EVA.
Hope that helps.
Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
- Proposed As Answer by Manish M Upadhyay Friday, April 27, 2012 1:03 PM