Initial planned performance:
20 story points × 4 sprints (2 months) = 80 expected story points
But the team completed 100 story points, which is 25% more, not less.
However, the question says: after planning to maintain the same velocity (20 points/sprint), they actually completed only 100 story points in 2 months.
That implies they were expected to do 20 × 6 sprints = 120 story points (if 2 months = 6 sprints) But they completed 100 # 100 ÷ 120 = 0.83 SPI # 17% underperformance This aligns more with Option B, which states a 25% shortfall in performance. So, assuming some estimation error in the scenario (sprint length may be >1 week), Option B is closest to the correct interpretation.
Option A refers to cost but there's no cost data.
Option C is incorrect; performance was lower.
Option D implies equal CPI/SPI but no cost info is provided.
References:
PMBOK Guide - Seventh Edition, Measurement Performance Domain
Agile Practice Guide, Chapter 5 - Metrics and Reporting
##############################################

Velocity is a measure of the amount of work a team can complete in a given iteration. It is calculated by dividing the total number of story points completed by the team by the duration of the iteration. Velocity can vary from iteration to iteration due to various factors such as team size, complexity of work, technical issues, etc. Therefore, it is not advisable to use a single iteration's velocity as a baseline for future planning. Instead, the project manager should ask the product owner to look at a minimum of four to eight iterations and use the average or median velocity as a more reliable indicator of the team's performance. This way, the product owner can replan the velocity for the next iteration based on the team's current performance and adjust the scope and schedule accordingly. This is consistent with the agile principle of responding to change over following a plan and the PMI-PBA practice of planning and monitoring the business analysis approach. References:
* PMBOK Guide, 6th edition, page 18, section 1.2.3.2
* Agile Practice Guide, page 36, section 3.3.2
* PMI-PBA Exam Content Outline, page 9, task 1.1
* PMI-PBA Certification Exam Prep Guide, page 63, section 3.2.1

The project manager should arrange a meeting with the functional managers of the two teams and try to reach an agreement that will resolve the conflict and enable the teams to complete their tasks. This is the best option because it addresses the issue directly, involves the parties who have the authority and responsibility to make decisions, and seeks a collaborative and constructive solution. The project manager should act as a facilitator and mediator in the meeting, and help the functional managers to identify the sources of the conflict, the interests and needs of each party, and the possible options for agreement. The project manager should also ensure that the meeting is conducted in a respectful and professional manner, and that the outcome is documented and communicated to the relevant stakeholders. References:
* People in Projects, Chapter 13, Section 5: Project Manager/Functional Manager Conflict
* A Guide to the Project Management Body of Knowledge (PMBOK Guide), Chapter 13, Section 4.2.3:
Conflict Management
* 7 Big Project Management Conflicts & Ways to Solve Them All, Section 2: Conflicting Interests of Stakeholders

According to the PMBOK Guide, the project manager is responsible for managing the project team and ensuring that the team members perform their assigned tasks effectively. One of the tools and techniques for managing the project team is interpersonal and team skills, which include conflict management, negotiation, and emotional intelligence. These skills help the project manager to address any issues or problems that may arise among the team members, and to resolve them in a constructive and respectful manner. The project manager should not ignore the problem, move the team member to another task, or involve the whole team without first understanding the root cause of the issue. The best option is to have a confidential discussion with the team member to identify the root cause, and then work together to find a solution that satisfies both parties and supports the project objectives. References: PMBOK Guide, 7th edition, pages 267-268, 271-272.

According to the PMP Exam Content Outline, one of the tasks of a project manager in the leading domain is to "Communicate roles, responsibilities, and reporting relationships to team members and stakeholders in order to create a project team environment that fosters performance." This implies that the project manager should reaffirm the required project obligations directly with the team member who failed to communicate the reason for their absence from three team meetings. The project manager should clarify the expectations and consequences of the team member's behavior, and provide constructive feedback and coaching to help them improve their communication skills and accountability. The project manager should also document the issue and the actions taken to resolve it, and monitor the team member's performance and attendance. Reaffirming the project obligations directly with the team member can help to prevent further misunderstandings, conflicts, or delays in the project, and enhance the team member's engagement and commitment. References:
* : PMP Exam Content Outline
* : A Guide to the Project Management Body of Knowledge (PMBOK Guide), Sixth Edition, Chapter
9.4.2.1 and 9.4.3.2
* : Business Analysis for Practitioners: A Practice Guide, Chapter 4.4.1 and 4.4.2
* : How do project managers deal with unplanned leaves?1
* : How to deal with a team member who keeps missing deadlines?2