3 Hybrid Project Management and Tailoring Online Quiz Questions

Use predictive planning throughout because it is the standard hybrid approach.

Use short iterative cycles to deliver and assess useful increments.

Delay all delivery until every feature is complete.

Remove governance so the team can change the work freely.

True

False

True

False

How uncertain the requirements and solution are

Dependencies and constraints such as procurement lead times or fixed dates

Whether benefits can be delivered in useful increments

User availability, team experience, suppliers, and required approvals

Whether the entire project can simply be labeled “agile” or “waterfall”

Ask sponsors to approve every routine team task each day.

Replace milestone reviews with unstructured user feedback only.

Review outcomes, risks, forecast, and milestone readiness at agreed intervals.

Wait until project closure to discuss risks or readiness.

Avoid written records so the team can remain agile.

Maintain documentation needed for decisions, coordination, operation, and compliance, and avoid unhelpful paperwork.

Require every team to create the same documents regardless of project needs.

Keep only the backlog and discard all formal approval evidence.

Keep procurement and safety approvals on a predictive plan.

Develop the uncertain interface in short iterations with user demonstrations.

Allow interface changes to bypass all integration dependencies.

Coordinate tested iteration outputs with hardware and integration milestones.

Move the integration milestone whenever an iteration runs late.

Stop testing features until all hardware work is complete.

Define when tested iteration outputs must be ready for the integration milestone.

Let the interface team plan independently because its work is iterative.

Use iterative delivery for all work, regardless of uncertainty.

Use more predictive planning for the stable requirements and short feedback cycles for uncertain requirements.

Delay planning until every requirement is final.

Choose an approach based only on the organization’s preferred method.

Use short iterations for site work and procurement, but fix the interface design before users see it.

Use a single predictive plan for every part because the infrastructure is fixed.

Keep site work, procurement, budget controls, and safety approvals predictive; develop the interface in short iterations with user demonstrations.

Let the interface team change hardware and integration dates whenever feedback arrives.

Maintain documentation that is useful for decisions, coordination, operation, or compliance, and avoid unhelpful paperwork.

Document every team conversation in a formal report, whether or not anyone needs it.

Remove all formal artifacts so the team can focus on delivery.

Keep only an iteration plan, even if approvals or compliance require other evidence.

Wait to set outcomes and funding limits until all detailed work is complete.

Detail the entire project plan early and keep it unchanged as new information appears.

Plan only the next iteration and leave outcomes and milestones undefined.

Set the overall vision, outcome measures, funding limits, and major milestones early, then detail near-term work as learning occurs.

True

False