Assessing the resource pool is the process of identifying and evaluating the availability, skills, and costs of the
resources needed for the project. The PM reviews the SOW from the contractor to understand the scope and
requirements of the project, grades the full-time equivalents' resumes to determine their qualifications and
suitability for the project, evaluates the titles and salaries to estimate the budget and allocation of the
resources, and estimates the number of hours for each milestone by full-time equivalents to plan the schedule
and workload of the project12.

Explanation
The project manager should develop a rollback plan next after determining the appropriate maintenance window in the operational infrastructure change process. A rollback plan is a contingency plan that describes how to revert to the previous state of the system or infrastructure in case of a failure or disruption during the change implementation. A rollback plan can help to minimize the impact and risk of the change and ensure business continuity and stability.

SaaS, or Software as a Service, is a type of cloud computing that provides ready-to-use software applications
over the internet. The software is hosted and managed by the service provider, and the users do not have to
install, update, or maintain it. SaaS is suitable for the global franchise because it can provide a unified solution
that can be accessed from anywhere, anytime, and on any device. SaaS can also provide real-time operation
reports without requiring the intervention of the country franchise managers. SaaS can offer benefits such as
scalability, flexibility, cost-effectiveness, and security for the global franchise123. References = CompTIA
Project+ Study Guide: Exam PK0-005, 3rd Edition, Chapter 4: Project Communications, p. 143; Types of
Cloud Computing - SaaS vs PaaS vs IaaS - AWS; What are the different types of cloud computing? | Google
Cloud; IaaS vs. PaaS vs. SaaS | IBM

See the Explanation for the solution.
Explanation:
Part 1:
Change Control Process:
* Consult the RACI matrix.
* Define new requirements and record changes.
* Assess the schedule, risk, and cost.
* Perform a demonstration.
* Obtain a sign off.
* Update and test the deliverable.
* Make an announcement on the company portal.
The change control process is a sequence of steps that helps to manage and document any changes or modifications to a project scope, schedule, cost, quality, or resources. The change control process typically involves the following steps:
* Consult the RACI matrix. A RACI matrix is a tool that defines and clarifies the roles and responsibilities of each team member for each task or activity in a project. RACI stands for responsible, accountable, consulted, and informed. Consulting the RACI matrix can help to identify who needs to be involved or informed about the change request and how to communicate with them.
* Define new requirements and record changes. The new requirements and changes are the details of what needs to be modified or added to the project deliverables or objectives based on the customer feedback or request. Defining and recording the new requirements and changes can help to communicate and justify the need and rationale for the change and its implications on the project scope and quality.
* Assess the schedule, risk, and cost. The schedule, risk, and cost are the aspects of the project that may be affected by the change request. Assessing the schedule, risk, and cost can help to determine the impact and feasibility of the change and identify any possible alternatives or corrective actions to minimize or avoid its negative effects.
* Perform a demonstration. A demonstration is a presentation or show of how the modified or updated deliverable works or meets the customer expectations or requirements. Performing a demonstration can help to validate and verify that the change request has been implemented correctly and effectively and to obtain feedback or approval from the customer or stakeholders.
* Obtain a sign off. A sign off is a formal acceptance and approval of the change request and its deliverables from the customer or stakeholders. Obtaining a sign off can help to confirm that the change request has been completed successfully and satisfactorily and to close the change control process.
* Update and test the deliverable. The deliverable is the product or service that is produced or provided by the project. Updating and testing the deliverable canhelp to ensure that it meets the quality standards and criteria and that it works as expected after implementing the change request.
* Make an announcement on the company portal. The company portal is a platform or channel that allows internal communication and collaboration among employees within an organization. Making an announcement on the company portal can help to inform and update other team members or departments about the change request and its outcomes and to share any lessons learned or best practices from the change control process.
Part2:
* Risk register: A risk register is a document that identifies, analyzes, and records the potential risks or
* uncertainties that may affect a project. Updating the risk register can help to capture any new or modified risks that may arise from the change request and to plan and implement appropriate risk responses.
* Schedule:A schedule is a document that shows the planned start and end dates, durations, dependencies, and progress of each task or activity in a project. Updating the schedule can help to reflect any changes or adjustments to the project timeline or milestones that may result from the change request and to monitor and control the project performance and delivery.
* Statement of work:A statement of work (SOW) is a document that defines the scope, deliverables, schedule, and terms and conditions of a project or contract. Updating the SOW can help to document any changes or additions to the project scope or deliverables that may be requested or agreed upon by the customer or stakeholders and to ensure alignment and agreement on what needs to be done and how it will be done.
* Change log:A change log is a document that tracks and records any changes or modifications that are made to the project scope, schedule, cost, quality, or resources during a project. Updating the change log can help to document the change request, approval, implementation, and impact of each change and ensure traceability and transparency.

Mitigate is a risk strategy that involves taking actions to reduce the probability or impact of a risk. By applying
new updates to a program in a sandbox environment, the software engineer is testing the changes before
implementing them in the actual system, thus minimizing the chance of errors or failures that could affect the
project1.