I'm planning a application development project and I want to calculate work for some resources depending on the work of other resources.
Example: In the analysis phase I have 2 resources, an analist and an architect. The task depends on the work done by the analist. For instance it takes 8hr for the analist. In the project plan I want to calculate the overhead of the architect based on 10% of the work done by the analist. It can't be done in MS Project 2003 (at my knowledge). Any suggestions on another tool?
Hello, I'm planning a application development project and I want to calculate work for some resources depending on the work of other resources. Example: In the analysis phase I have 2 resources, an analist and an architect. The task depends on the work done by the analist. For instance it takes 8hr for the analist. In the project plan I want to calculate the overhead of the architect based on 10% of the work done by the analist. It can't be done in MS Project 2003 (at my knowledge). Any suggestions on another tool? Thanks in advance, Marc
I’m not sure why you would want to capture the architects time for work that is done by the analyst. However, if you are trying to capture the fact that while the analyst is ultimately responsible for the work package but the architect has actual work s\he must do to contribute to the final deliverable, I would do the following in Project:
1. Create task (just side note – I really hate the fact that Project calls items tasks – PMs should not manage at the task level, they should measure at the deliverable or work package level but that’s just me on my soap box) for Analyst – Requirements Document with LOE showing 8h
2. Create task for Architect – Requirements Document with LOE showing 1h (I know that isn’t exactly 10% but work with it)
3. Then you must link task Analyst with a SF (or FF depending) dependency to task Architect.
I’m not sure why you would want to capture the architects time for work that is done by the analyst. However, if you are trying to capture the fact that while the analyst is ultimately responsible for the work package but the architect has actual work s\he must do to contribute to the final deliverable, I would do the following in Project: 1. Create task (just side note – I really hate the fact that Project calls items tasks – PMs should not manage at the task level, they should measure at the deliverable or work package level but that’s just me on my soap box) for Analyst – Requirements Document with LOE showing 8h 2. Create task for Architect – Requirements Document with LOE showing 1h (I know that isn’t exactly 10% but work with it) 3. Then you must link task Analyst with a SF (or FF depending) dependency to task Architect. Make sense? If not (or even if it does but you want other opinions) you might also try posting to MS Project Discussion group at http://www.microsoft.com/office/community/....public.project cheers Saving Changes...
"More than any time in history mankind faces a crossroads. One path leads to despair and utter hopelessness, the other to total extinction. Let us pray that we have the wisdom to choose correctly."
