PMP Questions ID 1666 what is the main reason for controlling the project scope

All Domains

Agile & Scrum

People

Process

Business Environment

CLOUD COMPUTING

Communications

Cost

DECISION SUPPORT SYSTEM (DSS)

FIREWALL TYPES & IMPLEMENTATION

Integration

IT STRATEGY COMMITTEE & IT STEERING COMMITTEE

Procurement

Quality

Resource

Risk

Schedule

Scope

Stakeholder

New PMP Question & Answers with explanation

What is the MAIN reason for controlling the project scope?

Select one

To prevent changes from affecting the project

Preventing scope creep

To enable scope creep

To ensure timely closure of the project

PMP Question No 1659 - Scope

The sponsor of your facilities upgrade project has left the company to join another organization. Several weeks later, you are reviewing the business case for the project, and you find that there are several inconsistencies between what is stated in the business case and what is described in the project scope. Further research shows that the business case as a whole is based on inaccurate information. What do you do?

Select one

Notify your project stakeholders immediately

Add this to the risk log

Update the requirements

Call the sponsor for clarification

Answer

PMP Question No 1618 - Scope

A project is contracted on a Cost-Plus-Fixed-Fee (CPFF) basis with a fee of 10 percent of estimated costs. The estimated cost is US$50,000. If the project comes in at US$75,000 with no changes in project scope, what would be the total cost of the contract?

Select one

US$55,000

US$125,000

US$75,000

US$80,000

Answer

PMP Question No 1613 - Scope

A first-time project manager wanted to have a “perfect project.” This manager informed the customer that this project would not accept change requests of any kind and that the scope would need to be defined precisely at the very start of the project. The customer agreed to this request. What would your comment on this situation be?

Select one

The is a good example of how the project management team can decide what is and what is not necessary for the project. Not allowing changes is a good way of ensuring that the project meets requirements as detailed in the project scope.

This is unrealistic and impractical. Change is inevitable and rather than look at a 'no change' project, it would be more in the project interests to plan for a robust change control process.

This indicates that the project manager is very aggressive and is likely to take the project to successful completion. Since he has announced the 'no change requests' policy, the customer manager can no longer request changes.

This is unrealistic and impractical. The project manager should not have announced his intentions to the customer. He should have had an unofficial policy of rejecting all change requests.

Answer

PMP Question No 1607 - Scope

Product scope is measured against the product requirements, while project scope is measured against:

Select one

The WBS and WBS dictionary

The project scope statement and its associated WBS and WBS dictionary

The project requirements and WBS

The acceptance criteria

Answer