When developing a coaching model to support and recognize team members' growth, it is essential for the project manager to consider the individual and personal objectives of the team members. This personalized approach ensures that the coaching strategy is aligned with the unique needs and goals of each team member, fostering an environment of growth and development. Tailoring the coaching to individual objectives also helps in maximizing the effectiveness of the coaching process23.
References:
The PMI's guide on an effective project manager coaching approach emphasizes the importance of considering individual needs and aligning them with the coaching process2.
Discussions on ExamTopics related to PMP coaching strategies also highlight the significance of focusing on individual and personal objectives when defining a coaching strategy1.

According to the PMBOK Guide, a change request is a formal proposal to modify any document, deliverable, or baseline. Change requests are processed through the Perform Integrated Change Control process, which involves reviewing, analyzing, approving, or rejecting changes. The project manager should follow the change management process and work with procurement if needed to deal with the new requirement from the key stakeholder. The project manager should assess the impact of the change on the project scope, schedule, cost, quality, risk, and other aspects, and obtain approval from the appropriate authority before implementing the change. The project manager should also communicate the change to the subcontracting company and negotiate any contractual modifications if necessary. The project manager should not engage an arbitrator, add the change to the next sprint, or allocate resources to work on the new feature immediately, as these actions may bypass the change management process, create conflicts, or disrupt the project plan. References:
PMBOK Guide, 6th edition, pages 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129,
130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151,
152, 153...
PMI-PBA Guide, pages 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37,
38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53...

Schedule crashing is a technique to shorten the project schedule by adding more resources or working overtime, without changing the project scope1. This can help improve the Schedule Performance Index (SPI) and Cost Performance Index (CPI) by completing more work in less time and within budget. The other options are not relevant to the question. Fast tracking is a technique to overlap project phases or activities to reduce the project duration, but it may increase risks and costs2. Earned schedule and earned value are methods to measure project performance, not techniques to improve it3 . References: 1: PMBOK Guide, 6th edition, p. 215 2: PMBOK Guide, 6th edition, p. 216 3: PMBOK Guide, 6th edition, p. 267 : PMBOK Guide,
6th edition, p. 260

This question belongs to the Business Environment domain because it concerns compliance with organizational governance and approval authority. PMI governance guidance explains that project governance is aligned with the organization's governance model, and PMI methodology material highlights that approval processes should define who has authority, how approvals flow, and how funding and decisions are authorized. Procurement itself is a formal acquisition process governed by contractual and organizational rules.
The best response is to agree on a purchasing approval escalation method according to organizational governance. This ensures the project manager follows the correct approval thresholds, routing, and decision rights for high-value equipment purchases. Option B attempts to bypass governance. Option C may be inappropriate because not all purchase approvals automatically belong to the sponsor; the authority should follow established organizational rules. Option D is poor project management because equipment choices should be based on project needs and approved procurement processes, not on avoiding approval requirements. PMP-style logic emphasizes working within governance boundaries and establishing proper escalation and authorization paths before purchases are made.

When resource constraints conflict with the full scope of stakeholder requirements, the project manager should first facilitate a requirements prioritization workshop. This allows stakeholders to collaboratively identify the most critical features and align scope with available resources.
The PMBOK Guide - Seventh Edition emphasizes value delivery and stakeholder collaboration in prioritizing scope based on constraints. Requirements workshops are standard tools in scope planning and requirements elicitation.
Option B makes unilateral scope decisions, which could lead to stakeholder dissatisfaction.
Option C is valid, but only after the team jointly prioritizes based on business need.
Option D skips proper prioritization and assumes the budget can be increased, which may not be feasible.
References:
PMBOK Guide - Seventh Edition, Scope and Planning Performance Domains
PMI Business Analysis Practice Guide - Prioritization Techniques
##############################################