2 Adaptive and Agile Project Management Online Quiz Questions

True

False

True

False

They manage the Product Backlog and make its ordering clear.

They create a usable increment each Sprint and adapt their approach toward the Sprint Goal.

They establish Scrum and help address impediments.

They approve every change request before it can be considered.

Visualize work and its status.

Require every team to use fixed-length iterations.

Limit work in progress.

Manage flow and use feedback for collaborative improvement.

True

False

Use a predictive approach because uncertainty makes feedback unnecessary.

Use an adaptive approach with short cycles and regular demonstrations to learn from users.

Wait until all requirements are certain before beginning any work.

Choose a method based only on which label is most popular.

Consider the request's value and urgency.

Assess its risks and dependencies.

Accept every request to demonstrate responsiveness.

Consider its effect on the current goal and team capacity.

Use a purely adaptive approach and postpone all dependency planning.

Treat every component as fixed, even if one has uncertain user needs.

Plan major dependencies and approvals predictively, while adapting any uncertain component as appropriate.

Avoid planning because fixed dependencies prevent useful project management.

Keep the backlog unchanged because the original feature order cannot be revised.

Reorder the backlog so rescheduling is considered sooner, and assess dependencies and capacity.

Replace the entire backlog with the visual theme work.

Accept the change without considering its effect on the team's current goal.

Use a predictive approach and finalize all features before development.

Use an adaptive approach with short delivery cycles and frequent user feedback.

Use a predictive approach because requirements are uncertain.

Delay user feedback until the product is complete.

Require the team to start a new fixed-length Sprint for every work item.

Replace the existing workflow with a predictive plan that cannot change.

Visualize work and manage its flow without requiring fixed-length iterations.

Avoid displaying work status so that team members can focus independently.

Set a limit on how many items can be in progress and finish work before pulling in more.

Start as many items as possible so no team member is ever waiting.

Prioritize keeping every work item active, even when blockers prevent progress.

Add more work whenever an item is blocked, without considering team capacity.

Measure progress by counting meetings and documents produced, even if no usable work is complete.

Show completed, usable work so stakeholders can see what has been delivered.

Keep progress private until all originally proposed features are finished.

Treat time spent on tasks as proof that the intended outcome has been achieved.