5 Project Management Scenarios and Decisions Free Online FlashCards

When is a predictive project approach useful?

Use a predictive approach when requirements and dependencies are stable, changes are costly, or formal approvals and compliance evidence are essential.

Why does the customer-support app scenario favor an adaptive approach?

The team can release a limited version and learn from usage while user preferences remain uncertain, so an adaptive approach supports discovery and reprioritization.

Why is a predictive approach suitable for the bridge replacement?

Use a primarily predictive approach because the design, permits, safety requirements, and construction dependencies are substantially defined, and changes could have serious consequences.

Why does the system replacement scenario call for a hybrid approach?

Use integrated plans and governance for contracts, migration, security, interfaces, and cutover; use iterative prototypes to refine department workflows.

What is the first step in the practical decision routine?

First describe the change or evidence, separating a confirmed issue from an assumption or request.

What characterizes an adaptive project approach?

An adaptive approach delivers in short cycles, gathers feedback, and revises priorities as the team learns. It suits uncertain needs when usable increments can be tested.

What is a hybrid project approach?

A hybrid approach deliberately combines methods, such as predictive governance and release controls with iterative design and development.

How should an app team handle an immovable launch date?

Agree which features are essential for the date and which can follow. Do not silently add scope while keeping every other commitment unchanged.

How should a team evaluate a request to widen a bridge's pedestrian path?

Clarify the need, develop feasible options, estimate impacts, and identify safety or approval implications before an authorized decision-maker decides.

What should the team do first about the vendor's data-conversion warning?

Record the risk's probability and impact, an owner, and response options; test a representative data sample early.

How can the system team set expectations about prototypes?

Explain that the cutover window and security requirements are constraints, while some workflow details remain open to discovery.

What factors should a team assess when evaluating a change?

Consider expected value, scope, time, cost, quality, risk, dependencies, and affected stakeholders.