I think resource allocation to summary task as well as sub tasks is not totally rubbish. For e.g. If you have a deliverable that is the summary of different activities (sub tasks)to be done. In that case you can allocate the resources to its sub tasks then finally to make the deliverable complete some works need to be done (compilation & checking etc.) that extra work you could allocate to summary task. As the need of progress update, try to update % work complete instead % complete.
MS Projects does allow assignments at the parent task level and also allow collection of actuals against it. However, the calculation of %Complete at the parent level based on the actuals can be an issue.
For example, Andy and Bob are assigned to task 1.1 and task 1.2 for 20 hours and 40 hours, respectively. Carol is assigned to Task 1 the summary task for 40 hours.
The total planned work for task 1 is correctly shown as 100 hours. (20 + 40 + 40)
When Task 1.1 and Task 1.2 are progressed with actual 20 hours and 40 hours. It marked the task 1 as 100% complete since all the sub task are complete. The problem is that the actual work hours for task 1 is 60 hours (40 +20) that is different from the planned work. If you now enter the actual work for Task 1. The % Complete changes to 99%.
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.
I think resource allocation to summary task as well as sub tasks is not totally rubbish. For e.g. If you have a deliverable that is the summary of different activities (sub tasks)to be done. In that case you can allocate the resources to its sub tasks then finally to make the deliverable complete some works need to be done (compilation & checking etc.) that extra work you could allocate to summary task. As the need of progress update, try to update % work complete instead % complete.
Hi Dylan
Thanks for the reply.
GM
MS Projects does allow assignments at the parent task level and also allow collection of actuals against it. However, the calculation of %Complete at the parent level based on the actuals can be an issue.
For example, Andy and Bob are assigned to task 1.1 and task 1.2 for 20 hours and 40 hours, respectively. Carol is assigned to Task 1 the summary task for 40 hours.
The total planned work for task 1 is correctly shown as 100 hours. (20 + 40 + 40)
When Task 1.1 and Task 1.2 are progressed with actual 20 hours and 40 hours. It marked the task 1 as 100% complete since all the sub task are complete. The problem is that the actual work hours for task 1 is 60 hours (40 +20) that is different from the planned work. If you now enter the actual work for Task 1. The % Complete changes to 99%.
It seems not handling this properly.