A. Display the level of effort and resources utilized.

B. Identify dependencies between sprints or iterations.

C. Identify and communicate upcoming milestones.

D. Display the remaining work across time.

A. Incremental design and architecture.

B. Manual regression testing.

C. Test-Driven Development (TDD).

D. Pair programming.

A. Work from a prioritized backlog.

B. Work in timeboxed sprints.

C. Are self-organized and empowered.

D. Value individuals and interactions.

A. Yes, the ScrumMaster should get status updates and distribute new tasks to the team.

B. Yes, the ScrumMaster should hold Scrums daily and keep the time to 15 minutes or less.

C. No, the ScrumMaster should act in the role of facilitator to foster team self-organization.

D. No, the ScrumMaster should allow the Scrum to run as long as is required by the team.

A. the implementation date is set and sponsor approval has been received.

B. the iteration testing deadline arrives and code testing must stop.

C. failing to make a decision eliminates an important alternative.

D. release planning is complete and the first iteration planning starts.