Story points and velocity in Agile in Software Engineering - Cheat Sheet & Quick Revision

Recall & Review

beginner

What are story points in Agile?

Story points are a way to measure the effort needed to complete a task or user story. They consider complexity, time, and risk, but are not tied to exact hours.

beginner

How is velocity used in Agile teams?

Velocity is the amount of work a team completes in a sprint, usually measured in story points. It helps predict how much work the team can do in future sprints.

intermediate

Why don't Agile teams use exact hours for estimating tasks?

Exact hours can be misleading because tasks vary in complexity and uncertainty. Story points allow teams to estimate effort more flexibly and focus on relative size.

intermediate

What does a stable velocity indicate about an Agile team?

A stable velocity means the team’s work output is consistent over time, which helps in reliable sprint planning and forecasting project timelines.

advanced

Can velocity be used to compare different Agile teams? Why or why not?

No, velocity is unique to each team because story points are relative and based on that team’s understanding. Comparing velocities between teams can be misleading.

What do story points measure in Agile?

A Exact hours to complete a task

B Effort and complexity of a task

C Number of team members

D Project budget

Story points measure the effort and complexity, not exact hours or other unrelated factors.

Velocity in Agile is usually measured in:

A Story points completed per sprint

B Number of bugs fixed

C Hours worked per day

D Lines of code written

Velocity tracks how many story points a team completes in a sprint to help plan future work.

Why is velocity not a good metric to compare different Agile teams?

A Because teams use different story point scales

B Because velocity measures bugs

C Because velocity is based on hours

D Because velocity changes daily

Each team defines story points differently, so velocity is unique to each team.

What does a sudden drop in velocity usually indicate?

A Sprint length has changed

B Team is working faster

C Story points have increased

D Team is facing challenges or blockers

A drop in velocity often means the team encountered problems slowing progress.

Which of these is NOT a factor considered in story points?

A Task complexity

B Risk and uncertainty

C Exact time in hours

D Effort required

Story points do not measure exact time but relative effort and complexity.

Explain what story points are and why Agile teams use them instead of exact hours.

Think about how teams estimate work without guessing exact time.

Describe how velocity helps Agile teams plan their work and what it means if velocity changes.

Consider velocity as a team’s speed in completing work.

Practice

1. What do story points represent in Agile project management?

easy

A. The deadline for completing a project

B. The exact number of hours needed to finish a task

C. A relative measure of effort required to complete a task

D. The total number of tasks in a sprint

Solution

1. Step 1: Understand story points concept

   Story points are used to estimate how much effort a task will take compared to other tasks, not exact hours.

2. Step 2: Differentiate from time estimates

   Unlike hours, story points are relative and help teams compare tasks easily.

3. Final Answer:

   A relative measure of effort required to complete a task -> Option C

4. Quick Check:

   Story points = relative effort [OK]

Hint: Story points measure effort, not exact time [OK]

Common Mistakes:

• Confusing story points with hours
• Thinking story points count tasks
• Mixing story points with deadlines

2. Which of the following best defines velocity in Agile?

easy

A. The total story points completed in a sprint

B. The time taken to complete a single task

C. The number of team members working on a sprint

D. The number of meetings held during a sprint

Solution

1. Step 1: Identify velocity meaning

   Velocity is the sum of story points completed by the team in one sprint.

2. Step 2: Exclude unrelated options

   Team size, task time, and meetings do not define velocity.

3. Final Answer:

   The total story points completed in a sprint -> Option A

4. Quick Check:

   Velocity = completed story points [OK]

Hint: Velocity sums completed story points per sprint [OK]

Common Mistakes:

• Confusing velocity with team size
• Thinking velocity is task duration
• Mixing velocity with number of meetings

3. A team completed tasks with story points: 3, 5, 2, and 8 in a sprint. What is their velocity?

medium

A. 20

B. 18

C. 10

D. 8

Solution

1. Step 1: Add all completed story points

   Sum = 3 + 5 + 2 + 8 = 18

2. Step 2: Confirm velocity definition

   Velocity is total story points done in sprint, so 18 is correct.

3. Final Answer:

   18 -> Option B

4. Quick Check:

   3+5+2+8 = 18 [OK]

Hint: Add all completed story points for velocity [OK]

Common Mistakes:

• Adding incorrectly
• Choosing highest single story point
• Confusing velocity with number of tasks

4. A team planned 30 story points for a sprint but completed only 22. What is the velocity and what does it indicate?

medium

A. Velocity is 22; team completed less than planned

B. Velocity is 30; team met the plan

C. Velocity is 52; sum of planned and completed

D. Velocity is 8; difference between planned and completed

Solution

1. Step 1: Identify velocity from completed points

   Velocity equals story points actually completed, which is 22.

2. Step 2: Interpret velocity vs plan

   Since 22 is less than planned 30, team completed fewer points than expected.

3. Final Answer:

   Velocity is 22; team completed less than planned -> Option A

4. Quick Check:

   Velocity = completed points = 22 [OK]

Hint: Velocity = completed points, not planned [OK]

Common Mistakes:

• Using planned points as velocity
• Adding planned and completed points
• Using difference as velocity

5. If a team's average velocity is 25 story points per sprint, how many sprints will they need to complete a backlog of 120 story points?

hard

A. 3

B. 4

C. 6

D. 5

Solution

1. Step 1: Calculate number of sprints needed

   Divide total backlog points by average velocity: 120 ÷ 25 = 4.8 sprints.

2. Step 2: Round up to whole sprints

   Since partial sprints are not practical, round up to 5 sprints.

3. Final Answer:

   5 -> Option D

4. Quick Check:

   120/25 ≈ 5 sprints [OK]

Hint: Divide backlog by velocity, round up [OK]

Common Mistakes:

• Rounding down instead of up
• Using velocity as planned points
• Ignoring partial sprint calculation