Showing posts with label scope. Show all posts
Showing posts with label scope. Show all posts

Sunday, 18 January 2015

Scope Management #4

Q: Your company has asked you to be the project manager for the product introduction of its new DeskTop Rock media system. You recently published the project scope statement. Which of the following is not contained in the project scope statement?

a) Requested changes;
b) Project configuration management requirements;
c) Project specifications;
d) Constraints.

A: a)

Requested changes are an output of the Scope Definition process. They are not part of the project scope statement.


Thursday, 8 January 2015

Scope Management #3

Q: You are working with XYZ organisation. Your senior manager imposed a new delivery date which is earlier than the project deliverables date mentioned in the scope statement. To whom are you most accountable?

a) Customer
b) Team members
c) Sponsor
d) Senior Manager

A: a)


Wednesday, 7 January 2015

Scope Management #2

Q: You are a project manager for an agricultural supply company. You have just completed and obtained sign-off on the project scope statement for your new Natural Bug Busters project. A key stakeholder has informed you that a deliverable is missing from the project scope statement. The deliverable is a critical success factor. Which of the following actions should you take?

a) Modify the scope statement after an approved change request has been received from the stakeholder;
b) Modify the scope statement to reflect the new deliverable;
c) Inform the stakeholder that work not stated in the project scope statement is excluded from the project;
d) Schedule Variance;
e) Inform the stakeholder that this deliverable must be included in phase two of this project since sign-off has already been obtained.

The project scope statement will change throughout the project as a change requests are received and approved. PMs must be certain to discover all deliverables before publishing the project scope statement to prevent situations like the one described in the question.

Tuesday, 6 January 2015

Scope management #1

Q: You are working on a project that is similar in scope to a project performed last year by your company. Which of the following might you consider:

a) Reusing the previous project's product description when writing the scope statement
b) Reusing the previous project's cost-benefit analysis as justification for this project
c) Using the previous project's WBS as a template
d) Using the previous project's alternatives identification as a template

A: c) WBSs from previous projects can be used as templates on projects that are producing similar products, services or results. Some companies write WBS templates to be used for projects of similar scope.

Estimates #3

Q: Your project sponsor has requested a cost estimate for the project on which you're working. This project is similar in scope to a project you worked on last year. She would like to get the cost estimates as soon as possible. Accuracy is not her prime concern right now, and she would like to get the estimate asap. You decide to use:

a) Parametric estimating techniques
b) Analogous or top-down estimating techniques
c) Bottom-up estimating techniques
d) Computerised modeling techniques

A: b)

Analogous or top-down estimating techniques are a form of expert judgement. Since this project is similar to another recent project, you can use the cost estimates from the previous project to help you quickly determine estimates for the current project.

Wednesday, 15 October 2014

Project Schedule #2

Q: Your company has appointed you PM for a new product line production. Three new products are involved, two of which will be introduced together, and a third one that will follow within two years. Product number three will be elaborated in more detail closer to its release date, while the first two products will be elaborated in great detail now. The scope management plan has just been completed.  Which of the following is true?
Options:
a) The WBS template from a previous project, a tool and technique of the Create WBS process, was used to create the WBS for this project. The WBS encompasses the major deliverables for the project.
b) The WBS encompasses the full scope of work for the project and the technique in question is called rolling wave planning.
c) Only the deliverables associated with the work of the project should be listed on the WBS. Since product number three isn't being released until a later date it should not  yet be included on the WBS.
d) The WBS should be created next, and it encompasses the full scope of work for the project. Only the work of the project is listed on the WBS.

A: b).
Explanation: There isn't enough information in the question to know whether a) is correct, although it could be. d) is incorrect because the next process after the scope management plan is created is the Scope Definition process. The WBS details the entire scope of the project and includes all deliverables. It is an output of the Create WBS process and the technique of elaborating some deliverables at a later date is called rolling wave planning.