What is one recommended way of splitting Features into Stories during a PI Planning event?

Question

Options

• ADevelop the user interface (UI) with sample business logic and database access and then add the
• BImplement the database structure first and then implement the business logic and user interface
• CDevelop the functionality first and then test it on a second pass
• DImplement the simplest variant of the functionality first and then implement the rest as an

• A
  5% (1)
• B
  14% (3)
• C
  10% (2)
• D
  71% (15)

Explanation

Option D is correct because SAFe's recommended splitting strategy during PI Planning is to implement a thin vertical slice - the simplest end-to-end version of the functionality first, then elaborate it in subsequent Stories. This delivers working, testable value early and lets the team validate assumptions incrementally before investing in the full feature.

Why the distractors are wrong:

• A and B both describe horizontal (layer-by-layer) splitting - UI-first or database-first - which produces Stories that deliver no standalone business value until all layers are complete. SAFe explicitly discourages this.
• C describes a mini-waterfall within a Story (build everything, then test), which violates the agile principle of continuous quality and built-in testing.

Memory tip: Think of splitting a Feature like cutting a cake - you want vertical slices (a thin piece that includes all layers) rather than horizontal slabs (frosting first, then sponge). "Simplest variant first" = the thinnest vertical slice that still delivers value end-to-end.

No community discussion yet for this question.