Scenario practice questions

A project manager is evaluating whether to implement a PMO (Project Management Office) for the organization. Which scenario would best justify the creation of a PMO?

Trap 1: Projects are consistently completed under budget.

Success indicates effective processes, not a need for a PMO.

Trap 2: The project manager has extensive experience.

Experience is not a primary reason to create a PMO.

Trap 3: The organization has a single large project.

A single project typically does not require a PMO.

A
Projects are consistently completed under budget.
Why wrong: Success indicates effective processes, not a need for a PMO.
B
The organization has multiple projects with inconsistent processes and low success rates.
A PMO standardizes processes and improves success rates across multiple projects.
C
The project manager has extensive experience.
Why wrong: Experience is not a primary reason to create a PMO.
D
The organization has a single large project.
Why wrong: A single project typically does not require a PMO.

Question 2mediummultiple choice

A project manager is developing the project management plan. The sponsor requests detailed cost estimates for each work package, but the activities have not yet been defined. What should the project manager do?

Trap 1: Use analogous estimating to provide rough estimates.

Analogous estimating gives rough estimates, not the detailed estimates requested by the sponsor.

Trap 2: Ask the sponsor to approve a rough order of magnitude estimate.

A rough order of magnitude estimate is not detailed, and the sponsor requested detailed estimates.

Trap 3: Break down the work packages into activities and create bottom-up…

This is premature because activity definition has not yet been done; bottom-up estimates require defined activities.

A
Use analogous estimating to provide rough estimates.
Why wrong: Analogous estimating gives rough estimates, not the detailed estimates requested by the sponsor.
B
Ask the sponsor to approve a rough order of magnitude estimate.
Why wrong: A rough order of magnitude estimate is not detailed, and the sponsor requested detailed estimates.
C
Defer the cost estimates until after activity definition.
Activity definition must precede detailed cost estimation to ensure accuracy.
D
Break down the work packages into activities and create bottom-up estimates.
Why wrong: This is premature because activity definition has not yet been done; bottom-up estimates require defined activities.

Question 3easymultiple choice

A project manager is defining the project life cycle for a construction project where requirements are well-defined and unlikely to change. Which project management methodology is most appropriate for this scenario?

Trap 1: Agile

Agile is for evolving requirements; not suitable for stable, fixed-scope projects.

Trap 2: Hybrid

Hybrid combines elements; not necessary when requirements are clear.

Trap 3: Scrum

Scrum is an agile framework; not appropriate for fixed-scope construction.

A
Agile
Why wrong: Agile is for evolving requirements; not suitable for stable, fixed-scope projects.
B
Predictive
Predictive methodology uses sequential phases and is ideal for well-defined requirements.
C
Hybrid
Why wrong: Hybrid combines elements; not necessary when requirements are clear.
D
Scrum
Why wrong: Scrum is an agile framework; not appropriate for fixed-scope construction.

Question 4hardmultiple choice

A project manager notices that a key team member is frequently pulled away to work on another priority project, causing delays. This situation is an example of which type of constraint?

Trap 1: Mandatory dependency

A mandatory dependency is a hard logic relationship between activities.

Trap 2: Technical constraint

Technical constraints involve imposed technology choices, not resource availability.

Trap 3: Discretionary dependency

Discretionary dependency is a preferred order, not related to resource availability.

A
Mandatory dependency
Why wrong: A mandatory dependency is a hard logic relationship between activities.
B
Resource constraint
Correct. The limitation of key personnel is a resource constraint.
C
Technical constraint
Why wrong: Technical constraints involve imposed technology choices, not resource availability.
D
Discretionary dependency
Why wrong: Discretionary dependency is a preferred order, not related to resource availability.

Question 5easymultiple choice

A project manager is assigned to a new software development project with clearly defined requirements and minimal expected changes. Which project management methodology is most appropriate for this scenario?

Trap 1: Kanban

Kanban is an agile framework focused on continuous delivery, not sequential phases.

Trap 2: Agile

Agile is best for evolving requirements and iterative delivery, not stable requirements.

Trap 3: Hybrid

Hybrid combines elements but would not be the primary choice when requirements are fixed.

A
Kanban
Why wrong: Kanban is an agile framework focused on continuous delivery, not sequential phases.
B
Agile
Why wrong: Agile is best for evolving requirements and iterative delivery, not stable requirements.
C
Hybrid
Why wrong: Hybrid combines elements but would not be the primary choice when requirements are fixed.
D
Predictive (Waterfall)
Correct. Predictive methodology works well with stable, well-defined requirements.