MENU
What is one method to establish a team's velocity?
Suggested Answer: C
Get Premium SAFe-POPM Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
One method to establish a team's velocity is to compare the average story points completed throughout the previous iterations. This gives an indication of how much work the team can realistically deliver in a given time frame, based on their past performance. To calculate the team's velocity, you can use the following formula: Team velocity = total story points completed / number of iterations. You can also use various charts and tools to visualize the team's velocity and track its progress over time1234
* Velocity in Scrum: How to Measure and Improve Performance - Atlassian
* Discover the Concept of Team Velocity - OpenClassrooms
* A Word on Velocity - LeadingAgile
* Increasing Your Scrum Team's Velocity --- ClearlyAgile
35 comments · newest first
CA
Cathern
11 months ago
A seems a bit off, we need actual completed work, not just planned.
VI
Vinnie
11 months ago
Surprised that D is even an option. Doesn't that just show planned work?
MA
Marilynn
11 months ago
Wait, isn't C more accurate since it considers past performance?
MI
Michel
11 months ago
Totally agree with B! It's straightforward.
JO
Josphine
12 months ago
I think option B is the best way to measure velocity.
JA
Janna
12 months ago
I feel like adding Story points for all planned Stories might not give an accurate velocity since it doesn't account for what was actually completed.
SA
Santos
12 months ago
Comparing average Story points from previous Iterations seems like a solid approach, but I can't recall if that's what we focused on in class.
BE
Belen
1 year ago
I remember practicing a question where we had to add up the Story points for completed Features, so I think option B sounds familiar and might be correct.
MA
Matthew
1 year ago
I think calculating the percentage of planned versus actual Stories completed could be a way to measure velocity, but I'm not sure if that's the best method.
AD
Adela
1 year ago
Ah, I see what they're getting at. Velocity is about looking at the Story points completed over time to get a sense of the team's consistent throughput. I think comparing the average across previous Iterations is the way to go.
BE
Beckie
1 year ago
Okay, I've got this. Velocity is all about measuring the actual work completed versus what was planned. I'm pretty sure the right answer is to calculate the percentage of planned versus actual Stories completed.
RU
Rupert
1 year ago
Hmm, I'm a bit unsure about this one. I know velocity is important, but I'm not totally clear on the different ways to calculate it. I'll have to think this through carefully.
KI
Kimberely
1 year ago
This seems like a straightforward question about Agile project management. I think the key is to focus on how teams track their progress during an Iteration.
ST
Stephaine
2 years ago
As a former project manager, I can tell you that option A is the way to go. Gotta track that planned vs. actual to get the true velocity.
MA
Matilda
2 years ago
I see your point, but I still think option A is the most accurate method for establishing team velocity.
SA
Sabrina
2 years ago
I prefer option C, looking at the average Story points completed in previous Iterations gives a good indication of velocity.
MA
Maryanne
2 years ago
I think option B could also be useful, adding up the Story points for completed Features.
IR
Irving
2 years ago
I agree, tracking planned versus actual is crucial for understanding team velocity.
ST
Stacey
2 years ago
Haha, option D sounds like the team's 'wish list' velocity, not the real deal. Give me option C any day!
AB
Abraham
2 years ago
Hmm, I'm not sure about option D. Wouldn't that just be the planned velocity, not the actual velocity the team achieved?
CH
Charlene
2 years ago
C) Compare the average Story points completed throughout the previous Iterations
LA
Laine
2 years ago
B) Add the Story points for all Features completed in the Iteration
FR
Franchesca
2 years ago
A) Calculate the percentage planned versus actual Stories completed during an Iteration
CR
Crista
2 years ago
I'm going with option B. Adding up the story points for all completed features gives a clear picture of the team's output.
FA
Fabiola
2 years ago
I prefer option C, comparing the average story points completed in previous iterations gives a good baseline.
EL
Elbert
2 years ago
I think option A could also be useful to track the planned versus actual stories completed.
CA
Carin
2 years ago
I agree, option B is a good method to establish the team's velocity.
TA
Tawna
2 years ago
I think C) Compare the average Story points completed throughout the previous Iterations makes more sense, as it gives a better overall picture of the team's velocity.
CO
Corinne
2 years ago
I disagree, I believe the answer is B) Add the Story points for all Features completed in the Iteration.
RE
Refugia
2 years ago
Option C sounds like the way to go. Tracking the average story points completed over time is a great way to measure team velocity.
EL
Elvis
2 years ago
That's true, it's important to track how well the team is meeting their planned goals.
DE
Dell
2 years ago
A) Calculate the percentage planned versus actual Stories completed during an Iteration
SH
Shenika
2 years ago
That makes sense, it gives a good overall picture of the team's performance.
LE
Leoma
2 years ago
C) Compare the average Story points completed throughout the previous Iterations
IL
Ilda
2 years ago
I think the answer is A) Calculate the percentage planned versus actual Stories completed during an Iteration.