{"id":598,"date":"2022-03-25T18:16:13","date_gmt":"2022-03-25T18:16:13","guid":{"rendered":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/?post_type=chapter&p=598"},"modified":"2022-04-15T18:54:44","modified_gmt":"2022-04-15T18:54:44","slug":"8-4-resource-allocation","status":"publish","type":"chapter","link":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/chapter\/8-4-resource-allocation\/","title":{"rendered":"8.4 Resource Allocation"},"content":{"raw":"Based on the Resource Management Plan and according to the estimation methods, the project team should identify the resources necessary for the project activities and should allocate them to execute the project activities. Allocation of resources is named \u201cResource Loading\u201d. Then, the project team can have a resource usage calendar that exhibits the amounts of resources assigned to each activity during the project. Let\u2019s continue with \u201cTable 7.1. Activity List Template\u201d from Chapter 7, and load resources to the activities of \u201c1.3 Preparation of Project Charter\u201d.\r\n
\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
Table 8.2: Resource Loading for 1.3 \u201cPreparation of Project Charter\u201d<\/caption>\r\n
\r\n
Activity List for Project \u201cGrocery LLC\u2019s M-Commerce Project\u201d<\/strong><\/div><\/td>\r\n<\/tr>\r\n
Activity identifier<\/strong><\/td>\r\nActivity title<\/strong><\/td>\r\nScope of Work<\/strong><\/td>\r\nPerson Responsible<\/strong><\/td>\r\nPredecessors<\/strong><\/td>\r\nResources<\/strong><\/td>\r\n<\/tr>\r\n
1.3<\/td>\r\nPreparation of Project Charter<\/td>\r\nThe project charter that will authorize the project manager to undertake the responsibility of the project and apply the resources to project activities will be prepared.<\/td>\r\nProject Manager<\/td>\r\n\r\n

\u00a0 \u00a0 \u00a0 \u00a01.1<\/p>\r\n

\u00a0 \u00a0 \u00a0 \u00a01.2<\/p>\r\n <\/td>\r\n

<\/td>\r\n<\/tr>\r\n
1.3.1<\/td>\r\nDevelop high-level scope<\/td>\r\nThe high-level scope consists of the project purpose, measurable project objectives, high-level requirements, project description, boundaries, key deliverables, and assumptions and constraints.<\/td>\r\nSystems Analyst 1<\/td>\r\n1.2<\/td>\r\nSystems Analyst 1<\/td>\r\n<\/tr>\r\n
1.3.2<\/td>\r\nIdentify overall project risks<\/td>\r\nThis includes the identification of the risks that affect the project in general.<\/td>\r\nSystems Analyst 2<\/td>\r\n1.3.1<\/td>\r\nSystems Analyst 2<\/td>\r\n<\/tr>\r\n
1.3.3<\/td>\r\nDevelop high-level schedule<\/td>\r\nThis includes the estimation of the overall schedule with summary milestones.<\/td>\r\nTeam Member 1<\/td>\r\n1.3.1<\/td>\r\nSystems Analyst 1<\/td>\r\n<\/tr>\r\n
1.3.4<\/td>\r\nIdentify main resources and develop a high-level budget<\/td>\r\nThis includes the initial estimation of all resources (human resources, physical resources, and services), and the budget.<\/td>\r\nTeam Member 2<\/td>\r\n1.3.3<\/td>\r\nSystems Analyst 1\r\n\r\n

Systems Analyst 2<\/p><\/td>\r\n<\/tr>\r\n

1.3.5<\/td>\r\nIdentify key stakeholders and project team member roles<\/td>\r\nStakeholders with high-interest levels and\/or power levels will be identified.\r\n\r\n

The project team's composition will be created. The qualifications required should be detailed.<\/p>\r\n\r\n

The project sponsor's authority will be detailed.<\/p><\/td>\r\n

Team Member 3<\/td>\r\n\r\n

\u00a0 \u00a0 \u00a0 1.3.1<\/p>\r\n

\u00a0 \u00a0 \u00a0 1.3.2<\/p>\r\n<\/td>\r\n

Systems Analyst 1\r\n\r\n

Systems Analyst 2<\/p>\r\n\r\n

Sales & Marketing Expert 1<\/p>\r\n\r\n

Sales & Marketing Expert 2<\/p>\r\n\r\n <\/td>\r\n<\/tr>\r\n

1.3.6<\/td>\r\nDevelop project approval requirements and project exit criteria<\/td>\r\nBased on the project scope and other sections of the project charter, project approval requirements and exit criteria should be detailed.\r\n\r\n

Exit criteria include the conditions that describe the early termination of the project.<\/p><\/td>\r\n

Team Member 1, 2, 3<\/td>\r\n\r\n

\u00a0 \u00a0 \u00a0 1.3.1<\/p>\r\n

\u00a0 \u00a0 \u00a0 1.3.2<\/p>\r\n

\u00a0 \u00a0 \u00a0 1.3.3<\/p>\r\n

\u00a0 \u00a0 \u00a0 1.3.4<\/p>\r\n

\u00a0 \u00a0 \u00a0 1.3.5<\/p>\r\n<\/td>\r\n

Systems Analyst 1\r\n\r\n

Systems Analyst 2<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/div>\r\n \r\n\r\nIn Table 8.2, we only assigned human resources. We also assume that all the people work full-time, which is 8 hours a day. They work during the weekdays, which makes the weekly total work hours forty. In Table 8.3, we can see how human resources are distributed to the tasks by week.\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
Table 8.3: Resource Usage Calendar<\/caption>\r\n
Resource Name<\/strong><\/th>\r\nWork<\/strong><\/th>\r\nMay 2<\/strong><\/th>\r\nMay 9<\/strong><\/th>\r\nMay 16<\/strong><\/th>\r\nMay 23<\/strong><\/th>\r\nMay 30<\/strong><\/th>\r\nJune 6<\/strong><\/th>\r\n<\/tr>\r\n<\/thead>\r\n
Systems Analyst 1<\/strong><\/td>\r\n240 hrs<\/strong><\/td>\r\n40<\/strong><\/td>\r\n32<\/strong><\/td>\r\n40<\/strong><\/td>\r\n64<\/strong><\/td>\r\n40<\/strong><\/td>\r\n24<\/strong><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Clarify project purpose and determine project scope <\/em><\/td>\r\n40 hrs<\/em><\/td>\r\n40<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Develop high-level scope <\/em><\/td>\r\n32 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n32<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Develop high-level schedule <\/em><\/td>\r\n48 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n40<\/em><\/td>\r\n8<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Identify main resources and develop a high-level budget <\/em><\/td>\r\n16 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n16<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Identify key stakeholders and project team member roles <\/em><\/td>\r\n64 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n40<\/em><\/td>\r\n24<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Develop project approval requirements and project exit criteria <\/em><\/td>\r\n40 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n16<\/em><\/td>\r\n24<\/em><\/td>\r\n<\/tr>\r\n
Systems Analyst 2<\/strong><\/td>\r\n200 hrs<\/strong><\/td>\r\n40<\/strong><\/td>\r\n0<\/strong><\/td>\r\n40<\/strong><\/td>\r\n56<\/strong><\/td>\r\n40<\/strong><\/td>\r\n24<\/strong><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Clarify project purpose and determine project scope <\/em><\/td>\r\n40 hrs<\/em><\/td>\r\n40<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Identify overall project risks<\/em><\/td>\r\n40 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n40<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Identify main resources and develop a high-level budget <\/em><\/td>\r\n16 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n16<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Identify key stakeholders and project team member roles <\/em><\/td>\r\n64 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n40<\/em><\/td>\r\n24<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Develop project approval requirements and project exit criteria <\/em><\/td>\r\n40 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n16<\/em><\/td>\r\n24<\/em><\/td>\r\n<\/tr>\r\n
Sales & Marketing Expert 1<\/strong><\/td>\r\n104 hrs<\/strong><\/td>\r\n40<\/strong><\/td>\r\n0<\/strong><\/td>\r\n0<\/strong><\/td>\r\n40<\/strong><\/td>\r\n24<\/strong><\/td>\r\n0<\/strong><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Clarify project purpose and determine project scope <\/em><\/td>\r\n40 hrs<\/em><\/td>\r\n40<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Identify key stakeholders and project team member roles <\/em><\/td>\r\n64 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n40<\/em><\/td>\r\n24<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
Sales & Marketing Expert 2<\/strong><\/td>\r\n104 hrs<\/strong><\/td>\r\n40<\/strong><\/td>\r\n0<\/strong><\/td>\r\n0<\/strong><\/td>\r\n40<\/strong><\/td>\r\n24<\/strong><\/td>\r\n0<\/strong><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Clarify project purpose and determine project scope <\/em><\/td>\r\n40 hrs<\/em><\/td>\r\n40<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n
\u00a0\u00a0 Identify key stakeholders and project team member roles <\/em><\/td>\r\n64 hrs<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n40<\/em><\/td>\r\n24<\/em><\/td>\r\n\u00a0<\/em><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n \r\n\r\nResource usage calendars help project teams evaluate whether resources are assigned without conflicts. As can be seen in Table 8.3, System Analyst 1 (SA1) and 2 (SA2), both, have resource overallocation problems on May 23rd week. SA1 works 64 hours on that week while SA2 works 56 hours. Both work more than 40 hours (8 hours per weekday) assuming that overtime work is not allowed. In the next section, we will discuss how to solve this overallocation by means of resource leveling.","rendered":"

Based on the Resource Management Plan and according to the estimation methods, the project team should identify the resources necessary for the project activities and should allocate them to execute the project activities. Allocation of resources is named \u201cResource Loading\u201d. Then, the project team can have a resource usage calendar that exhibits the amounts of resources assigned to each activity during the project. Let\u2019s continue with \u201cTable 7.1. Activity List Template\u201d from Chapter 7, and load resources to the activities of \u201c1.3 Preparation of Project Charter\u201d.<\/p>\n

\n\n\n\n\n\n\n\n\n\n\n\n
Table 8.2: Resource Loading for 1.3 \u201cPreparation of Project Charter\u201d<\/caption>\n
\n
Activity List for Project \u201cGrocery LLC\u2019s M-Commerce Project\u201d<\/strong><\/div>\n<\/td>\n<\/tr>\n
Activity identifier<\/strong><\/td>\nActivity title<\/strong><\/td>\nScope of Work<\/strong><\/td>\nPerson Responsible<\/strong><\/td>\nPredecessors<\/strong><\/td>\nResources<\/strong><\/td>\n<\/tr>\n
1.3<\/td>\nPreparation of Project Charter<\/td>\nThe project charter that will authorize the project manager to undertake the responsibility of the project and apply the resources to project activities will be prepared.<\/td>\nProject Manager<\/td>\n\n

\u00a0 \u00a0 \u00a0 \u00a01.1<\/p>\n

\u00a0 \u00a0 \u00a0 \u00a01.2<\/p>\n

 <\/td>\n

<\/td>\n<\/tr>\n
1.3.1<\/td>\nDevelop high-level scope<\/td>\nThe high-level scope consists of the project purpose, measurable project objectives, high-level requirements, project description, boundaries, key deliverables, and assumptions and constraints.<\/td>\nSystems Analyst 1<\/td>\n1.2<\/td>\nSystems Analyst 1<\/td>\n<\/tr>\n
1.3.2<\/td>\nIdentify overall project risks<\/td>\nThis includes the identification of the risks that affect the project in general.<\/td>\nSystems Analyst 2<\/td>\n1.3.1<\/td>\nSystems Analyst 2<\/td>\n<\/tr>\n
1.3.3<\/td>\nDevelop high-level schedule<\/td>\nThis includes the estimation of the overall schedule with summary milestones.<\/td>\nTeam Member 1<\/td>\n1.3.1<\/td>\nSystems Analyst 1<\/td>\n<\/tr>\n
1.3.4<\/td>\nIdentify main resources and develop a high-level budget<\/td>\nThis includes the initial estimation of all resources (human resources, physical resources, and services), and the budget.<\/td>\nTeam Member 2<\/td>\n1.3.3<\/td>\nSystems Analyst 1<\/p>\n

Systems Analyst 2<\/p>\n<\/td>\n<\/tr>\n

1.3.5<\/td>\nIdentify key stakeholders and project team member roles<\/td>\nStakeholders with high-interest levels and\/or power levels will be identified.<\/p>\n

The project team’s composition will be created. The qualifications required should be detailed.<\/p>\n

The project sponsor’s authority will be detailed.<\/p>\n<\/td>\n

Team Member 3<\/td>\n\n

\u00a0 \u00a0 \u00a0 1.3.1<\/p>\n

\u00a0 \u00a0 \u00a0 1.3.2<\/p>\n<\/td>\n

Systems Analyst 1<\/p>\n

Systems Analyst 2<\/p>\n

Sales & Marketing Expert 1<\/p>\n

Sales & Marketing Expert 2<\/p>\n

 <\/td>\n<\/tr>\n

1.3.6<\/td>\nDevelop project approval requirements and project exit criteria<\/td>\nBased on the project scope and other sections of the project charter, project approval requirements and exit criteria should be detailed.<\/p>\n

Exit criteria include the conditions that describe the early termination of the project.<\/p>\n<\/td>\n

Team Member 1, 2, 3<\/td>\n\n

\u00a0 \u00a0 \u00a0 1.3.1<\/p>\n

\u00a0 \u00a0 \u00a0 1.3.2<\/p>\n

\u00a0 \u00a0 \u00a0 1.3.3<\/p>\n

\u00a0 \u00a0 \u00a0 1.3.4<\/p>\n

\u00a0 \u00a0 \u00a0 1.3.5<\/p>\n<\/td>\n

Systems Analyst 1<\/p>\n

Systems Analyst 2<\/p>\n<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

 <\/p>\n

In Table 8.2, we only assigned human resources. We also assume that all the people work full-time, which is 8 hours a day. They work during the weekdays, which makes the weekly total work hours forty. In Table 8.3, we can see how human resources are distributed to the tasks by week.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Table 8.3: Resource Usage Calendar<\/caption>\n
Resource Name<\/strong><\/th>\nWork<\/strong><\/th>\nMay 2<\/strong><\/th>\nMay 9<\/strong><\/th>\nMay 16<\/strong><\/th>\nMay 23<\/strong><\/th>\nMay 30<\/strong><\/th>\nJune 6<\/strong><\/th>\n<\/tr>\n<\/thead>\n
Systems Analyst 1<\/strong><\/td>\n240 hrs<\/strong><\/td>\n40<\/strong><\/td>\n32<\/strong><\/td>\n40<\/strong><\/td>\n64<\/strong><\/td>\n40<\/strong><\/td>\n24<\/strong><\/td>\n<\/tr>\n
\u00a0\u00a0 Clarify project purpose and determine project scope <\/em><\/td>\n40 hrs<\/em><\/td>\n40<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Develop high-level scope <\/em><\/td>\n32 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n32<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Develop high-level schedule <\/em><\/td>\n48 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n40<\/em><\/td>\n8<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Identify main resources and develop a high-level budget <\/em><\/td>\n16 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n16<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Identify key stakeholders and project team member roles <\/em><\/td>\n64 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n40<\/em><\/td>\n24<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Develop project approval requirements and project exit criteria <\/em><\/td>\n40 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n16<\/em><\/td>\n24<\/em><\/td>\n<\/tr>\n
Systems Analyst 2<\/strong><\/td>\n200 hrs<\/strong><\/td>\n40<\/strong><\/td>\n0<\/strong><\/td>\n40<\/strong><\/td>\n56<\/strong><\/td>\n40<\/strong><\/td>\n24<\/strong><\/td>\n<\/tr>\n
\u00a0\u00a0 Clarify project purpose and determine project scope <\/em><\/td>\n40 hrs<\/em><\/td>\n40<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Identify overall project risks<\/em><\/td>\n40 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n40<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Identify main resources and develop a high-level budget <\/em><\/td>\n16 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n16<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Identify key stakeholders and project team member roles <\/em><\/td>\n64 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n40<\/em><\/td>\n24<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Develop project approval requirements and project exit criteria <\/em><\/td>\n40 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n16<\/em><\/td>\n24<\/em><\/td>\n<\/tr>\n
Sales & Marketing Expert 1<\/strong><\/td>\n104 hrs<\/strong><\/td>\n40<\/strong><\/td>\n0<\/strong><\/td>\n0<\/strong><\/td>\n40<\/strong><\/td>\n24<\/strong><\/td>\n0<\/strong><\/td>\n<\/tr>\n
\u00a0\u00a0 Clarify project purpose and determine project scope <\/em><\/td>\n40 hrs<\/em><\/td>\n40<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Identify key stakeholders and project team member roles <\/em><\/td>\n64 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n40<\/em><\/td>\n24<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
Sales & Marketing Expert 2<\/strong><\/td>\n104 hrs<\/strong><\/td>\n40<\/strong><\/td>\n0<\/strong><\/td>\n0<\/strong><\/td>\n40<\/strong><\/td>\n24<\/strong><\/td>\n0<\/strong><\/td>\n<\/tr>\n
\u00a0\u00a0 Clarify project purpose and determine project scope <\/em><\/td>\n40 hrs<\/em><\/td>\n40<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n
\u00a0\u00a0 Identify key stakeholders and project team member roles <\/em><\/td>\n64 hrs<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n\u00a0<\/em><\/td>\n40<\/em><\/td>\n24<\/em><\/td>\n\u00a0<\/em><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Resource usage calendars help project teams evaluate whether resources are assigned without conflicts. As can be seen in Table 8.3, System Analyst 1 (SA1) and 2 (SA2), both, have resource overallocation problems on May 23rd week. SA1 works 64 hours on that week while SA2 works 56 hours. Both work more than 40 hours (8 hours per weekday) assuming that overtime work is not allowed. In the next section, we will discuss how to solve this overallocation by means of resource leveling.<\/p>\n","protected":false},"author":3,"menu_order":5,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-598","chapter","type-chapter","status-publish","hentry"],"part":588,"_links":{"self":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/598","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/users\/3"}],"version-history":[{"count":28,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/598\/revisions"}],"predecessor-version":[{"id":849,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/598\/revisions\/849"}],"part":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/parts\/588"}],"metadata":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapters\/598\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/media?parent=598"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/pressbooks\/v2\/chapter-type?post=598"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/contributor?post=598"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/project-management-navigating-the-complexity\/wp-json\/wp\/v2\/license?post=598"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}