MGT2 TASK 3 Monitoring and Controlling IT Project Management,100% CORRECT, Exams of Information and Communications Technology (ICT)

Download MGT2 TASK 3 Monitoring and Controlling IT Project Management,100% CORRECT and more Exams Information and Communications Technology (ICT) in PDF only on Docsity!

MGT2 TASK 3 Monitoring and

Controlling

IT Project Management (Western Governors

University)

MGT2_KKM1: Monitoring and Controlling Monitoring and Controlling Template A. Risk Assessment Risk Description Likelihood (L, M, H) Impact (L, M, H) Responsible Person Prevention/Mitigation Strategy Existing power lines may not meet the company’s standards for its’ uses. H H Eva Miller Have the facilities team investigate the power lines. Current configuration will work short-term, but installation of new cables should be presented as an additional project/task. Additional equipment may be needed for storage and transfer of data L M Omar Patel Have the network team investigate. Purchase additional equipment if necessary for task completion. Duplicate files have been found and may be caused by previous backup problems. L L Sara Phan Since the files are from many years in the past, there is little impact to the current project if the files are found to be duplicates from that event. Preserve or purge duplicate files. Account request could take significantly longer than expected to have the QA engineers registered as authorized users. M H Ren Sousa There is still a month until the QA engineers need access. The process for account approval should be started as soon as possible in preparation for their tasks. Potential working hours during Holidays. M L Ahmed Williams Address expected scheduling in advance of the holidays and designate employees to days to keep on schedule. Key: L=Low, M=Medium, H=High B. Gantt Chart PDF attached and submitted. C1. Earned Value Analysis

MGT2_KKM1: Monitoring and Controlling Monitoring and Controlling Template Team EV AC PV CV CPI SV SPI Premigration planning

Storage $7,290.36 $7,425.00 $10,800.00 $(134.64) 0.98 $(3,509.64) 0. Off-site cloud system $3,166.80 $2,925.00 $3,250.00 $241.80 1.08 $(83.20) 0. Testing $3,762.42 $3,900.00 $3,532.26 $(137.58) 0.96 $230.16 1. Migration - - - - 1.00 - 1. Total $26,442.78 $26,775.00 $37,218.62 $(332.22) 0.99 $(10,775.84) 0. C2. Earned Value Projections Team EAC ETC Est. Duration Est. Completion Date Premigration planning $24,592.58 $12,067.58 36 Days 19-Sep Storage $12,832.70 $5,407.70 32 Days 13-Sep Off-site cloud system $36,022.17 $33,097.17 62 Days 11-Nov Testing $45,401.63 $41,501.63 59 Days 8-Nov Migration $14,400.00 $14,400.00 24 Days 15-Dec Total $133,249.07 $106,474.07 15-Dec C3. Discussion of Earned Value Analysis and Projections Based on the earned value analysis and projects that was conducted, several conclusions can be drawn about the various team’s progress. The CPI of the premigration, storage, and testing teams are below 1.0. This indicates that those teams have spent more money on the projects progress than what was expected at this point in time. The migration team has not conducted any work yet and has a 1.0 CPI as an anticipated projection. The Off-site cloud system team has managed to save money on their project, showing a 1.08 CPI. This has helped to offset the below 1.0 CPI of the other teams, bringing the average to 0.99. This places the overall project just slightly over budget by $332.22. he scheduling performance index shows a similar trend of three teams falling behind, one team ahead of schedule, and one that has not started work. The Premigration team hit a significant setback at the start of the project due to old wiring needing to be replaced at the new building. This caused a cascading effect on the timelines of the other teams. The testing team has managed to stay ahead of schedule. The migration team has not performed any work so its estimated duration and estimated completion date have not changed. Depending on the critical path, the migration team may fall significantly behind the expected completion date. The overall project has a 0.71 SPI indicating that the project is behind schedule and will cause the project completion to be pushed 4-8 weeks further out. The 0.71 SPI indicates an extension of 41 days to the estimated completion date. Unless the impact of the teams running behind schedule is mitigated, the project will exceed the hard deadline of January 1.

MGT2_KKM1: Monitoring and Controlling Monitoring and Controlling Template teams and tasks to further fall behind. By hiring additional employees these tasks will be completed fast and, hopefully, get the project back on schedule. The off-site cloud system team is under budget but behind on schedule. To bring this team’s tasks back on schedule, hiring additional employees or implementing overtime will help to bring the team back on schedule. If the team stays behind schedule, the project may pass the hard deadline set by the employer. Due to this deadline, bringing the project on schedule is more important than the cost of the project.