1 Project Delivery Approaches and Decision Criteria Online Quiz Questions

True

False

True

False

Adaptive, because any uncertainty about occupant preferences calls for repeated replanning of the whole project.

Predictive, because the main scope and delivery sequence are largely defined.

Agile, because construction work is usually divided into frequent usable software-like increments.

Hybrid, because every project with stakeholder input must combine two approaches.

Users can review working versions regularly.

Users and decision-makers are rarely available for feedback or decisions.

The work can be divided into useful increments.

Early user feedback and delivery of valuable functionality are important.

Required approval gates and audit evidence can be retained while suitable features are developed iteratively.

A regulated project must use predictive development for every component.

Mandatory traceability, testing, or documentation can require defined controls and evidence.

Iterative work can disregard required security controls if it produces user feedback sooner.

Agile is a separate name for all adaptive work, whether or not it uses increments.

Agile is a way of working within the adaptive family that emphasizes collaboration and frequent usable increments.

Agile is a predictive approach that fixes scope and sequence up front.

Agile is a hybrid approach that always divides work equally between predictive and adaptive methods.

Use only predictive development, because fixed release and security obligations make iterative work unsuitable.

Use only agile practices, because iterative feature discovery removes the need for approval gates and audit evidence.

Use a hybrid approach, retaining required governance and controls while developing suitable features iteratively.

Use adaptive development without planned release coordination, because user-facing functionality is uncertain.

Strengthen upfront definition, arrange delegated decision authority, or consider a hybrid approach.

Assume an agile approach will work unchanged because feedback availability does not affect it.

Avoid defining requirements and plans until users become regularly available.

Use adaptive delivery and treat missed stakeholder reviews as confirmation that the backlog is stable.

True

False

Agile is the broader category, and adaptive is one of its specific methods.

Adaptive is the broader category, and agile is a way of working within it.

Adaptive and agile are unrelated approaches that cannot be combined.

Agile is another name for predictive delivery.

Use an adaptive approach because stable requirements make feedback unnecessary.

Use an agile approach because construction must always be divided into increments.

Use a predictive approach because scope and dependencies are well understood.

Use a hybrid approach because a fixed budget rules out upfront planning.

Plan for the limited feedback by strengthening upfront definition or delegating decision authority.

Select agile because it does not depend on stakeholder feedback.

Use adaptive delivery and postpone all decisions until stakeholders become available.

Avoid any planning because the requirements may change.

Use only predictive delivery because security controls prevent iterative work.

Use only agile delivery because user-facing features are uncertain.

Use adaptive delivery without fixed release planning or approval points.

Combine predictive governance and release planning with iterative development of suitable features.