Scaled Agile SAFe-SPC Exam - Topic 6 Question 17 Discussion

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

Question #: 17
Topic #: 6

An Agile Release Train prepares for PI Planning. They have both Features and Program Epics among the desirable items for this PI. However, Product Management is stuck because some Epics are too big and won't fit in this PI.

APick only those Epics that have clearly defined success criteria and might fit into the PI.

BSplit Epics into Features and prioritize the Features to determine what should go into the PI.

CSplit Epics into Features and use capacity allocation to determine what should go into the PI.

DInstead of planning just the upcoming PI, plan for a longer period to cover the full duration of the Program Epics.

Show Suggested Answer

Suggested Answer: A, B

by Isadora at May 24, 2024, 12:20 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Dottie

3 months ago

D could lead to scope creep, not sure that's a good idea.

upvoted 0 times

...

Stephaine

3 months ago

Wait, can we really split Epics like that? Seems risky.

upvoted 0 times

...

Nadine

3 months ago

A sounds too limiting, we need to think bigger!

upvoted 0 times

...

Phyliss

4 months ago

I think C is better, capacity allocation helps with planning.

upvoted 0 times

...

Lashaun

4 months ago

B is the way to go, splitting makes it manageable!

upvoted 0 times

...

Phuong

4 months ago

I recall that planning for a longer period could lead to scope creep. It might be better to focus on what we can realistically achieve in this PI.

upvoted 0 times

...

Roxane

4 months ago

I feel like picking only Epics with clear success criteria might limit us too much. What if we miss out on something important?

upvoted 0 times

...

Thora

5 months ago

I think we practiced a similar question where we had to decide on Epics, and I leaned towards splitting them into Features. It seems like the most logical step.

upvoted 0 times

...

Michell

5 months ago

I remember we discussed how splitting Epics into Features can help with prioritization, but I'm not sure if capacity allocation is necessary.

upvoted 0 times

...

Catalina

5 months ago

I think option C is the way to go. Using capacity allocation to determine what fits in the PI makes the most sense.

upvoted 0 times

...

Denny

5 months ago

I'm a bit confused by the difference between Epics and Features. Can someone clarify that for me?

upvoted 0 times

...

Reynalda

5 months ago

Hmm, splitting the Epics into Features seems like a good approach to me. That way we can prioritize what's most important.

upvoted 0 times

...

Alline

5 months ago

This looks like a tricky one. I'll need to think through the options carefully.

upvoted 0 times

...

Margo

5 months ago

I'm feeling pretty confident about this one. Option B is the clear winner in my opinion.

upvoted 0 times

...

Stephaine

5 months ago

Okay, let me see... I know that global choices are available across the entire Dataverse environment, while local choices are specific to a single table. But I'm not sure which one would be the best option here to ensure other users can access the Choice field.

upvoted 0 times

...

Glory

5 months ago

No problem, I've got this. A, B, and C are the correct functions available to grid users. I'm confident in my answer.

upvoted 0 times

...

Dana

5 months ago

Hmm, I'm a bit unsure about this one. The question is asking for the command to configure Router 2 as a server-only mode, but the options don't seem to directly address that. I'll need to think this through carefully.

upvoted 0 times

...

Devora

5 months ago

Hmm, I'm a bit unsure about this one. I know SSH is used for remote access, but I'm not totally clear on the specific commands for managing authentication keys. I'll have to think this through carefully.

upvoted 0 times

...

Micaela

5 months ago

Okay, let me see if I can break this down. A DHCP client is the host that requests an IP address, not the server that assigns it. So I'm going to go with A on this one.

upvoted 0 times

...

Xenia

9 months ago

What, no option for 'Throw up your hands and go home'? That's my kind of planning approach.

upvoted 0 times

...

Howard

10 months ago

A) Pick only those Epics that have clearly defined success criteria and might fit into the PI. Sounds like a good way to keep things simple and focused.

upvoted 0 times

Elden

8 months ago

User 4: And use capacity allocation to ensure we're not overcommitting.

upvoted 0 times

...

Alita

8 months ago

User 3: We should prioritize the Features within those Epics to make sure we're on track.

upvoted 0 times

...

Buck

8 months ago

User 2: Agreed, that way we can stay focused on what's achievable.

upvoted 0 times

...

Mariann

9 months ago

User 1: Let's pick only the Epics with clear success criteria for this PI.

upvoted 0 times

...

Ashton

10 months ago

D) Instead of planning just the upcoming PI, plan for a longer period to cover the full duration of the Program Epics. This could be a good way to get a handle on those big Epics.

upvoted 0 times

Fatima

8 months ago

C) Split Epics into Features and use capacity allocation to determine what should go into the PI.

upvoted 0 times

...

Chandra

8 months ago

B) Split Epics into Features and prioritize the Features to determine what should go into the PI.

upvoted 0 times

...

Georgeanna

9 months ago

A) Pick only those Epics that have clearly defined success criteria and might fit into the PI.

upvoted 0 times

...

Kallie

9 months ago

C) Split Epics into Features and use capacity allocation to determine what should go into the PI.

upvoted 0 times

...

Pansy

9 months ago

B) Split Epics into Features and prioritize the Features to determine what should go into the PI.

upvoted 0 times

...

Billye

10 months ago

A) Pick only those Epics that have clearly defined success criteria and might fit into the PI.

upvoted 0 times

...

Stefania

10 months ago

C) Split Epics into Features and use capacity allocation to determine what should go into the PI. I like the idea of considering the team's capacity when deciding what to include.

upvoted 0 times

Freida

9 months ago

User 4: Definitely. We don't want to overload the team and risk not delivering on our commitments.

upvoted 0 times

...

Alaine

9 months ago

User 3: I agree. It's important to consider the team's capacity when planning for the PI.

upvoted 0 times

...

Melissa

9 months ago

User 2: That sounds like a good approach. We need to make sure we can realistically complete everything in the PI.

upvoted 0 times

...

Hui

10 months ago

User 1: Let's split the Epics into Features and use capacity allocation to decide what goes into the PI.

upvoted 0 times

...

Levi

11 months ago

But what if we split the Epics into Features and prioritize them instead?

upvoted 0 times

...

Von

11 months ago

I agree with Adell. It will help us focus on what's achievable in this PI.

upvoted 0 times

...

Merilyn

11 months ago

B) Split Epics into Features and prioritize the Features to determine what should go into the PI. This seems like the most logical approach to me. Breaking down those massive Epics is the way to go.

upvoted 0 times