Quiz – Team Velocity Basics

Question 1 of 6

1. Question

Velocity is calculated by:

Summing story points of all completed user stories

Correct Incorrect Correct answer

Counting hours each person worked

Correct Incorrect Correct answer

Measuring individual developer output

Correct Incorrect Correct answer

Adding up open backlog items

Correct Incorrect Correct answer

Question 2 of 6

2. Question

Velocity is best understood as:

A collective team metric, not individual performance

Correct Incorrect Correct answer

A ranking of the fastest developer

Correct Incorrect Correct answer

A fixed number that never changes

Correct Incorrect Correct answer

A budget for the project

Correct Incorrect Correct answer

Question 3 of 6

3. Question

After how many sprints do teams typically improve predictability?

Three to four sprints

Correct Incorrect Correct answer

One single sprint

Correct Incorrect Correct answer

Twenty sprints minimum

Correct Incorrect Correct answer

It never improves

Correct Incorrect Correct answer

Question 4 of 6

4. Question

In early sprints, what should teams focus on?

Trends rather than isolated numbers

Correct Incorrect Correct answer

Hitting an exact number every sprint

Correct Incorrect Correct answer

Comparing themselves to other teams

Correct Incorrect Correct answer

Maximizing points at any cost

Correct Incorrect Correct answer

Question 5 of 6

5. Question

Match each velocity idea to its meaning.

Sort elements

Completed points per sprint
Estimation improves with experience
Workload a team can maintain

Velocity

Correct Incorrect Correct answer

Cone of Uncertainty

Correct Incorrect Correct answer

Sustainable pace

Correct Incorrect Correct answer

Question 6 of 6

6. Question

In Agile, what metric sums the story points a team completes each sprint?

Correct Incorrect Correct answer