Pragmatic Agile Workshop

Project Scope statement

Discuss PMP doubts, tips and lesson learned. iZenBridge makes PMP® Certification easy
gagan1986
Posts: 11
Joined: Sun Jun 26, 2016 5:17 am

Project Scope statement

Postby gagan1986 Thu Mar 16, 2017 12:22 am

Q. You are managing a six-month project and have held bi-weekly meetings with your project stakeholder. After five and half month of work, the project is on schedule and budget, but the stakeholder are not satisfied with the deliverables. This situation will delay the project completion by one month. The most important process that could prevent this situation is:

A. Monitor and control risks.
B. control schedule.
C. Define Scope.
D Control Scope

Rita claims; Option C.

I believe it should be D. As we can do variance analysis in control scope and create change request in order to prevent this situation.
manishpn
Expert
Expert
Posts: 2125
Joined: Sat Jan 04, 2014 3:55 pm

Re: Project Scope statement

Postby manishpn Thu Mar 16, 2017 7:38 pm

Kindly provide your reasoning for option #D
Br,
Manish P
PMP, PMI - ACP, SAFe Agilist
http://www.izenbridge.com/blog/7-effect ... ification/
VCAB
Participant
Participant
Posts: 71
Joined: Wed Dec 21, 2016 4:26 pm

Re: Project Scope statement

Postby VCAB Fri Mar 24, 2017 12:46 am

Q. You are managing a six-month project and have held bi-weekly meetings with your project stakeholder. After five and half month of work, the project is on schedule and budget, but the stakeholder are not satisfied with the deliverables. This situation will delay the project completion by one month. The most important process that could prevent this situation is:

A. Monitor and control risks.
B. control schedule.
C. Define Scope.
D Control Scope

C is the answer (planning is proactive and the question is asking for "prevention"). So we have to look within the planning process group. If you look at the other answers, they are all controlling processes. There is the key phrase "the customer is not satisfied with the deliverable" there are several reason why customers are not happy with the deliverables, among them are, wrong requirement collected, misunderstand of the requirement by the project team, obtaining requirement from the wrong stakeholder (very often these lead to products completed and unhappy customers)---these are all within the collect requirement and the primary output of that process are requirement doc and traceability matrix, both of which are input into the define scope. So in this doc (SCOPE STATEMENT), you have the product requirement (which the customer is unhappy with) and the project mgt processes to obtain the desired requirement.

Return to “PMP® Open Forum”

Who is online

Users browsing this forum: Google [Bot] and 8 guests