Story points and velocity in Agile in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Story Points

What do story points primarily measure in Agile project management?

A The amount of time in hours a task will take

B The exact cost of completing a task

C The relative effort and complexity of a task

D The number of team members required for a task

💡 Hint

Think about what story points help teams estimate beyond just time.

Story points measure the relative effort, complexity, and uncertainty of a task, not exact time or cost.

📋 Factual

intermediate

Velocity Calculation

How is velocity calculated in an Agile team?

A Sum of story points completed in a sprint

B Number of tasks assigned in a sprint

C Total hours worked by the team in a sprint

D Number of bugs fixed in a sprint

💡 Hint

Velocity relates to completed work measured in story points.

Velocity is the total story points of all user stories completed during a sprint.

🚀 Application

advanced

Using Velocity for Sprint Planning

If a team’s average velocity is 30 story points per sprint, how many story points should they plan for the next sprint to avoid overcommitment?

A Exactly 30 story points to match past performance

B Less than 30 story points to allow buffer for unexpected work

C More than 30 story points to increase productivity

D Zero story points to focus on fixing bugs only

💡 Hint

Consider realistic planning and avoiding overload.

Planning slightly less than average velocity helps manage risks and unexpected tasks.

🔍 Analysis

advanced

Interpreting Velocity Fluctuations

What could be a likely reason if a team’s velocity drops significantly for two consecutive sprints?

A The story points were underestimated in previous sprints

B The team size increased suddenly

C The team is working on simpler tasks

D There are blockers or unexpected issues slowing progress

💡 Hint

Think about what usually causes delays or slowdowns in work.

Blockers or unexpected problems reduce the amount of work completed, lowering velocity.

❓ Reasoning

expert

Comparing Story Points Across Teams

Why is it not recommended to compare story points between different Agile teams?

A Because each team estimates story points based on their own context and scale

B Because story points are absolute measures of time

C Because story points are only used for bug tracking

D Because velocity is the same for all teams regardless of story points

💡 Hint

Consider how story points are assigned and what they represent.

Story points are relative and subjective; each team defines their own scale, so direct comparison is misleading.

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