SAFE-SPC · Question #34
Backlogs in SAFe behave just like queues.
The correct answer is B. False. B is correct because SAFe backlogs are prioritized lists, not FIFO queues. In a standard queue, items are processed in the order they arrive (first-in, first-out). SAFe backlogs, by contrast, are continuously re-ranked based on business value, risk, and cost of delay - most…
Question
Backlogs in SAFe behave just like queues.
Options
- ATrue
- BFalse
How the community answered
(31 responses)- A6% (2)
- B94% (29)
Explanation
B is correct because SAFe backlogs are prioritized lists, not FIFO queues. In a standard queue, items are processed in the order they arrive (first-in, first-out). SAFe backlogs, by contrast, are continuously re-ranked based on business value, risk, and cost of delay - most commonly using Weighted Shortest Job First (WSJF) - so a newly added item can immediately jump to the top if it has the highest priority.
A is wrong because calling them equivalent ignores a core SAFe principle: backlogs require active management and re-prioritization, whereas queues are passive, order-preserving structures. SAFe even draws on Lean thinking to warn that unmanaged backlogs can accumulate like queues, which is treated as waste - reinforcing that the goal is to prevent backlog-as-queue behavior, not embrace it.
Memory tip: Think "queue = fair line at a deli counter (first come, first served)" vs. "backlog = triage room in an ER (highest priority gets seen first, regardless of arrival order)." If you remember that SAFe uses WSJF to rank work by value, you'll always know backlogs are prioritized, not sequential.
Topics
Community Discussion
No community discussion yet for this question.