Project Management Foundations Practice Quiz (11 questions)

All questions and answers

1. Which characteristic distinguishes a project from ongoing operational work?

A project continues until its resources are reassigned.
A project has a definite start and end and creates a unique result.
A project repeats a standard output as part of routine operations.
A project maintains recurring services without a planned end.

A project has a definite start and end and creates a unique result.

Explanation

A project is a temporary effort with a definite beginning and end that creates a unique product, service, or result. Ongoing operational work is not defined by a planned project end.

2. A project manager must balance limited time and funding against scope and quality demands. Who determines the priorities among these competing constraints?

The project team ranks constraints based on its preferred workflow.
The customer assigns priorities by approving each completed task.
The project manager gives every constraint equal priority throughout.
Management sets the priorities among the competing demands.

Management sets the priorities among the competing demands.

Explanation

Project constraints can include time, cost, scope, quality, and other competing demands, and management sets their priorities. The project manager may coordinate the work, but the unit assigns the priority-setting role to management.

3. A product remains on the market after the project that created it has closed. Which distinction best explains this?

The product lifecycle can continue from conception to withdrawal, while the project lifecycle ends with project closure.
The project lifecycle begins with product withdrawal, while the product lifecycle begins with project initiation.
The product lifecycle ends when project planning finishes, while the project lifecycle lasts until product withdrawal.
The product and project lifecycles both end when the project deliverables are produced.

The product lifecycle can continue from conception to withdrawal, while the project lifecycle ends with project closure.

Explanation

A product lifecycle runs from the product's conception until it is withdrawn, while a project lifecycle runs from project initiation through closure to produce deliverables. The project can therefore close while the product continues to exist.

4. At the start of a project, which set of activities is characteristic of the initiating process group?

Formally authorize the project, create its charter, identify stakeholders and high-level needs, and prepare a stakeholder-management strategy.
Carry out planned tasks, produce deliverables, and coordinate the team's day-to-day work.
Organize the work, assess the team's ability to meet objectives, evaluate knowledge areas, and create a completion roadmap.
Track performance against plans, identify deviations, and apply corrective actions.

Formally authorize the project, create its charter, identify stakeholders and high-level needs, and prepare a stakeholder-management strategy.

Explanation

Initiating formally authorizes the project, provides information for the project manager to begin, creates the charter, identifies stakeholders and their high-level needs, and produces a stakeholder-management strategy. Planning, a plausible alternative, organizes the project and develops a roadmap before work begins.

5. What is the primary responsibility of a project sponsor?

Governs programs and projects by selecting investments for organizational value
Owns departmental resources and directs the technical work performed by them
Manages related projects to coordinate their results with organizational strategy
Champions the project, secures organizational support, and provides funding

Champions the project, secures organizational support, and provides funding

Explanation

The sponsor advocates for the project, builds organizational buy-in, and provides its funding. A program manager instead coordinates related projects and guides their managers.

6. What must a change to project scope be evaluated against before it is approved?

Its effects on schedule, staffing, procurement, and reporting responsibilities
Its effects on team assignments, technical methods, and organizational structure
Its effects on product features, market demand, and operational maintenance
Its effects on time, cost, risk, quality, resources, and customer satisfaction

Its effects on time, cost, risk, quality, resources, and customer satisfaction

Explanation

A scope change must be assessed for effects on the project’s key constraints, including time, cost, risk, quality, resources, and customer satisfaction, and then handled through integrated change management. Evaluating only staffing and procurement would omit several required impact areas.

7. What is the purpose of requirements traceability during a project?

To compare actual project performance with the schedule and cost baselines
To rank stakeholders by influence and determine how they should be engaged
To decompose approved deliverables into work packages for estimating and scheduling
To link requirements to objectives or other requirements and analyze proposed scope changes

To link requirements to objectives or other requirements and analyze proposed scope changes

Explanation

Requirements traceability connects each requirement to project objectives or related requirements, helping the team assess proposed changes to product or project scope. Decomposing deliverables into work packages is the function of the work breakdown structure, not requirements traceability.

8. During which process is formal customer acceptance of interim deliverables obtained?

Verify Scope, using validated deliverables and the scope baseline
Integrated Change Control, when proposed scope changes are reviewed
Close Project or Phase, when the project or phase receives final sign-off
Control Scope, when completed work is compared with the approved baseline

Verify Scope, using validated deliverables and the scope baseline

Explanation

Verify Scope obtains formal customer acceptance of interim deliverables. Close Project or Phase is the process associated with final acceptance or sign-off for the project or phase as a whole.

9. How do mandatory and discretionary activity dependencies differ in project sequencing?

Mandatory dependencies permit activities to overlap, while discretionary dependencies require a predecessor to finish before its successor starts.
Mandatory dependencies reflect requests from outside the project, while discretionary dependencies are created by inserting waiting time between activities.
Mandatory dependencies follow the natural work sequence or a contract, while discretionary dependencies are chosen by the team and may be changed.
Mandatory dependencies are selected by the team to compress the schedule, while discretionary dependencies follow the natural work sequence or a contract.

Mandatory dependencies follow the natural work sequence or a contract, while discretionary dependencies are chosen by the team and may be changed.

Explanation

Mandatory dependencies arise from the natural flow of work or contractual requirements, whereas discretionary dependencies reflect the project manager and team's chosen sequencing. A team can change a discretionary dependency to help compress or fast-track the schedule; an external dependency, by contrast, is based on a party outside the project.

10. Why should activity-duration estimates be made by the people who will perform the work whenever possible?

Their familiarity with the work can make the estimates more realistic.
Their estimates remove the need to identify activity resource requirements.
Their authority allows them to approve the project schedule baseline.
Their involvement converts duration estimates into calculated risk reserves.

Their familiarity with the work can make the estimates more realistic.

Explanation

Performers are often most familiar with the work, which can help them estimate its duration realistically. Resource requirements still need to be identified; involving performers does not eliminate that estimation input.

11. A project manager is building a schedule and wants to estimate the likelihood of meeting a target completion date while accounting for uncertainty in activity durations. Which technique should the manager use?

Use fast tracking to perform critical-path activities in parallel
Apply resource leveling to create a schedule constrained by available resources
Run a Monte Carlo simulation using the network diagram and activity estimates
Calculate total float to determine how much noncritical activities can slip

Run a Monte Carlo simulation using the network diagram and activity estimates

Explanation

Monte Carlo analysis simulates project outcomes using the network diagram and optimistic, pessimistic, and most likely activity estimates, allowing completion-date probabilities to be estimated. Resource leveling addresses resource limits and may lengthen the schedule, but it does not itself calculate completion probabilities.

Study with flashcards

Lock in the answers with 10 flashcards on Project Management Foundations.

What defines a project in terms of duration and output?

It is a temporary effort with a definite start and end that creates a unique product, service, or result.

What distinguishes operational work from project work?

Operational work is ongoing, whereas project work has a definite end.

When does the product lifecycle begin and end?

It begins when a new product is conceived and ends when it is withdrawn.

See the flashcards →

Read the study guide

Go over the full study guide for Project Management Foundations.

Read the study guide →

Related classes

Make your own practice quizzes

Upload your class notes and Revizly writes a practice quiz with explained answers in about a minute.

Quiz maker