When trust or satisfaction is an issue with a stakeholder-especially one as critical as the sponsor-the first step is direct communication. A one-on-one meeting to understand expectations, concerns, and establish rapport is essential. This aligns with stakeholder engagement best practices, where early and proactive engagement is prioritized.
The PMBOK Guide - Seventh Edition, in the Stakeholder Performance Domain, recommends identifying and analyzing stakeholder needs and initiating communication to build or maintain relationships.
Option A is too process-oriented and premature before establishing rapport.
Option B is informative but lacks interpersonal connection.
Option C provides updates but does not address dissatisfaction or rebuild trust.
References:
PMBOK Guide - Seventh Edition, Stakeholder Engagement Performance Domain PMBOK Guide - Sixth Edition, Section 13.3: Manage Stakeholder Engagement
-

To answer this question, we need to calculate the earned value (EV), the planned value (PV), and the actual cost (AC) of the project based on the given information. Then, we can compare them to determine the project status in terms of schedule and cost performance.
The earned value (EV) is the monetary value of the work completed so far. It can be calculated by multiplying the percent complete of the project by the budget at completion (BAC), which is the total approved budget for the project. The BAC can be obtained by adding the approved work package cost estimates, the contingency reserves, and the management reserves. In this case, the BAC is:
BAC=9500+500+(10%×500)=10550
The EV is then:
EV=50%×10550=5275
The planned value (PV) is the monetary value of the work that was planned to be completed by a certain date.
It can be calculated by multiplying the planned percent of the project by the BAC. In this case, the PV is:
PV=40%×10550=4220
The actual cost (AC) is the monetary value of the work actually performed. It is given as:
AC=4500
To determine the project status, we can use the cost variance (CV) and the schedule variance (SV) formulas.
The CV is the difference between the EV and the AC, and it indicates whether the project is under budget or over budget. A positive CV means the project is under budget, while a negative CV means the project is over budget. The CV is:
CV=EV#AC=5275#4500=775
The SV is the difference between the EV and the PV, and it indicates whether the project is ahead of schedule or behind schedule. A positive SV means the project is ahead of schedule, while a negative SV means the project is behind schedule. The SV is:
SV=EV#PV=5275#4220=1055
From the CV and SV values, we can conclude that the project is under budget and ahead of schedule. To find the percentage of deviation from the planned cost and schedule, we can use the cost performance index (CPI) and the schedule performance index (SPI) formulas. The CPI is the ratio of the EV to the AC, and it measures the cost efficiency of the project. A CPI greater than 1 means the project is under budget, while a CPI less than 1 means the project is over budget. The CPI is:
CPI=ACEV=45005275=1.17
The SPI is the ratio of the EV to the PV, and it measures the schedule efficiency of the project. A SPI greater than 1 means the project is ahead of schedule, while a SPI less than 1 means the project is behind schedule.
The SPI is:
SPI=PVEV=42205275=1.25
From the CPI and SPI values, we can calculate the percentage of deviation from the planned cost and schedule by subtracting 1 and multiplying by 100. The percentage of deviation from the planned cost is:
(CPI#1)×100=(1.17#1)×100=17%
The percentage of deviation from the planned schedule is:
(SPI#1)×100=(1.25#1)×100=25%
Therefore, the project cost is 17% lower than planned, and the project schedule is 25% ahead of planned.
Among the given options, the closest one is B. The project cost is 10% lower than planned.
References:
PMBOK Guide, 6th edition, part 1, ch. 7.4.2.1, pp. 267-268.
PBA Guide, 1st edition, part 2, ch. 6.3.2.1, pp. 140-141.

According to the Professional in Business Analysis (PMI-PBA) Guide, a requirements traceability matrix is a table that links requirements to their origin and tracks them throughout the project life cycle. A requirements traceability matrix helps to ensure that all requirements are addressed by the project deliverables, and that any changes to the requirements are reflected in the project scope, schedule, cost, quality, and risk. In this scenario, the project manager should review the requirements traceability matrix with the concerned stakeholder to verify if the requirement in question is indeed missing or not. This would help to clarify the source, scope, and status of the requirement, and to identify any gaps, inconsistencies, or conflicts between the requirements and the deliverables. This would also help to avoid any misunderstandings, miscommunications, or assumptions that could lead to stakeholder dissatisfaction or project failure. Checking the approved list of requirements, working with the stakeholder to improve the acceptance criteria, or discussing additional requirements are actions that should be taken after the review of the requirements traceability matrix, not before. These actions do not address the root cause of the situation, which is the possible discrepancy between the requirements and the deliverables. References: (Professional in Business Analysis Reference Materials source and documents)
* Professional in Business Analysis (PMI-PBA) Guide, Chapter 4, Section 4.3.1.3
* A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Seventh Edition, Chapter 5, Section 5.2.2.3
* The Standard for Project Management - Seventh Edition, Chapter 3, Section 3.2.2.3

One of the primary responsibilities of the Scrum Master is to remove impediments that may block the team from achieving its sprint or iteration goal. If a dependency is discovered late in the project, swift and direct collaboration is required to ensure delivery continuity. Initiating communication with the dependent team aligns with the Scrum Master's role as a servant leader and facilitator.
According to the Agile Practice Guide (Chapter 3 - Agile Roles), the Scrum Master works across teams and organizational boundaries to resolve external dependencies that may block the team. It is not the sole responsibility of the Product Owner or individual team members to manage these external issues.
Option A shifts responsibility inappropriately to the Product Owner.
Option B doesn't resolve the dependency but merely postpones or reorders work.
Option D fails to address the systemic coordination needed; it may be helpful later but isn't the primary step.
References:
Agile Practice Guide, Section 3.1 - Scrum Master Responsibilities
PMBOK Guide - Seventh Edition, Team Performance Domain
-

In project management, it's crucial to address performance issues promptly and constructively. Providing feedback and coaching the team member during the iterative design stage can help improve their performance12. This approach aligns with the principles of continuous improvement and learning, which are key aspects of iterative design stages. Coaching involves helping the team member understand their areas of improvement, providing guidance on how to enhance their skills, and offering support as they work towards improving their performance34. This not only helps the individual team member but also contributes to the overall performance and success of the project12.
References:
Teams and Project Performance - Project Management Institute1
Building and Leading High-Performing Teams | PMI2
How to Improve Project Team Performance | Villanova University3
Team Performance Assessment - Lovepmp4