The number of items in the backlog can be determined by looking at the "Commitment" column for each
sprint in the provided chart. For Sprint 5, there is a commitment of completing 23 items, which is the highest
among all sprints. This indicates that there are at least 23 items in the backlog to be worked on. This is
consistent with the concept of agile project management, which allows for changes and additions to the project
scope based on customer feedback and changing requirements. References = CompTIA Project+ PK0-005
Certification Study Guide, Chapter 14: Agile Project Management, page 321. CompTIA Project+ Cert Guide:
Exam PK0-004, Chapter 9: Agile Project Management, page 287

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 can help 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.

The project manager should have generated a contingency plan first to alleviate the impact of this issue prior to deployment where a major malfunction resulted in an inoperative product condition during a code implementation. A contingency plan is a plan that outlines alternative courses of action or strategies to deal with potential problems or risks that may occur during a project. A contingency plan can help to prevent or minimize the negative impacts of unforeseen events or issues on the project objectives and deliverables and ensure business continuity and stability.

The project manager should notify the functional manager that resources are released after completing a
project successfully in a functional organization. A functional organization is a type of organizational structure
where employees are grouped by their functions or specialties, such as finance, marketing, or engineering. In a
functional organization, the functional manager has more authority and control over the resources than the
project manager. Therefore, the project manager should inform the functional manager when the resources are
no longer needed for the project and can be reassigned to other tasks or projects.

The product owner is the person who is responsible for managing the product backlog, which includes adding,
removing, or changing items based on stakeholder feedback and business value. The product owner is also the
one who can collaborate with the development team and the scrum master to decide if a change can be
accommodated in the current sprint or deferred to a future sprint. Therefore, the stakeholder should have asked
the product owner to request the change instead of the team member, who is not authorized to make changes to
the sprint backlog12.