A stakeholder has rejected a project's deliverable because it does not meet the original business...

The best approach to resolve this issue is to suggest re-estimating the requirement and following the change control process. This would allow the project team to assess the impact of the change request, evaluate the feasibility and cost of the modification, and obtain the approval of the stakeholders before implementing the change. A change control process is a method used to manage change requests for projects and big initiatives. It’s part of a change management plan, which defines the roles for managing change within a team or company1. Meeting with the customer and apologizing for misunderstanding the business’s need is not sufficient, as it does not address the root cause of the problem or propose a solution. Providing the stakeholder with a copy of the approved requirements baseline and moving forward without making a change is not acceptable, as it ignores the stakeholder’s feedback and dissatisfaction. Requiring development resources to work overtime to modify the deliverable to satisfy the stakeholder is not advisable, as it may compromise the quality of the work, increase the project cost and risk, and demoralize the team. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline2, PMI Guide to Business Analysis3, Business Analysis for Practitioners: A Practice Guide4, What Is a Change Control Process? (with Example Change Log)