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

- Free Preparation Discussions

Scaled Agile SAFe-SPC Exam - Topic 1 Question 43 Discussion

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

Question #: 43
Topic #: 1

[All SAFe-SPC Questions]

(Select 2) What steps in the Portfolio Kanban are most appropriate for running research spikes?

AAnalysis---spikes help clarify feasibility.

BImplementing---teams perform spikes as usual

CFunnel---understand whether the Epic makes sense.

DPortfolio Backlog---run a spike before pulling into development.

Show Suggested Answer

Suggested Answer: A, C

A: During the Analysis step, research spikes (time-boxed investigations) are used to clarify feasibility, identify unknowns, and gather data for decision making.

C: In the Funnel step, early research or spikes help determine if the Epic is even worth advancing, especially for innovations or high-risk items.

Portfolio Backlog (D) is for items already accepted for future implementation; it's generally too late for basic research spikes. Implementing (B) is for execution, not discovery.

SAFe 6.0 Website: Portfolio Kanban

SPC 6.0 Guide: ''Spikes are often run during the Funnel and Analysis steps to clarify scope, feasibility, and business case.''

===========

by Erasmo at Jul 14, 2025, 07:04 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Selma

8 months ago

D is a must! Spikes should be done before dev starts.

upvoted 0 times

...

Clare

8 months ago

Totally agree with A! Feasibility is key.

upvoted 0 times

...

Virgilio

8 months ago

I feel uncertain about "Implementing" being a step for spikes; it seems more like a regular task rather than a research phase.

upvoted 0 times

...

Cordell

8 months ago

I think A and D make the most sense for research spikes.

upvoted 0 times

...

Jaime

8 months ago

I'm leaning towards "Portfolio Backlog" because it seems logical to run a spike before pulling something into development, but I could be wrong.

upvoted 0 times

...

Nana

9 months ago

I remember practicing a question similar to this, and I think "Funnel" makes sense to evaluate if the Epic is worth pursuing.

upvoted 0 times

...

Alysa

9 months ago

Wait, can spikes really clarify feasibility like that?

upvoted 0 times

...

Shawnee

9 months ago

C is also important to gauge the Epic's value.

upvoted 0 times

...

Gianna

9 months ago

I think "Analysis" is definitely one of the steps since spikes help clarify feasibility, but I'm not sure about the second one.

upvoted 0 times

...

Alberta

10 months ago

I'm pretty confident that the Analysis and Portfolio Backlog steps are the right answers here. Spikes help clarify feasibility, and should be done before pulling work into the development process. That's how I'd approach this question.

upvoted 0 times

...

Renato

10 months ago

The Funnel step seems like a good place to run research spikes, to understand whether the Epic makes sense before committing to it. But I'm not 100% sure on that. Guess I'll have to review the Portfolio Kanban process again.

upvoted 0 times

...

Sage

10 months ago

I'm a bit confused on this one. I know spikes are used to explore technical feasibility, but I'm not sure which specific steps in the Portfolio Kanban they would fit into. I'll have to think this through more carefully.

upvoted 0 times

...

Dion

10 months ago

I think the Analysis and Portfolio Backlog steps would be most appropriate for running research spikes. Spikes help clarify feasibility and should be done before pulling work into development.

upvoted 0 times

...

Jackie

10 months ago

I'm pretty confident that the Analysis and Portfolio Backlog steps are the most appropriate for research spikes. Spikes help clarify feasibility and you'd want to do that research before committing the Epic to development.

upvoted 0 times

...

Kristian

11 months ago

The Funnel step seems like a good place to run research spikes, to understand whether the Epic makes sense before moving forward. And the Portfolio Backlog step also seems relevant, to do the spike before pulling it into development.

upvoted 0 times

...

Cathrine

11 months ago

I'm a bit confused on this one. I know spikes are used to explore technical feasibility, but I'm not sure which specific steps in the Portfolio Kanban process they would fit into. I'll have to think this through carefully.

upvoted 0 times

...

Nadine

11 months ago

I think the Analysis and Portfolio Backlog steps would be most appropriate for running research spikes. Spikes help clarify feasibility and understand the Epic before pulling it into development.

upvoted 0 times

...

Joye

12 months ago

Funny how B is Joyen an option. That's like putting the cart before the horse! Definitely C and D for me.

upvoted 0 times

Clay

11 months ago

I agree, C and D make more sense for research spikes.

upvoted 0 times

...

...

Lauran

1 year ago

Hmm, I'd say C and D. Gotta make sure the Epic makes sense before we start sinking time and resources into it. Spikes are like the pre-flight check for our Kanban.

upvoted 0 times

...

Alyce

1 year ago

Haha, B? Really? Teams performing spikes as usual? That's like saying we should implement the feature we're trying to understand. Nah, C and D are the way to go.

upvoted 0 times

Yuonne

11 months ago

Yeah, I agree with you. Running a spike before pulling into development makes more sense.

upvoted 0 times

...

...

Kerry

1 year ago

But shouldn't we also consider understanding whether the Epic makes sense in the Funnel step?

upvoted 0 times

...

Doyle

1 year ago

I agree, it helps clarify feasibility before committing resources.

upvoted 0 times

...

Juan

1 year ago

I think running a spike before pulling into development is important.

upvoted 0 times

...

Timothy

1 year ago

I'd go with A and D. Spikes are great for clarifying requirements and making sure we're on the right track before pulling anything into dev.

upvoted 0 times

Theron

1 year ago

D) Portfolio Backlog---run a spike before pulling into development.

upvoted 0 times

...

Levi

1 year ago

A) Analysis---spikes help clarify feasibility.

upvoted 0 times

...

...

Malika

1 year ago

C and D, definitely. Spikes are all about understanding the feasibility and value of Epics before committing to them.

upvoted 0 times

Noah

1 year ago

Spikes help clarify feasibility, so Analysis and Portfolio Backlog are key steps to take.

upvoted 0 times

...

Ramonita

1 year ago

C and D are crucial for running research spikes. It's important to understand the value before committing.

upvoted 0 times

...

Ressie

1 year ago

Running a spike before pulling into development from the Portfolio Backlog ensures you have a clear understanding before moving forward.

upvoted 0 times

...

Jesus

1 year ago

Spikes help clarify whether the Epic makes sense, so starting at the Funnel stage is key.

upvoted 0 times

...

Erin

1 year ago

C and D are crucial for running research spikes. It's important to understand the feasibility and value before committing.

upvoted 0 times

...

...