Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

How to track a bunch of unrelated activities?

5 replies [Last post]
Evgeny Z.
User offline. Last seen 38 weeks 6 days ago. Offline
Joined: 13 Jan 2008
Posts: 442
Groups: None
Hi everyone,

I need your advice on how to track the following activities.

There is a task for engineer to update / create a bunch of documents. There is no specific sequence in which they have to be done, also engineer may switch between documents.

But I have the following requirements:

• I need to be able to estimate the total amount of work (duration) needed for the whole activity.

• I need to be able to track completing of individual documents.


One thing I could have done is to put a schedule, where all documents need to be done one after another, but I do not want to force a specific sequence on engineer, it needs to be flexible. So, if would start working from the last document, I would have to change the schedule to update it.

Any ideas how it can be done?

Replies

Evgeny Z.
User offline. Last seen 38 weeks 6 days ago. Offline
Joined: 13 Jan 2008
Posts: 442
Groups: None
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.
Will Green
User offline. Last seen 15 years 12 weeks ago. Offline
Joined: 28 Jan 2009
Posts: 4
Groups: None
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 Engineer’s 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.
Evgeny Z.
User offline. Last seen 38 weeks 6 days ago. Offline
Joined: 13 Jan 2008
Posts: 442
Groups: None
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.
Darren Kosa
User offline. Last seen 7 years 9 weeks ago. Offline
Joined: 8 Feb 2008
Posts: 256
Groups: None
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
Trevor Rabey
User offline. Last seen 1 year 21 weeks ago. Offline
Joined: 29 Nov 2005
Posts: 530
Groups: None
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, don’t link them.
So you have 5 Tasks, each has a 10 Day Duration estimate.
Each has the engineer assigned.
You can’t 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.