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

Question

Options

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

• A
  76% (29)
• B
  8% (3)
• D
  16% (6)

Explanation

Funnel and Analysis are the two Portfolio Kanban steps where research spikes belong because both stages are fundamentally about reducing uncertainty before committing resources. In the Funnel (C), spikes help determine whether an Epic is worth pursuing at all - they answer "does this even make sense?" In Analysis (A), spikes dig deeper into technical feasibility, cost, and risk so the Epic can be properly sized before entering the Portfolio Backlog. Option B is wrong because by the time an Epic reaches Implementing, major unknowns should already be resolved - spikes there indicate a failure of earlier discovery, not a planned step. Option D is wrong because the Portfolio Backlog is a holding queue for work ready to be pulled into development; introducing spikes there creates unnecessary delay and signals the Epic wasn't properly analyzed.

Memory tip: Think "FA before you commit" - Funnel and Analysis are your spike windows. Once an Epic passes Analysis, the big questions should already be answered.

No community discussion yet for this question.