TOPIC: Opportunity to deliver enhanced capacity

Question :"You are completing the work defined in the project scope statement of a new software development project when a team member points out that you have an opportunity to deliver enhanced capability to the client at no extra cost, time or risk to the project. What should you do NEXT ?

a> Ignore the request of the team member
b> decline to make changes and proceed to deliver exactly what the scope statement sets out
c> go ahead , make changes and surprise client with the extra capability
d> assess the change via the change control process and if approved amend the project scope statement.

I choose option <b>, but the book says option <d>....... any idea why option <d> is best, as I thought GOLD PLATING should not be entertained........????

Subhajit,

Before anything else: Please tell us where this question comes from. As an aspiring PMP you always want to attribute copyright and ensure that you give credit where credit is due.

Thank you!

Hi Cornelius,

This comes from the book "PMP Examination Practice Questions" for the PMBOK Guide, 5th Edition,by "SEAN WHITAKER" ....> question no# 79, page -29.

The answer "d) assess the change via the change control process and if approved amend the project scope statement." is indeed correct. Here are my thoughts:

a> Ignore the request of the team member

It would be wrong to simply "ignore" your team member. Everyone has a right to be heard.

b> decline to make changes and proceed to deliver exactly what the scope statement sets out

By declining the idea of the team member offhand like this you are making two mistakes. (1) You dismiss the input from the team member and he will very likely not give future input. (2) You ignore the opportunity to deliver the best possible solution to the customer without even consulting with the customer.

c> go ahead , make changes and surprise client with the extra capability

This is gold plating. Just making the changes without following proper process is wrong.

d> assess the change via the change control process and if approved amend the project scope statement.

This is the correct approach because (1) you are acknowledging that the input from your team member is valid, (2) you accept the fact that change requests can come from any and every stakeholder on the project, (3) you are guiding the change request into the appropriate change control process, and (4) as part of this process you only implement the change AFTER it has been approved by the responsible change control body (which likely includes your customer).