In situations where a stakeholder objects to a project, it is crucial for the project manager to assess the impact of the stakeholder's concerns and engage with them properly. This involves understanding the stakeholder's perspective, the reasons behind their objections, and the potential influence they have on the project. By doing so, the project manager can address the concerns in a manner that respects the stakeholder's legacy ties while also guiding the project towards its objectives. Effective stakeholder engagement is a key aspect of project management and business analysis, as it helps in managing expectations, resolving conflicts, and ensuring that all parties are aligned with the project's goals.
: (Project Management Institute. (n.d.). A Guide to the Project Management Body of Knowledge (PMBOK Guide) - Sixth Edition; Project Management Institute. (n.d.). PMI's Professional in Business Analysis (PMI- PBA).)

In a matrixed organization, the project manager does not have full authority over the resources and must negotiate with the functional manager for their availability. In this scenario, the project manager should first engage with the functional manager to discuss the details and obtain the required support for testing the software. This approach promotes collaboration and ensures that all parties are aware of the project needs and constraints. References: Project Management Professional (PMP) Reference Materials source and documents:
PMI - Project Management Professional (PMP), PMI - PMBOK Guide and Standards, Professional in Business Analysis Reference Materials study guide: PMI - Professional in Business Analysis
1of5
Show learn more suggestions

When a customer cannot clearly define a major piece of functionality, attempting to lock down detailed requirements up front typically increases rework and delays value. The best approach is to use prototyping to make requirements tangible and accelerate learning. Building a prototype (B) enables rapid feedback, clarifies expectations, and reduces ambiguity by showing the customer working behavior rather than asking them to specify everything in words. This aligns with iterative delivery and progressive elaboration: deliver something small quickly, validate understanding, and refine. Assigning a BA to write detailed requirements (A) can help, but it still depends on the customer's ability to articulate needs; it may create false certainty. Adding time
/resources to estimating (C) is a delay strategy, not value delivery. Raising a risk (D) is appropriate to document uncertainty, but it does not solve the problem or create momentum. Prototyping supports early value, improves stakeholder alignment, and reduces failure risk by validating assumptions before full-scale build.

According to the PMBOK Guide, the project lead should manage stakeholder expectations and engagement throughout the project life cycle. The project lead should also support the agile team's decisions and authority regarding the product scope and releases. The agile team is responsible for delivering valuable and functional products to the customer in short iterations. Therefore, the project lead should work with the stakeholder to understand what the concerns are while at the same time conveying the benefits of incremental deliveries. The project lead should also communicate the value proposition and the vision of the product to the stakeholder and seek their feedback and collaboration. References: PMBOK Guide, 6th edition, pages 18, 37, 51-52, 286-
287.

According to the PMBOK Guide, 7th edition, section 8.1.3, page 269, the Kanban board is a visual tool that shows the status of work items and the flow of work through different stages. The Kanban board helps the team to limit the work in progress, identify bottlenecks, and optimize the delivery of value. When a project sponsor requests to prioritize a new backlog item, the project manager should communicate the impact of starting the item with the project sponsor, as this may affect the existing work items, the team capacity, and the project schedule. The project manager should also seek to understand the rationale and urgency of the request, and negotiate a mutually agreeable solution with the project sponsor. The other options are not the best actions for the project manager, as they do not address the need to communicate and collaborate with the project sponsor, who is a key stakeholder and decision maker. Decomposing the item immediately and beginning work may cause disruption and confusion to the team and the project. Discussing the impact of starting the item with the team may be helpful, but it does not involve the project sponsor who made the request. Finishing the small tasks in progress before decomposing the item may delay the delivery of value and the satisfaction of the project sponsor. References:
* PMBOK Guide, 7th edition, section 8.1.3, page 269
* PMI-PBA Exam Practice Test and Study Guide, 2nd edition, chapter 8, page 179