During the development of a new mobile application, the client requests an additional feature that was not included in the original project scope. The client insists that the schedule and budget must remain unchanged. As the project manager, what is the best course of action?
Treat it as a project change and inform the client that changes to the scope cannot be accommodated without altering the schedule or budget.
Recognize it as a project change and deny the request due to constraints in schedule and budget.
Consider it a product change and proceed to implement the new feature since the client requested no changes to schedule or budget.
Classify it as a product change and initiate the change control process to evaluate the impact and adjust the project plan accordingly.
Adding a new feature that was not part of the original scope is a product change. Even if the client wants the schedule and budget to remain unchanged, the project manager should initiate the change control process to evaluate the impact of this request on the project's objectives. This assessment may reveal that the new feature cannot be accommodated without affecting the schedule, budget, or quality, and discussions with the client can then address potential adjustments or trade-offs. Proceeding without proper evaluation could jeopardize the project's success.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is a change control process?
Open an interactive chat with Bash
What are the implications of scope changes on a project?
Open an interactive chat with Bash
What are the differences between project change and product change?