4 Choosing an Approach for a Project Online Quiz Questions

True

False

True

False

Use predictive planning because the scope and solution are understood and changes are costly.

Use adaptive delivery because all work should be tested in short cycles.

Use adaptive delivery because fixed commitments favor frequent reprioritization.

Choose an approach based only on which method the team has used before.

Select a project-management framework immediately and assume it will resolve the uncertainty.

Run a prototype or feasibility test to reduce uncertainty before settling on an approach.

Commit to a detailed predictive plan even though the solution is unknown.

Avoid testing until the entire project has been planned.

Ignore the dependencies and allow each team to set unrelated delivery dates.

Use only short-cycle delivery because dependencies make coordination unnecessary.

Plan integration and coordination across the dependent work, using milestones where needed.

Remove all external suppliers from the project before planning.

Whether team members have the skills and availability the work requires

Whether the team prefers a familiar method, regardless of project needs

Whether the team has authority to make day-to-day decisions

Whether the team has suitable tools

Whether the team can access users or relevant specialists

Use adaptive delivery for every part, including the defined approvals, without planning review gates.

Use predictive planning for every part, even though user-facing features are not yet clear.

Use a hybrid approach: plan infrastructure and approval gates predictively, and develop user-facing features in short increments with feedback.

Delay all infrastructure and privacy planning until user-facing features are complete.

The solution is uncertain, and the team can learn through frequent feedback.

The scope is stable, and changes are costly.

Stakeholders can give frequent feedback on useful increments.

Formal approvals and fixed commitments dominate, while feedback is unavailable.

Useful increments can be delivered and evaluated.

Reassess only after the project has been delivered.

Reassess at major milestones or when relevant project conditions change.

Reassess only if an individual team member prefers a different framework.

Reassess after every routine task, regardless of project conditions.

True

False

Adaptive, because short cycles are preferable even when the work is stable and changes are costly.

Predictive, because scope and solution are understood and formal approvals and fixed commitments dominate.

Hybrid, because every project with formal approvals must combine predictive and adaptive practices.

Adaptive, because a stable scope requires frequent reprioritization.

Adaptive, because the team can deliver useful increments and adjust them using frequent feedback.

Predictive, because uncertainty makes it especially important to lock down all requirements at the outset.

Predictive, because frequent feedback is incompatible with planned work.

Hybrid, because any uncertain requirement means some parts of the project must be regulated.

Skip reviews until the project is complete so stakeholders do not interrupt delivery.

Use adaptive work without scheduled decision points, since formal approvals are unnecessary.

Plan explicit review and decision points around stakeholder feedback and formal approvals.

Assume stakeholders will become available more often once delivery begins.