SAFE-SPC practice question 6 of 25

You are working with an ART that is preparing for their first PI Planning event. All Features are formulated and ready for WSJF prioritization. However, when you look over the list of Features, it turns out that they are big tasks rather than Features. What technique would be useful to fix the list of backlog items to be able to apply WSJF?

Full set: 179 questions
Answer options
A: Split the backlog items into smaller, more manageable pieces of work and rearrange them into real Features. Correct answer
B: Formulate business benefits for each backlog item. If no meaningful business benefits can be identified, it's not a Feature and should be redefined.
C: Build explicit dependencies between backlog items. If B depends on A for completion, make sure that the opportunity enablement WSJF is a parameter of A.
D: Identify the associated Epics when formulating Features.
Correct Answer:
A. Split the backlog items into smaller, more manageable pieces of work and rearrange them into real Features.
Explanation

Features in SAFe should be right-sized, delivering value and being small enough for incremental delivery within a PI. If the current backlog items are too large (“big tasks”), the best technique is to split them into smaller, more manageable Features. This enables meaningful WSJF prioritization and supports flow-based delivery.
Reference: SAFe 6.0 Website: Features and Capabilities SPC 6.0 Guide: “Right-size Features to fit within a PI for effective prioritization and delivery.” ===========

Scroll to Top