Any good project planning and tracking tool should be able to do something like this for you. The left-hand-most column of numbers is no more than an addition of all the hours in the plan. For example, top left, the team will have 2443 hours holiday over the duration of the project stage. They shall be sick for 448 hours. How do we know how sick they're going to be? Look across to the third column from the right hand side: there's a figure of 2.4. That's 2.4%. In other words the 448 sickness hours represent 2.4% of the team members' time. Why 2.4%? Well, that's how sick they were last year - we're just re-using past factual information.
The second block are project investments (not overheads!). The P1 row tells us the team plan to invest 877 hours in team meetings and admin tasks such as time recording. Please would you add up the P4, P5 and P6 hours? They come to 1253. This is the change budget - the planner thinks 1253 hours will be spent investigating, implementing and controlling changes during the stage. Please look across to the 6th column in from the right hand side and add up those three numbers (coloured green). They come to 8.7 which simply tells us that the 1253 hours for change are 8.7% of the project hours. And you've guessed it, it's 8.7% because that's roughly what it had been in project stages like this in the past.
Please imagine you are the manager of this project. We are now at the end of week 4 of this 24 week stage.
According to the plan, how many hours holiday should the team have taken so far? 228 hours. And how many have they actually taken? 246 hours. So, over the first four weeks they've had 8% more holiday than they told you about.
Now please look at the P6 row, PCR Control. The fourth number along is 2.42 - what is that telling us?
| EFFORT DISTRIBUTION|
|-------Hours--------||--Of Category--||Of Proj / Non-Proj||-Of Grand Total-|
|Total||---To Date---||Total||-To Date-||Total||-To Date-||Total||-To Date-|
|NON PROJECT TIME|
|NON PROJECT TOTAL||3999||568||552||0.98||100||100||100||100||100||100||21.9||19.5||19.3|
|Int Qual check||Q1||75||40||26||0.65||1.2||3.9||2.4||0.5||1.7||1.1||0.4||1.4||0.9|
|Ext Qual check||QE||-||-||10||100||-||-||0.9||-||-||0.4||-||-||0.3|
|Real Work Totals||8045||1339||1241||0.93||100||100||100||56.3||56.9||53.8||44.0||45.9||43.4|
Over the first four weeks the team have spent nearly two and a half times more hours on PCR Control than expected - 104 hours vs a plan of 43 hours. If you were the project manager would you ignore that information? You'd investigate. It could simply be a time recording error or it could be a start up problem that won't recur - both of those would be good news. But if you conclude you haven't allowed anything like enough time for PCR Control in your plan what would you do? You'd adjust the plan to allocate more hours to that activity over the remaining 20 weeks of the stage. With luck you're rebalancing - something somewhere else is running under estimate. If you're not so lucky everything is running over and you may have a real problem. What we are getting here is early warning: so far, activity by activity, how good have the estimates proven to be.
In small projects you don't need this data as you can track each person and each task individually. But beyond a certain team size you can't do that any more and you need something like this to distil the essence out of the detail so you can read the runes (to mix a couple of metaphors).
One last thing on this page: what will the fourth column from the right tell us when we reach the
end of the stage? It will tell us, to one decimal place, what percentage of the project hours was actually
spent on meetings, on change, on rework, etc. Might that data be valuable when planning the next
similar project? Absolute gold dust. You've got a checklist of all the task types that were done and what
percentage each was of the total project hours.
Project Management Book
Copyright M Harding Roberts 2012 2013 2014 2015 2016 2017
Project Management Articles
IT Project Management Course
Home Sitemap Contact Us