The client provided a statement of work (SOW) to the project manager and suggested that the project manager
and team just need to execute the plan. A SOW is a document that defines the scope, deliverables, schedule,
and terms and conditions of a project or contract. A SOW typically includes information such as purpose,
scope of work, location of work, period of performance, deliverables schedule, applicable standards,
acceptance criteria, special requirements, and payment schedule. A SOW can help to establish a common
understanding and agreement between the client and the service provider on what needs to be done and how it
will be done.

The project manager and team should review assumptions and constraints for input to the risk register during the planning phase of a project. Assumptions are statements that are considered to be true for the purpose of planning, but may or may not be valid in reality. Constraints are factors that limit the project scope, time, cost, quality, or resources. Both assumptions and constraints can introduce risks to the project, which are uncertain events or conditions that can have a positive or negative impact on the project objectives. The risk register is a document that records the identified risks, their causes, impacts, probabilities, responses, owners, and status. Reviewing assumptions and constraints can help the project manager and team identify, analyze, prioritize, and plan for the potential risks that may affect the project12.
The other options are not the correct activities that the team should do during the planning phase of a project.
Identifying and assessing stakeholders (option A) is an activity that is done during the initiating phase of a project, not the planning phase. Stakeholders are individuals or groups that have an interest or influence in the project, and their identification and assessment is important to define the project scope, objectives, and success criteria, and to establish a communication plan12. Holding daily status meetings (option B) is an activity that is done during the executing and monitoring and controlling phases of a project, not the planning phase. Daily status meetings are short and frequent meetings where the project team members report on their progress, issues, and plans for the next day. Daily status meetings can help the project manager track the project performance, resolve problems, and communicate updates12. Removing access and planning the project sign-off (option C) is an activity that is done during the closing phase of a project, not the planning phase.
Removing access is a security measure to ensure that the project resources do not have access to the project systems, data, or assets after the project is completed. Planning the project sign-off is a process to obtain the formal acceptance and approval of the project deliverables from the stakeholders and customers12.

Infrastructure as a service (IaaS) offers administrators more direct control over operating systems than other
cloud service models. IaaS is a type of cloud computing service that provides virtualized computing resources
such as servers, storage, network, and operating systems over the internet. IaaS allows users to rent or lease
infrastructure resources on demand and pay only for what they use. IaaS gives users more flexibility and
control over their infrastructure resources and enables them to configure, manage, and customize their
operating systems according to their needs and preferences3

The project manager should review existing artifacts to get an understanding of the purpose of the project.
Existing artifacts are documents or records that provide information about the project background, context,
scope, objectives, requirements, stakeholders, and deliverables. They may include documents such as project
proposal, project charter, business case, feasibility study, statement of work (SOW), or contract. Reviewing
existing artifacts can help to clarify the project vision and expectations and provide a basis for planning and
executing the project.

Explanation
Scrum requires the most availability from the business team among the given options. Scrum is a popular agile framework that organizes work into short iterations called sprints, usually lasting one to four weeks. Scrum emphasizes collaboration between teams, customers, and stakeholders and encourages open communication and transparency throughout the project lifecycle. Scrum requires frequent involvement and feedback from the business team through activities such as product backlog refinement, sprint planning, sprint review, sprint retrospective, and daily scrum meetings.