While giving practice tests on various websites, I've compiled a list
of questions for which I do not fully understand the reason why the
answer is the answer given.
I'll be giving PMP exam this weekend 6/4 and appreciate help on the
questions below:
Thanks
Rajat
 

As a project manager, your first priority in relation to scope changes
is to-------------      A       B
A) manage each scope change immediately upon becoming aware of the
request, in accordance with scope change control procedures
B) discourage and prevent unnecessary changes
C) ensure that all scope changes are properly documented
D) discuss each scope change request with your project sponsor to
ensure you have their approval before requesting the change
 

[Rajat] I answered A. Correct answer is B. Why not A, because by doing
A you would automatically do B?
 

Who ultimately controls changes to scope on a project?
a. The project manager
b. Senior management
You chose: c. The change control board (incorrect)
d. The customer
 

The correct answer was response d. I chose C.
Web-site Explanation: Of course it’s the customer. Ask yourself, who
is cutting the check for you to do all that work and what are they
willing to pay for? The PM certainly doesn’t and the CCB doesn’t fund
your project. Sr. Management can be subsumed under the customer
heading
[Rajat] Assuming customer is cash-rich and there is no shortage of
funds, does it mean that scope-increase would spiral out of control?
The answer seems to indicate that funding is the only criteria here;
however I thought CCB is the right answer because it would review
impact to triple constraints and quality, risk etc before determining
a change in scope.
 

You are managing a project in which there is a large procurement
activity. One of the stakeholders approaches you with the need for a
change. You have an off-line meeting with the stakeholder and discuss
the change, decide it can be done and agree to implement. What mistake
has the project manager made here?
a. You forgot to consult with senior management
b. You forgot to consult with other stakeholders on the team
c. Contract changes require a formal written approval
You chose: d. You forgot to perform an impact assessment (incorrect)
 

The correct answer was response c.
Explanation: Don’t get fooled by this question. It addresses a
procurement issue, but it’s really about the correct form of
communication to use in the situation. Contracts always require a
formal written approval if change to the contract is needed
[Rajat] I thought PM would FIRST do an impact assessment before
filling out the formal change-request.
 

The project has been running smoothly; initiation phase is complete
and the team is working on all aspects of planning. You had meetings
with stakeholders several times to collect requirements and as a
result, requirements documentation is almost complete, as are high-
level and detailed design documents. As construction begins on the
project, several stakeholders have indicated the need for changes to
the requirements set. They are claiming these elements were missed in
the initial requirements collection process, and they want you to add
these elements to the project immediately. You perform an impact
assessment and get it back to them only to hear that they are not
going to allow any changes in the project budget or the timeline to
complete these additional elements. What is the most effective tool
that you could use to prevent this instance of scope creep?
You chose: a. Change control system (incorrect)
b. Configuration management system
c. Murder Board
d. Work Authorization System
 

The correct answer was response d.
Explanation: One of the defined uses of a work authorization system is
for the control of scope creep
[Rajat] I do not understand how work auth system could help in the
scenario described in the question.
 

Who can approve of changes to any of the primary constraints on your
project such as scope, budget, or timeline?
a. The Change Control Board (incorrect)
You chose: b. The sponsor
c. Senior management
d. Key stakeholders
 

The correct answer was response c.
Explanation: Senior management must be consulted regarding high-level
constraints
[Rajat] I thought the Sponsor sets the project constraints initially
during ‘Develop Charter’ and Define Scope
 

A series of stakeholder meetings were called to address the needs of
stakeholders for the upcoming project. A list of 150 requirements was
drawn up. After reviewing the list and developing a high level
estimate, the PM reported back to the stakeholder group that due to
the budget limitations on the project, it would be possible to deliver
75 of these requirements. A new meeting was called to cull the list
from 150 to 75. The stakeholders, all PhD’s, were going through the
list, when there was serious contention about a group of requirements.
The disagreement escalated to a shouting match, and several
stakeholders left the meeting infuriated. What risk tool would have
best prevented this situation?
a. Brainstorming
b. SWOT analysis
c. Delphi Technique
You chose: d. Nominal Group technique (incorrect)
 

The correct answer was response c.
Explanation: With the Delphi technique, participants remain anonymous
to each other so that they can simply focus on the facts without
having to deal with the emotional components of the problem. PMBOK®
Guide, p. 432
[Rajat] I agree that using Delphi would prevent the conflict; however
if PM would follow the proper process for Nominal group technique,
that would prevent the conflict as well. Moreover, Nominal group
technique is used for prioritizing and culling the list of
requirements; so why is answer not D?
 

A senior stakeholders approaches the project manager to slightly
modify the project scope to include an additional feature required by
him. The project is already in the execution stage. What should be the
response of the project manager?
Options:
A. It is difficult to incorporate this feature as the project is
already moved out of planning stage
B. Analyze the impact of the request on the other factors of triple
constraints namely cost and schedule
C. Bring the change request to Change Control Board to decide on its
fate
D. Document the change request as per project scope management plan
 

Explanation : Answer (d) Document the change request as per project
scope management plan . Project manager should only consider
documented change requests. He should ensure that when the change is
requested the impact on features and functions of product is
documented with change request before the change is allowed to move
through Integrated Change Control. Option (b) and (c) would come later
as part of Integrated Change Control process
 

My Answer :  B Analyze the impact of the request on the other factors
of triple constraints namely cost and schedule
 

[Rajat] I thought that, the first step before documenting CR would be
to analyze impact of the request on other factors of triple-
constraint. Why is B not the answer?
 

You have recently made the final delivery of your software project to
the customer. Before making the release you ensured that thorough
testing was done and verified project scope. However after a week of
delivery customer shows his dissatisfaction on the release and says
product doesn’t support critical functionality. He asks you to add
this feature immediately. What should you do?
Options:
A. Understand the customer requirement and estimate the additional
time and resource required to complete it, Communicate the same to the
customer
B. Discuss the customer feedback with the senior management and seek
their advice on the matter
C. Analyze the in-house process of testing and scope verification to
determine the root cause of the problem
D. Ignore the customer and proceed with project closure activity
 

Explanation : Answer (d) Ignore the customer and proceed with project
closure activity. Once the project manager has made a release and if
the project scope has been completed, project is completed. The
project manager should resist the urge for request to do additional
work once the project scope is fulfilled even if the customer is
unhappy because technically the project is over
 

My Answer :  C Analyze the in-house process of testing and scope
verification to determine the root cause of the problem
 

[Rajat] I answered C because root cause analysis may give answers
regarding customer dissatisfaction and you may be able to address it
that way. With answer D, customer may not give the formal final sign-
off on the project, which is an important part of ‘close project’
process.
 

A senior stakeholder complains that much of the work required to
satisfy the requirements suggested by him are not captured in the
project document. Which of the following document can be used to
determine what is and what is not part of the project work?
Options:
A. Work Breakdown Structure
B. Scope Creep
C. Project Scope Statement
D. Stakeholder Register
 

[Rajat] I answered C. Correct answer is A. Why is C not  correct; as
the scope statement defines all the work that is needed to achieve the
project objectives.
 

Question:
A project has recently been joined by some new team members and the
project manager wants to help them see their roles and provide the
project team with an understanding on where their work packages fit on
project management plan . Which of the following would be most
suitable document?
Options:
A. Requirements Documentation
B. Requirements Traceability Matrix
C. Responsibility Assignment Matrix
D. Work breakdown structure
 

[Rajat] I answered C, because RAM can show work-packages and the
assigned person against it. Does WBS have roles or whose assigned to
the work-package info in it? Also I’m not sure what is meant by “where
the work packages fit on project management plan” in the question.