Create a report detailing the impact of scope changes on project parameters such as cost, quality, and schedule
Explanation: Any scope changes in a project must go through the Integrated Change Control process to determine the impact on project parameters such as cost, quality and schedule. The changes must then be presented to the Change Control Board for their review. Then, all approved changes must be planned, and resources must be allocated. Therefore, the first step for Jared is to create a report detailing the impact of scope changes on project parameters such as cost, quality and schedule. [PMBOK® Guide 6th edition, Page 115]
Project charter
Explanation: The summary milestone schedule is normally included as part of the project charter, which documents the business need, understanding of customer’s needs, and other high-level items. [PMBOK® Guide 6th edition, Page 81]
The changes are documented and they follow the change management process to obtain an Approved Change request.
Explanation: All changes should be formally documented in writing. Any changes that are verbally discussed but undocumented should not be processed or implemented. [PMBOK® Guide 6th Edition, Page 113]
Divide the tasks the SME was performing into smaller components and see how these smaller components can now be delivered to the project.
Explanation: The problem at hand is that we are losing a SME that was performing multiple tasks for the project, and now we are unable to find a replacement. The best strategy at this stage is to divide the tasks the SME was performing into smaller components and see how these smaller components can now be delivered to the project (alternatives analysis). For example, you may acquire an experienced stakeholder from the user group for user relationship management and a senior business analyst from the market with sufficient technical knowledge to help collect and validate system requirements in collaboration with the acquired experienced stakeholder. [PMBOK® Guide 6th edition, page 111]
Supportive action
Explanation:
Change requests can include preventive or corrective actions and defect repairs. Supportive action is not a valid choice. [PMBOK® Guide 6th edition, Page 96]
Project charter
Explanation:
The project has just been approved and all Andy has at the moment is the project charter itself. The project charter has a preliminary list of project stakeholders. Andy can use this list as a starting point. [PMBOK® Guide 6th edition, Page 81]
Corrective action
Explanation:
A corrective action is anything that needs to be done to bring the project back on track. Care must be taken not to confuse corrective action with preventive action. Corrective action is taken to correct the results of a non-conformance event that happened in the past. Whereas, preventive action is taken to avoid or mitigate any potential non-conformance event that may occur in the future. [PMBOK® Guide 6th edition, Page 96]
Initiate the formal change control process to find the impact of his recommendation
Explanation: Change requests should always be recorded in written form and entered in the change management system to determine the impact of the change on the scope, budget, schedule and quality. Thus, Joe must initiate the formal change control process. After approval from the change control board, Joe can allocate resources and funds to implementing the change. Hence, Joe must initiate the change first. [PMBOK® Guide 6th edition, Page 113]
Stress on documentation
The problem at hand is high employee turnover. If you have no control over this issue, long-term contracts and virtual teams are not going to help. One of the issues with high employee turnover is loss of undocumented project knowledge with each departing employee. This issue can be mitigated by stressing on maintaining project documentation. [PMBOK® Guide 6th edition, page 107]
Initiate a preventive action to reduce the probability of negative consequences associated with the poor quality of the road
Explanation: There is no need to update the quality management plan since the problem is with the workmanship and not with the quality management plan. The scenario is asking for an action that will ensure future compliance, i.e. a preventive action. Note that since all of the reported defects have been fixed, there is no need for any corrective action or defect repair at this stage. [PMBOK® Guide 6th edition, Page 96]