AAC Agile Planning & Estimation 2

Question 1

In MoSCoW prioritization, the 'S' stands for:

Accepted Answer

Should have

Answer

Significant

Answer

Scheduled

Answer

Systematic

Question 2

T-shirt sizing (XS, S, M, L, XL) is best used during which phase of Agile planning?

Accepted Answer

High-level roadmap and portfolio-level estimation

Answer

Detailed sprint-level task breakdowns

Answer

Final acceptance testing before release

Answer

Post-sprint retrospectives

Question 3

The Cone of Uncertainty in Agile planning illustrates that:

Accepted Answer

The team's confidence increases as the project progresses and unknowns are resolved

Answer

Estimates become less reliable over time due to team turnover

Answer

Scope changes are always the result of poor initial planning

Answer

Velocity decreases predictably in the final stages of a project

Question 4

Rolling wave planning in Agile refers to the practice of:

Accepted Answer

Planning near-term work in detail while keeping future work at a higher level

Answer

Completing all planning upfront before development begins

Answer

Assigning work in waves of ten stories at a time

Answer

Re-estimating every story at the end of each sprint

Question 5

A sprint burndown chart shows:

Accepted Answer

Remaining work (story points or tasks) plotted against time within a sprint

Answer

The number of bugs introduced during the sprint

Answer

The team's cumulative velocity across all sprints

Answer

The total cost incurred by the project to date

Question 6

The INVEST criteria for user stories include which of the following attributes?

Accepted Answer

Independent, Negotiable, Valuable, Estimable, Small, Testable

Answer

Integrated, Negotiable, Valuable, Extensible, Standardized, Testable

Answer

Iterable, Normalized, Verified, Efficient, Scalable, Timely

Answer

Interactive, Networked, Verified, Executable, Structured, Trackable

Question 7

A 'spike' story in Agile planning is used to:

Accepted Answer

Allocate time for research or experimentation to reduce uncertainty before estimation

Answer

Address a sudden increase in user traffic to the application

Answer

Document technical debt discovered during a sprint

Answer

Capture emergency bug fixes that bypass normal backlog prioritization