{"id":979,"date":"2025-01-02T06:00:31","date_gmt":"2025-01-02T06:00:31","guid":{"rendered":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/?post_type=chapter&p=979"},"modified":"2025-01-20T05:24:29","modified_gmt":"2025-01-20T05:24:29","slug":"8-10-exercises","status":"publish","type":"chapter","link":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/chapter\/8-10-exercises\/","title":{"rendered":"8.10 Exercises"},"content":{"raw":"
\r\n

Exercise 1: Resource Allocation and Leveling for the Smart Home Project<\/h2>\r\n<\/header>\r\n
\r\n\r\nSmartTech Inc., a leading fictional company in home automation, has been contracted to install a comprehensive smart home automation system for a luxury residence. The system includes smart lighting, security cameras, and voice-controlled HVAC systems. The homeowner expects the installation to be completed in 4 weeks to align with their move-in date.\r\n\r\nThe project involves the following activities:\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
Activity<\/strong><\/th>\r\nDescription<\/strong><\/th>\r\nDuration<\/strong><\/th>\r\nPredecessors<\/strong><\/th>\r\nResources Required<\/strong><\/th>\r\n<\/tr>\r\n<\/thead>\r\n
A<\/td>\r\nPerform home assessment<\/td>\r\n2 days<\/td>\r\n-<\/td>\r\n2 assessors<\/td>\r\n<\/tr>\r\n
B<\/td>\r\nProcure equipment<\/td>\r\n7 days<\/td>\r\n-<\/td>\r\nProcurement team<\/td>\r\n<\/tr>\r\n
C<\/td>\r\nInstall smart lighting systems<\/td>\r\n3 days<\/td>\r\nA, B<\/td>\r\n2 technicians<\/td>\r\n<\/tr>\r\n
D<\/td>\r\nInstall security camera systems<\/td>\r\n2 days<\/td>\r\nA, B<\/td>\r\n2 technicians<\/td>\r\n<\/tr>\r\n
E<\/td>\r\nInstall HVAC systems<\/td>\r\n3 days<\/td>\r\nA, B<\/td>\r\n2 technicians<\/td>\r\n<\/tr>\r\n
F<\/td>\r\nPerform system testing<\/td>\r\n1 day<\/td>\r\nC, D, E<\/td>\r\n1 technician, 1 quality analyst<\/td>\r\n<\/tr>\r\n
G<\/td>\r\nProvide homeowner training<\/td>\r\n1 day<\/td>\r\nF<\/td>\r\n1 trainer<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\nThe team includes:\r\n
    \r\n \t
  • 2 assessors<\/li>\r\n \t
  • 3 technicians<\/li>\r\n \t
  • 1 quality analyst<\/li>\r\n \t
  • 1 trainer<\/li>\r\n<\/ul>\r\n

    Tasks and Questions<\/strong><\/h3>\r\n

    Part 1: Resource Allocation<\/strong><\/h4>\r\n
      \r\n \t
    1. Create a Resource Allocation Plan<\/strong>: Assign resources to each activity based on the requirements and available team members.\r\n
        \r\n \t
      • Create a resource allocation table for all activities.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
      • Identify Overallocations<\/strong>:\r\n
          \r\n \t
        • Review the resource allocation and identify any overallocation issues.<\/li>\r\n \t
        • Highlight the specific activities and days where conflicts occur.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ol>\r\n

          Part 2: Resource Leveling<\/strong><\/h4>\r\n
            \r\n \t
          1. Apply Resource Leveling<\/strong>: Adjust the schedule to resolve overallocation issues using resource leveling techniques.\r\n
              \r\n \t
            • Reallocate tasks to balance the workload.<\/li>\r\n \t
            • Adjust the start dates of activities if necessary.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
            • Analyze the Impact<\/strong>:\r\n
                \r\n \t
              • How does resource leveling affect the project\u2019s total duration?<\/li>\r\n \t
              • Are there any delays in completing the project within the homeowner\u2019s 4-week deadline?<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ol>\r\n
                  \r\n \t
                1. <\/li>\r\n<\/ol>\r\n<\/div>\r\n<\/div>\r\n \r\n
                  \r\n

                  Exercise 2: Crashing Activities<\/h2>\r\n<\/header>\r\n
                  \r\n\r\nBelow is a WBS for a project that includes durations and predecessors.\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
                  Activity ID<\/strong><\/td>\r\nActivity<\/strong><\/td>\r\nPredecessor(s)<\/strong><\/td>\r\nDuration (days)<\/strong><\/td>\r\n<\/tr>\r\n
                  A<\/td>\r\nDefine Project Scope<\/td>\r\nNone<\/td>\r\n3<\/td>\r\n<\/tr>\r\n
                  B<\/td>\r\nIdentify Stakeholder Requirements and Conduct Feasibility Study<\/td>\r\nA<\/td>\r\n9<\/td>\r\n<\/tr>\r\n
                  C<\/td>\r\nDevelop Project Charter and Initial Plan<\/td>\r\nB<\/td>\r\n7<\/td>\r\n<\/tr>\r\n
                  D<\/td>\r\nCreate Wireframes and Mockups<\/td>\r\nC<\/td>\r\n7<\/td>\r\n<\/tr>\r\n
                  E<\/td>\r\nPrepare Testing Environment<\/td>\r\nC<\/td>\r\n6<\/td>\r\n<\/tr>\r\n
                  F<\/td>\r\nDevelop Front-End and Back-End Components<\/td>\r\nD<\/td>\r\n12<\/td>\r\n<\/tr>\r\n
                  G<\/td>\r\nIntegrate Components and Test Functionality<\/td>\r\nE, F<\/td>\r\n8<\/td>\r\n<\/tr>\r\n
                  H<\/td>\r\nConduct User Acceptance Testing (UAT)<\/td>\r\nG<\/td>\r\n6<\/td>\r\n<\/tr>\r\n
                  I<\/td>\r\nDeploy and Optimize Performance<\/td>\r\nH<\/td>\r\n7<\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n

                  Tasks and Questions<\/strong><\/h3>\r\n
                    \r\n \t
                  1. Draw the Network Diagram:<\/strong>\r\n
                      \r\n \t
                    • Based on the table above, create a network diagram that visually represents the sequence of activities. Ensure all dependencies (finish-to-start) are correctly illustrated. Apply forward pass and backward pass.<\/li>\r\n \t
                    • Indicate each activity's duration, ES, LS, EF, LF, and slack in the network diagram.<\/li>\r\n \t
                    • Which activities are in the critical path?<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t
                    • Crash the Project:<\/strong>\r\n
                        \r\n \t
                      • Crash two activities and explain:\r\n
                          \r\n \t
                        • Which activities will be shortened?<\/li>\r\n \t
                        • Explain how you can shorten activities, for example, by assigning more resources. Explain which resources can be increased or which new resources can be allocated.<\/li>\r\n \t
                        • How will the overall project duration be affected?<\/li>\r\n \t
                        • Indicate if the critical path changed.<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ol>\r\n<\/div>\r\n<\/div>\r\n ","rendered":"
                          \n
                          \n

                          Exercise 1: Resource Allocation and Leveling for the Smart Home Project<\/h2>\n<\/header>\n
                          \n

                          SmartTech Inc., a leading fictional company in home automation, has been contracted to install a comprehensive smart home automation system for a luxury residence. The system includes smart lighting, security cameras, and voice-controlled HVAC systems. The homeowner expects the installation to be completed in 4 weeks to align with their move-in date.<\/p>\n

                          The project involves the following activities:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
                          Activity<\/strong><\/th>\nDescription<\/strong><\/th>\nDuration<\/strong><\/th>\nPredecessors<\/strong><\/th>\nResources Required<\/strong><\/th>\n<\/tr>\n<\/thead>\n
                          A<\/td>\nPerform home assessment<\/td>\n2 days<\/td>\n–<\/td>\n2 assessors<\/td>\n<\/tr>\n
                          B<\/td>\nProcure equipment<\/td>\n7 days<\/td>\n–<\/td>\nProcurement team<\/td>\n<\/tr>\n
                          C<\/td>\nInstall smart lighting systems<\/td>\n3 days<\/td>\nA, B<\/td>\n2 technicians<\/td>\n<\/tr>\n
                          D<\/td>\nInstall security camera systems<\/td>\n2 days<\/td>\nA, B<\/td>\n2 technicians<\/td>\n<\/tr>\n
                          E<\/td>\nInstall HVAC systems<\/td>\n3 days<\/td>\nA, B<\/td>\n2 technicians<\/td>\n<\/tr>\n
                          F<\/td>\nPerform system testing<\/td>\n1 day<\/td>\nC, D, E<\/td>\n1 technician, 1 quality analyst<\/td>\n<\/tr>\n
                          G<\/td>\nProvide homeowner training<\/td>\n1 day<\/td>\nF<\/td>\n1 trainer<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                          The team includes:<\/p>\n

                            \n
                          • 2 assessors<\/li>\n
                          • 3 technicians<\/li>\n
                          • 1 quality analyst<\/li>\n
                          • 1 trainer<\/li>\n<\/ul>\n

                            Tasks and Questions<\/strong><\/h3>\n

                            Part 1: Resource Allocation<\/strong><\/h4>\n
                              \n
                            1. Create a Resource Allocation Plan<\/strong>: Assign resources to each activity based on the requirements and available team members.\n
                                \n
                              • Create a resource allocation table for all activities.<\/li>\n<\/ul>\n<\/li>\n
                              • Identify Overallocations<\/strong>:\n
                                  \n
                                • Review the resource allocation and identify any overallocation issues.<\/li>\n
                                • Highlight the specific activities and days where conflicts occur.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n

                                  Part 2: Resource Leveling<\/strong><\/h4>\n
                                    \n
                                  1. Apply Resource Leveling<\/strong>: Adjust the schedule to resolve overallocation issues using resource leveling techniques.\n
                                      \n
                                    • Reallocate tasks to balance the workload.<\/li>\n
                                    • Adjust the start dates of activities if necessary.<\/li>\n<\/ul>\n<\/li>\n
                                    • Analyze the Impact<\/strong>:\n
                                        \n
                                      • How does resource leveling affect the project\u2019s total duration?<\/li>\n
                                      • Are there any delays in completing the project within the homeowner\u2019s 4-week deadline?<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n
                                          \n
                                        1. <\/li>\n<\/ol>\n<\/div>\n<\/div>\n

                                           <\/p>\n

                                          \n
                                          \n

                                          Exercise 2: Crashing Activities<\/h2>\n<\/header>\n
                                          \n

                                          Below is a WBS for a project that includes durations and predecessors.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
                                          Activity ID<\/strong><\/td>\nActivity<\/strong><\/td>\nPredecessor(s)<\/strong><\/td>\nDuration (days)<\/strong><\/td>\n<\/tr>\n
                                          A<\/td>\nDefine Project Scope<\/td>\nNone<\/td>\n3<\/td>\n<\/tr>\n
                                          B<\/td>\nIdentify Stakeholder Requirements and Conduct Feasibility Study<\/td>\nA<\/td>\n9<\/td>\n<\/tr>\n
                                          C<\/td>\nDevelop Project Charter and Initial Plan<\/td>\nB<\/td>\n7<\/td>\n<\/tr>\n
                                          D<\/td>\nCreate Wireframes and Mockups<\/td>\nC<\/td>\n7<\/td>\n<\/tr>\n
                                          E<\/td>\nPrepare Testing Environment<\/td>\nC<\/td>\n6<\/td>\n<\/tr>\n
                                          F<\/td>\nDevelop Front-End and Back-End Components<\/td>\nD<\/td>\n12<\/td>\n<\/tr>\n
                                          G<\/td>\nIntegrate Components and Test Functionality<\/td>\nE, F<\/td>\n8<\/td>\n<\/tr>\n
                                          H<\/td>\nConduct User Acceptance Testing (UAT)<\/td>\nG<\/td>\n6<\/td>\n<\/tr>\n
                                          I<\/td>\nDeploy and Optimize Performance<\/td>\nH<\/td>\n7<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                                          Tasks and Questions<\/strong><\/h3>\n
                                            \n
                                          1. Draw the Network Diagram:<\/strong>\n
                                              \n
                                            • Based on the table above, create a network diagram that visually represents the sequence of activities. Ensure all dependencies (finish-to-start) are correctly illustrated. Apply forward pass and backward pass.<\/li>\n
                                            • Indicate each activity’s duration, ES, LS, EF, LF, and slack in the network diagram.<\/li>\n
                                            • Which activities are in the critical path?<\/li>\n<\/ul>\n<\/li>\n
                                            • Crash the Project:<\/strong>\n
                                                \n
                                              • Crash two activities and explain:\n
                                                  \n
                                                • Which activities will be shortened?<\/li>\n
                                                • Explain how you can shorten activities, for example, by assigning more resources. Explain which resources can be increased or which new resources can be allocated.<\/li>\n
                                                • How will the overall project duration be affected?<\/li>\n
                                                • Indicate if the critical path changed.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<\/div>\n<\/div>\n

                                                   <\/p>\n","protected":false},"author":256,"menu_order":11,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":[],"pb_section_license":""},"chapter-type":[],"contributor":[],"license":[],"class_list":["post-979","chapter","type-chapter","status-publish","hentry"],"part":232,"_links":{"self":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/979","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/users\/256"}],"version-history":[{"count":8,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/979\/revisions"}],"predecessor-version":[{"id":1090,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/979\/revisions\/1090"}],"part":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/parts\/232"}],"metadata":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapters\/979\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/media?parent=979"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/pressbooks\/v2\/chapter-type?post=979"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/contributor?post=979"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/pressbooks.ulib.csuohio.edu\/projectmanagement2ndedition\/wp-json\/wp\/v2\/license?post=979"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}