Chapter 3 Project Management

The scope baseline is a component of the project management plan and is critical for you to verify scope and perform scope control. Which of the following is not a component of the scope baseline? 1. Project Scope Statement 2. WBS 3. WBS dictionary 4. Activity list

Activity list

During the Validate process you formalize acceptance of the project deliverables and keep the project focused on the business need for which it was undertaken. This product should be done: 1. At the beginning of the project 2. At the end of the project 3. When required by the project sponsor 4. After getting verified deliverables from the Control Quality process

After getting verified deliverables from the Control Quality process

In your project, while decompressing the project work into more manageable components you are aware of the problem of excessive decomposition. Which of the following is NOT the consequence of excessive decomposition? 1. Non-productive management effort 2. Inefficient use of resources 3. decreased efficiency in work performance 4. Better knowledge of activity sequences

Better knowledge of activity sequences

You are the project manager in a company. You have finished preparing a detailed description of the project and product. What will you do next? 1. Collect requirements 2. Create WBS 3. Validate Scope 4. Control Scope

Create WBS

Your project sponsor recently attended a project management conference where the purposes of the Management-By-Objectives (MBO) approach were discussed. In this context, which of the following is NOT a purpose of MBO? 1. Aligning project goals with organization goals 2. Aligning project goals with the goals of other sub-units of the organization 3. Aligning project goals with the goals of previous projects 4. Aligning project goals with individual goals

Aligning project goals with the goals of previous projects

After collecting requirements, one of your tasks as a project manager is to prepare a scope statement for your project. the scope statement provides: 1. Authorization to the project manager for using organizational resources for project activities 2. Documentation of how the project scope will be managed and how scope changes will be integrated into the project 3. Definition for work breakdown structure 4. Common understanding of the project scope among project stakeholders

Common understanding of the project scope among project stakeholders.

You have undertaken a project under contract where you are supposed to create an anti-virus software product for a customer in ten months. You follow the software development life cycle which includes analysis, high level design, low level design, coding, testing, and rollout with a deliverable at the end of each phase. Your customer has defined the scope very well and said that he is going to review your product after ten months. In this case, you should: 1. Insist that the customer verify the deliverables at the end of each phase 2. Ask you senior management to review the deliverables at the end of each phase to ensure that the delivereables satisfy customer requirements 3. Complete the product as per specifications and provide the completed product to the customer as requested 4. Provide project deliverables to the customer at the end of each phase, even if the customer does not review them

Complete the product per specifications and provide the completed product to the customer as requested

In your project, the process of monitoring the status of the project and product scope and managing changes to the scope baseline is referred to as: 1. Validate Scope 2. Control Scope 3. Define Scope 4. Collect Requirements

Control Scope

Project Scope Management includes the processes required to ensure that the project includes all the work required, and only the work required, to complete the work successfully. In this context, a detailed project scope statement is prepared as part of: 1. Collect Requirements 2. Create WBS 3. Scope Elabroration 4. Define Scope

Define Scope

You are managing a complicated software development project with several deliverables. To be effective and to be alert to potential future problems, you monitor the status of completion of the project deliverables. the information will be available to you in the: 1. Work performance measurements 2. Project baseline changes 3. Work performance information 4. Earned value techniques

Earned value techniques

You have recently joined as the project manager for ABC Company. You notice that the customers are getting frequent change requests implemented by informally approaching the team members. This has resulted in work disruption and discontent among team members. What should be your FIRST priority to remedy the situation? 1. Create a detailed project scope statement 2. Align the project objectives with the organizational goals 3. Ensure proper project scope control 4. Call a meeting of all the project stakeholders to resolve any outstanding issues

Ensure proper project scope control

The Scope Management Plan is an important component of the Project Management Plan since it provides direction on how the project will be managed throughout the project life cycle. The Scope Management Plan documents: 1. Which product requirement will be incorporated 2. How project scope will be defined, developed, controlled, and verified 3. Which stakeholders are most critical for defining the project scope 4. High-level project scope deliverables

How project scope will be defined, developed, controlled, and verified

After completing the define Scope process, management has asked you to coordinate the activities related to work breakdown structure (WBS) in your project. When using documentation as a tool, what should you do FIRST? 1. Identify the development and related work 2. Determine the constituent components of the WBS 3. Assign responsibility for each task in the WBS 4. Create the cost and time estimates for each activity in the project

Identify the development and related work

You are the project manager of a software company involved in creating an anti-virus software product. you are in the execution phase of the project when you realize that a requirement was not included in the product. This si due to an omission in defining the scope baseline of the project. What should you do? 1. Issue a change request 2. Take corrective action 3. Add the requirement to your product and continue with execution 4. Take defect repair action

Issue a change request

As a project manager, you are responsible for managing changes to the project scope. If, at the end of the project, a customer wants a major change in the scope of work, you should: 1. Reject the change 2. Make the required change 3. Escalate the matter to senior management 4. Let the customer know about the impact of the change

Let the customer know about the impact of the change

Your project is very critical for the company and must be completed within the next six months. the project charter has been signed, but the scope statement is not yet prepared. The management asks you to go ahead with the project without the scope statement being approved. What should you do? 1. Refuse to work on the project, because the management is not following standard project management practices. 2. To save time, you should start the project with inputs from the project charter 3. Meet the management and explain the problems you may face if you start a project without a scope statement. 4. Escalate the issue to the project sponsor and issue a risk memo

Meet the management and explain the problems you may face if you start a project without a scope statement

The project scope statement consists of the product scope description and project deliverables. It also defines the: 1. Scope Baseline 2. WBS 3. Product acceptance criteria 4. WBS dictionary

Product acceptance criteria

Your company exhibited a car model in two international auto expos and obtained feedback from the global automobile industry, auto magazines, and others. The company decided to go ahead with the designing and manufacturing of the car, taking into consideration the feedback received. Which of the following methods did your company use to make this decsion? 1. Observation technique 2. Prototype 3. Requirement documentation 4. Requirement traceability matrix

Prototype

Which of the following cannot be considered a benefit of a well-constructed scope statement? 1. Provides a documented basis for making fututre project decisions 2. Develops common understanding of project scope among stakeholders 3. Provides knowledge of project justification, deliverables, and objectives 4. Provides a basis for time and cost estimates

Provides a basis for time and cost estimates

Inspection includes activities such as measuring. examining, and testing undertaken to determine whether results conform to requirements. Which of the following terms does not refer to inspection? 1. Product review 2. Audit 3. Walkthrough 4. Stage-gate

Stage-gate

Project scope management includes the processes required to ensure that the project includes all the work required and only the work required to complete the project successfully. In this context, the project charter plays a very important role because it: 1. Provides a list of project deliverables 2. Provides high-level project description and product characteristics 3, Provides deliverables oriented grouping of work components 4. describes the project plan parameters, i.e., quantifiable criteria that must be met for the project to be considered successful

Provides high-level project description and product characteristics

You are a project manager in a manufacturing company. You are developing a new product. In this context, you conducting requirements workshop for the stakeholders to determine the products critical characteristics. Which technique would you use for this purpose? 1. Quality function development 2. Joint application development 3. Voice of the customer 4. Juran's improvement technique

Quality function development

The customer accepted your project's product two weeks ago, but recently complained that some of the product features are not as desired and that the product is not functioning properly. What should you do FIRST? 1. Ignore the customer, since he has already accepted the product 2. Review the customer's test results 3. review the Validate Scope process 4. Start working on rectifying the errors as reported by the customer

Review the Validate Scope process

As part of decompressing, you break down the project work that needs to be accomplished in the near term at a low level of WBS. However, the work planned in the future is broken down at a relatively high level of WBS. This technique is called: 1. Procrastination 2. Delaying tactics 3. Futuristic planning 4. Rolling wave planning

Rolling wave planning

Planning the scope for a project occurs very early in the project life cycle. One of the first steps is to document how the project scope will be defined, validated, and controlled. the output(s) of the Plan Scope Management process are: 1. Scope management plan 2. Scope baseline and Requirements documentation 3. Scope management plan and Requirements documentation 4. Scope management plan and Requirements management plan

Scope management plan and Requirements management plan

Which of the following is not an accepted form for the WBS structure? 1. Using phases of the project life cycle as the second level of decomposition, with the product and project deliverables inserted at the third level 2. Using major deliverables as the second level of decomposition 3. Using work packages as the first level of decomposition 4. Incorporating subcomponenets which may be developed by organizations outside the project team, such as contracted work

Using work packages as the first level of decomposition

You are a project manager in a large software development organization. It is a primary objective in your company to deliver quality products with a low rate of errors and high product acceptance rate by your customers. The company has made significant investments in a robust system to support these corporate objectives and goals. When developoing contracts for software development projects, it is standard that the customer is required to follow rigorously defined processes for user acceptance testing which must be conducted each time a module is completed. the customer is also required to notify the project manager, in writing that the software module was tested and whether it was acceptable or not. This user acceptance testing, and the resulting notification is part of which process? 1. Control Scope 2. Collect Requirements 3. Validate Scope 4. Perform Quality Assurance

Validate Scope

Which of the following statements related to Validate Scope and control Quality processes is accurate? 1. Validate Scope is concerned with correctness of the work results, while Control Quality is primarily concerned with acceptance of the work results 2. Validate Scope is concerned with acceptance of the work results, while Control Quality is primarily concerned with correctness of the work results 3. Validate Scope is done only after changes are approved by the control board. 4. Both Validate Scope and Control Quality processes are always done sequentially

Validate Scope is concerned with acceptance of the work results, while Control Quality is primarily concerned with correctness of the work results

In which document will you find the code of account identifier, description of work, responsible organization, and list of schedule milestones? 1. WBS 2. WBS Dictionary 3. PERT/CPM Charts 4. Roles and responsibilities Matrix

WBS Dictionary

As a project manager, you are interested in creating a detailed project scope statement to clearly define what work will be performed and what work is going to be excluded. Which of the following will NOT be part of this project scope statement? 1. Project exclusions 2. Work Breakdown Structure (WBS) 3. Project deliverables 4. Project assumptions and constraints

Work breakdown structure (WBS)