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.