Story points and velocity in Agile in Software Engineering - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define what a story point measures in Agile.

Software Engineering

A story point is a unit used to estimate the [1] of a user story.

Drag options to blanks, or click blank then click option'

Adeadline

Bcomplexity

Ccost

Dteam size

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing story points with hours or deadlines.

Thinking story points measure cost or team size.

Story points measure the complexity or effort required to complete a user story, not the deadline or cost.

2fill in blank

medium

Complete the sentence to explain velocity in Agile.

Software Engineering

Velocity is the amount of [1] a team completes in a sprint.

Drag options to blanks, or click blank then click option'

Astory points

Bbugs

Cmeetings

Dcode lines

Attempts:

3 left

💡 Hint

Common Mistakes

Thinking velocity counts bugs fixed or lines of code.

Confusing velocity with number of meetings.

Velocity measures how many story points a team finishes during a sprint, showing their delivery speed.

3fill in blank

hard

Fix the error in the statement about story points.

Software Engineering

Story points are measured in [1] like hours or days.

Drag options to blanks, or click blank then click option'

Acurrency

Bunits

Cteam members

Dtime

Attempts:

3 left

💡 Hint

Common Mistakes

Assuming story points equal hours or days.

Confusing story points with currency or team size.

Story points are not measured in time units like hours or days; they measure relative effort or complexity.

4fill in blank

hard

Fill both blanks to describe how velocity helps Agile teams.

Software Engineering

Velocity helps teams [1] their future [2] more accurately.

Drag options to blanks, or click blank then click option'

Apredict

Bdeadlines

Cplan

Dresources

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up planning with resource allocation.

Thinking velocity helps set deadlines directly.

Velocity allows teams to predict and plan their future work better by understanding their delivery rate.

5fill in blank

hard

Fill all three blanks to complete the formula for calculating velocity.

Software Engineering

Velocity = sum of [1] completed in [2] divided by number of [3].

Drag options to blanks, or click blank then click option'

Astory points

Bsprint

Csprints

Dteam members

Attempts:

3 left

💡 Hint

Common Mistakes

Using team members instead of sprints in the formula.

Confusing sprint with sprint count.

Velocity is calculated as the total story points completed in sprints divided by the number of sprints considered, showing average delivery.

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