Answers:
1. Answer: C
It’s not enough that the Project Manager approves of the Project Management Plan; it needs to be approved by all of the stakeholders in the project. Everyone on the team should feel comfortable with the processes that are going to be used to do the work.
2. Answer: B
Joe is doing root-cause analysis on process problems: that’s Perform Quality Assurance. Remember, Perform Quality Control is when you are trying to find problems in your work products through inspection. Perform Quality Assurance is when you are looking at the way your process affects the quality of the work you are doing.
3. Answer: C
Every change request needs to be evaluated to determine whether or not it should be made. That’s what we do in the Perform Integrated Change Control process—every change is analyzed to determine its impact. It’s then documented as a change request and put into the change control system. That’s where the stakeholders on the CCB determine if the change should be made.
4. Answer: A
When a change has been approved you always need to update the baseline and then implement the change. That way, you will be sure to track your performance versus new scope and schedule expectations and not the old ones.
5. Answer: B
By the time the Close Project or Phase process happens, you should have already gotten formal written acceptance for the deliverables. That’s what the Verify Scope process is for, and you verify that formal acceptance in the Close Project or Phase process.
6. Answer: A
The project scope management plan is a really important tool in your project. It tells you exactly how you’ll create the project scope, define the WBS, verify that the work has been done, and make changes to the scope. But it doesn’t tell you about specific assumptions that you and the team have made, or constraints on your project. To find those, you should look in the