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.
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.
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.
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.
Spider Project is most functional and powerful professional project management software.
The first SP version was launched in 1993 and since then it has been constantly improved. Today is used in 34 countries though most Spider Project customers are in Russia. Spider Project offers numerous unique functional features and is the only PM software that optimizes resource, cost, and material constrained schedules and budgets for projects and portfolios.
The unique features of Spider Project include Quantity Based Scheduling, Conditional Scheduling, Skill Scheduling, Optimal Resource, Cost and Material Leveling, Resource Critical Path Calculation, Cash and Material Flows Calculation and Management, Trend Analysis, Advanced Risk Simulation and Analysis, Calculation of Success Probability Trends, Calculation and Management of required Project Time and Cost Buffers, Application of Corporate Norms, Management of many Parallel Budgets, Multiple WBS and many others.
Spider Project was and is used for management of many large scale programs in Russia, including $51bln construction program for 2014 Winter Olympic Games preparation.
The application areas where Spider Project is successfully used include Aerospace, Banking, Construction, Defense, Energy, Engineering, Infrastructure, Manufacturing, Metallurgy, Mining, Oil & Gas, Railways, Retail, Shipbuilding, Software Development, Telecommunications, Utilities, etc.
P6-Auditor - Display information from Primavera P6 audit tables in a user-friendly format
Unifier-Archiver - Extract and archive important documents and attachments from Primavera Unifier
Unifier-Loader - Load data into and out of Unifier via Excel
PCM-Loader - Import data into Primavera Contract Management with flexible and secure, template-driven Excel spreadsheets
PCM-Archiver - Extract and archive important documents and attachments from Primavera Contract Management
PCM-Unifier Migrator - Automatically transfer live and historical data from Primavera Contract Management to Primavera Unifier with ease
Create Radically Better Construction Schedules with ALICE Technologies
Use the power of AI to create construction schedules that reduce risk while cutting costs and build time. With ALICE, develop the ideal schedule during preconstruction -- or recover projects that are off schedule and over budget.
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.