MENU
How does a team calculate its initial velocity during its first PI Planning meeting when teams don't have historic data?
Suggested Answer: B
Get Premium SAFe-SPC Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
HE
Hershel
11 months ago
Option B makes sense, but it feels risky to wait that long!
HE
Helene
11 months ago
I think rolling up team velocities is a better approach.
DE
Destiny
11 months ago
Wait, how can you guess velocity without any data?
ME
Melodie
11 months ago
Totally agree, option A seems practical!
MO
Moira
12 months ago
I heard assigning points per team member is common.
KA
Karon
12 months ago
I thought we agreed that calculating velocity right away could lead to inaccuracies, so option B seems reasonable to me.
ST
Stephaine
12 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.
BE
Beth
1 year ago
I feel like we practiced something similar where teams just estimate their capacity first. Could it be option C?
CA
Carmen
1 year 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.
PA
Patrick
1 year 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.
VI
Vincent
1 year 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.
DO
Dorthy
1 year 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.
ES
Esteban
1 year 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.
CA
Carmelina
1 year 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.
GE
Geraldine
1 year 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.
VI
Vince
1 year ago
I feel like high interobserver agreement is important, but I'm not confident it defines a valid data recording system.
CA
Cathrine
1 year 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.
AR
Arlette
1 year ago
Calculating velocity without data? Sounds like a recipe for disaster, like trying to navigate a maze with your eyes closed.
GR
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.
CR
Cristal
1 year ago
I think it's important to establish a baseline for velocity early on, and option A helps with that.
IS
Isaiah
1 year ago
It definitely simplifies the process and provides a consistent method for all teams.
MI
Mitsue
1 year ago
I agree, option A seems like the most practical approach for calculating initial velocity.
FR
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.
DA
Danica
1 year ago
Exactly, continuous improvement is key in Agile practices.
DE
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.
BI
Billy
1 year ago
But what if some teams overestimate or underestimate their velocity?
CO
Corinne
1 year ago
I agree, option C allows for autonomy and trust in the team's capabilities.
PA
Patria
2 years 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!
CO
Cordell
1 year ago
User 2: I agree, we don't want to set unrealistic expectations right from the start.
GI
Gianna
1 year ago
User 1: Option D does sound tempting, but we should consider the team's capacity too.
JE
Jesusita
2 years 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.
AR
Ardella
2 years ago
I agree with Deonna, option C seems more flexible and realistic for our team.
DE
Deonna
2 years ago
I disagree, I believe option C is better as it allows teams to establish their own velocity.
BR
Brittni
2 years ago
I think we should go with option A and assign 8 points per team member.