How to track a bunch of unrelated activities?
Forum Sponsor
Top Posters
Julian Pegg
1 posts
Peter Nagy
2 posts
Raymund de Laza
17 posts
Syed_Asad
0 posts
Tony Greyvenstein
0 posts
Ahmed Al-Jubouri
13 posts
Umar Alvi
3 posts
Sibusiso Mahlalela
0 posts
Michael Samanyayi
3 posts
Simon Gumede
0 posts
Will,
thanks.
Unfortunately my current knowledge of MSP is apparently not sufficient to fully understand your answer.
<<
… assign units complete as the payment measurement type to a single task in MSP …..
>>
Can you just point me to where I can read more about it?
<<
method would show variences when statusing if there is work in progress on some of the documents
>>
What does exactly mean “statusing”?
Regards.
Hi all,
You could assign units complete as the payment measurement type to a single task in MSP. Each unit is one document and each unit is worth the average of the total time it will take to write all of the docs.(i.e. 12 docs taking various amounts of time but totaling 24 hours work would be 2 hours each) then adjust the duration according to how much of the Engineers time you would like to allocate to the activity. For each document that is completed you would claim one unit, however you would have to bear in mind that this method would show variences when statusing if there is work in progress on some of the documents.
Regards,
Will.
Darren, thanks.
This is what I have already been thinking about: to have an Excel spreadsheet, which calculates the % of completeness and in MS Project I just mark it.
Regards.
Hi Giles,
This isn’t something that MS Project does very well. You may well have to time-box the activity with a single fixed duration task and track progress by the amount of individual documents the engineer completes, 1/20, 2/20, 3/20, etc.
However, to estimate the effort you definitely need to calculate the amount of work that goes into creating each document, then total it up and use that as the basis for the tasks duration. As long as you register that assumption in a log of some kind, then I don’t think you’ll have too much difficulty tracking the task.
The only problem is you can’t tell if there are any dependencies on individual documents with other tasks in the schedule.
Regards,
Darren
Giles, just make sure that you have a grip on planning and tracking a single Task, and then do the same thing on each of the other Tasks. If they are not related by predecessor conditions, dont link them.
So you have 5 Tasks, each has a 10 Day Duration estimate.
Each has the engineer assigned.
You cant assign the engineer at 100% or he will be over-allocated, so he has to be assigned at 20% for each Task, or some combination of assignment % that does not make the Total Work exceed the 80 Hours of Work that he has available in 10 Days.
After they are all done, there is an Actual Start and Actual Finish date for each Task, and an Actual Work for each day and each Task. Put these in the fields in the Tracking Table.
Nothing changes if the Durations are not all equal, 10 Days.
If you do a status check at day 5, say, nothing much changes except you have a Remaining Duration > 0 instead of an Actual Finish date.