Scaled Agile SAFe-POPM Exam - Topic 1 Question 18 Discussion

Actual exam question for Scaled Agile's SAFe-POPM exam

Question #: 18
Topic #: 1

[All SAFe-POPM Questions]

What is one method to establish a team's velocity?

ACalculate the percentage planned versus actual Stories completed during an Iteration

BAdd the Story points for all Features completed in the Iteration

CCompare the average Story points completed throughout the previous Iterations

DAdd the Story points for all the Stories planned for the Iteration

Show Suggested Answer

Suggested Answer: C

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

by Ling at Sep 17, 2024, 06:47 AM

Limited Time Offer

25%

Off

Get Premium SAFe-POPM Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Cathern

5 months ago

A seems a bit off, we need actual completed work, not just planned.

upvoted 0 times

...

Vinnie

6 months ago

Surprised that D is even an option. Doesn't that just show planned work?

upvoted 0 times

...

Marilynn

6 months ago

Wait, isn't C more accurate since it considers past performance?

upvoted 0 times

...

Michel

6 months ago

Totally agree with B! It's straightforward.

upvoted 0 times

...

Josphine

6 months ago

I think option B is the best way to measure velocity.

upvoted 0 times

...

Janna

6 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.

upvoted 0 times

...

Santos

7 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.

upvoted 0 times

...

Belen

7 months 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.

upvoted 0 times

...

Matthew

7 months 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.

upvoted 0 times

...

Adela

7 months 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.

upvoted 0 times

...

Beckie

7 months 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.

upvoted 0 times

...

Rupert

7 months 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.

upvoted 0 times

...

Kimberely

7 months 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.

upvoted 0 times

...

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.

upvoted 0 times

Matilda

2 years ago

I see your point, but I still think option A is the most accurate method for establishing team velocity.

upvoted 0 times

...

Sabrina

2 years ago

I prefer option C, looking at the average Story points completed in previous Iterations gives a good indication of velocity.

upvoted 0 times

...

Maryanne

2 years ago

I think option B could also be useful, adding up the Story points for completed Features.

upvoted 0 times

...

Irving

2 years ago

I agree, tracking planned versus actual is crucial for understanding team velocity.

upvoted 0 times

...

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!

upvoted 0 times

...

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?

upvoted 0 times

Charlene

1 year ago

C) Compare the average Story points completed throughout the previous Iterations

upvoted 0 times

...

Laine

1 year ago

B) Add the Story points for all Features completed in the Iteration

upvoted 0 times

...

Franchesca

2 years ago

A) Calculate the percentage planned versus actual Stories completed during an Iteration

upvoted 0 times

...

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.

upvoted 0 times

Fabiola

2 years ago

I prefer option C, comparing the average story points completed in previous iterations gives a good baseline.

upvoted 0 times

...

Elbert

2 years ago

I think option A could also be useful to track the planned versus actual stories completed.

upvoted 0 times

...

Carin

2 years ago

I agree, option B is a good method to establish the team's velocity.

upvoted 0 times

...

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.

upvoted 0 times

...