|
||||||||||||||||
|
TGIW: Tweets on Project Scheduling ~ Worth reading
Thank God! It is a weekend.
In this weekend post, I will share the best tweets on project scheduling and microsoft project (these are the best from my view 🙂 )
> crgpm: Reading: A Checklist for Work Breakdown Structures http://bit.ly/bDbtAU #pmot
> badgerpendous Take a proactive approach through transparent scheduling. Have people include your team early, before project start, to plan.
> Athif #MSproject is a scheduling tool ONLY &NOT a #WBS. Tech activities on Project shld B recorded in WBS dictionary only. #PMOT
> rat_uni_process: Project Management and the Critical Path Method http://tinyurl.com/32lxu2g (expand)
> webwhy: Blog Post: Project Server 2010: Integration with Team Foundation Server 2010 http://goo.gl/fb/w94XX #MSDN #microsoft
Is Project’s % Complete and % Work Complete same?
If your task is half complete, then the work is half completed. Right? Not always.
% Complete = Actual Duration / Duration
% Work Complete = Actual Work / Work
Many times, when you assign a resource to a task, the work is evenly spread across the duration and hence both these percentages will be same. This could vary if the work contour is other than flat. Let say you have a 5 days duration task assigned to a resource (100%). If the resource reports actual duration as 2.5 days, and actual work is 1h + 3h + 2h = 6h, then % complete is 50% and % work complete is 25%.
This difference would be visible in schedules with summary tasks, where the beginning tasks have minimum resources and tasks after the middle are loaded with more resources.