Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Scaled Agile SAFe-SPC Exam - Topic 8 Question 19 Discussion

How does a team calculate its initial velocity during its first PI Planning meeting when teams don't have historic data?
B) It is not recommended to calculate velocity until the team has completed its first PI.
A) Assign 8 points per team member (not counting the Scrum Master and Product Owner) and subtract 1 point for each holiday or vacation day.
C) Allow teams to establish their own velocity and then roll them up to calculate the velocity of the train.
D) Assign 10 points per team member (not counting the Scrum Master and Product Owner) and subtract 1 point for each holiday or vacation day.

Scaled Agile SAFe-SPC Exam - Topic 8 Question 19 Discussion

Actual exam question for Scaled Agile's SAFe-SPC exam
Question #: 19
Topic #: 8
[All SAFe-SPC Questions]

How does a team calculate its initial velocity during its first PI Planning meeting when teams don't have historic data?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Mabel at Jun 23, 2024, 04:03 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Hershel
9 months ago
Option B makes sense, but it feels risky to wait that long!
upvoted 0 times
...
Helene
9 months ago
I think rolling up team velocities is a better approach.
upvoted 0 times
...
Destiny
10 months ago
Wait, how can you guess velocity without any data?
upvoted 0 times
...
Melodie
10 months ago
Totally agree, option A seems practical!
upvoted 0 times
...
Moira
10 months ago
I heard assigning points per team member is common.
upvoted 0 times
...
Karon
10 months ago
I thought we agreed that calculating velocity right away could lead to inaccuracies, so option B seems reasonable to me.
upvoted 0 times
...
Stephaine
10 months ago
I'm not entirely sure, but I think we talked about assigning points based on team members. Was it 8 or 10 points? That makes me lean towards option A or D.
upvoted 0 times
...
Beth
11 months ago
I feel like we practiced something similar where teams just estimate their capacity first. Could it be option C?
upvoted 0 times
...
Carmen
11 months ago
I remember we discussed that it's tricky to calculate velocity without historical data, but I think option B might be the safest choice.
upvoted 0 times
...
Patrick
11 months ago
I like option C - letting the teams establish their own velocity and then rolling them up to calculate the train's velocity. That seems like a more collaborative and flexible approach, especially for teams that are just starting out.
upvoted 0 times
...
Vincent
11 months ago
Hmm, I think option B is the way to go. It's not recommended to calculate velocity until the team has completed its first PI, so we should just focus on getting through that first sprint and then figure it out from there.
upvoted 0 times
...
Dorthy
11 months ago
This is a tricky one. Without any historical data, it's hard to know how to calculate the initial velocity. I'm not sure if option A or D is the right approach.
upvoted 0 times
...
Esteban
11 months ago
I'm pretty confident that option D is the correct answer. Assigning 10 points per team member and subtracting 1 point for each holiday or vacation day seems like a straightforward way to get an initial velocity, even without any prior data.
upvoted 0 times
...
Carmelina
11 months ago
Okay, let me think this through. Application-based segmentation means separating different applications on the network, right? And preventing lateral threat movement is about stopping threats from spreading across the network. I'm leaning towards App-ID, but I'll double-check my understanding just to be sure.
upvoted 0 times
...
Geraldine
11 months ago
Hmm, this looks like a tricky one. The output says the network-boot-arguments are not available, so I'm guessing that means network boot is not supported on this client. I'll probably go with option C or F.
upvoted 0 times
...
Vince
11 months ago
I feel like high interobserver agreement is important, but I'm not confident it defines a valid data recording system.
upvoted 0 times
...
Cathrine
11 months ago
This one seems tricky, but I think I know the answer. Digital signatures are designed to verify the integrity and origin of data, so the attack that would bypass that would be a replay attack.
upvoted 0 times
...
Arlette
1 year ago
Calculating velocity without data? Sounds like a recipe for disaster, like trying to navigate a maze with your eyes closed.
upvoted 0 times
...
Graciela
1 year ago
Option A is the clear winner here. 8 points per team member, minus a point for each vacation day. It's a tried and true method, like a good ol' velocity calculator recipe.
upvoted 0 times
Cristal
1 year ago
I think it's important to establish a baseline for velocity early on, and option A helps with that.
upvoted 0 times
...
Isaiah
1 year ago
It definitely simplifies the process and provides a consistent method for all teams.
upvoted 0 times
...
Mitsue
1 year ago
I agree, option A seems like the most practical approach for calculating initial velocity.
upvoted 0 times
...
...
France
1 year ago
I'm going with option C. Let the teams decide their own velocity, and then roll it up. It's like trusting the team to know what they're doing, instead of forcing them into a one-size-fits-all approach.
upvoted 0 times
Danica
1 year ago
Exactly, continuous improvement is key in Agile practices.
upvoted 0 times
...
Dean
1 year ago
That's a valid point. It's important for teams to reflect and adjust their velocity as they gain more experience.
upvoted 0 times
...
Billy
1 year ago
But what if some teams overestimate or underestimate their velocity?
upvoted 0 times
...
Corinne
1 year ago
I agree, option C allows for autonomy and trust in the team's capabilities.
upvoted 0 times
...
...
Patria
1 year ago
Oooh, option D sounds juicy! 10 points per team member, subtract a point for each holiday. That's like a sugar rush for the velocity calculation!
upvoted 0 times
Cordell
1 year ago
User 2: I agree, we don't want to set unrealistic expectations right from the start.
upvoted 0 times
...
Gianna
1 year ago
User 1: Option D does sound tempting, but we should consider the team's capacity too.
upvoted 0 times
...
...
Jesusita
1 year ago
Option B is the way to go. How can you calculate velocity without any historical data? That's like trying to run before you can walk.
upvoted 0 times
...
Ardella
1 year ago
I agree with Deonna, option C seems more flexible and realistic for our team.
upvoted 0 times
...
Deonna
1 year ago
I disagree, I believe option C is better as it allows teams to establish their own velocity.
upvoted 0 times
...
Brittni
1 year ago
I think we should go with option A and assign 8 points per team member.
upvoted 0 times
...

Save Cancel