Discuss Scaled Agile SP-SAFe-Practitioner Exam Topic 1 Question 48

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

ADevelop the user interface (UI) with sample business logic and database access and then add the actual functionality behind the UI

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 enhancement

Suggested Answer: D

One of the recommended ways of splitting Features into Stories during a PI Planning event is to use thehorizontal slicingtechnique, which means implementing the simplest variant of the functionality first and then adding more complexity and variations as enhancements. This technique helps to deliver value incrementally, reduce risk, and enable fast feedback and learning. Horizontal slicing also supports the application of theMinimum Viable Product (MVP)andMinimum Marketable Feature (MMF)concepts, which aim to deliver the smallest amount of functionality that can provide value and validate assumptions.Reference:Exam Study Guide: SP (6.0) - SAFe Practitioner,Feature,Story

Get Premium SP-SAFe-Practitioner Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

30 comments · newest first

Kayleigh 6 months ago

C could work, but testing later might miss early bugs.

Silva 6 months ago

D is more user-friendly. Users appreciate gradual improvements.

German 6 months ago

Option A seems risky. UI first can lead to issues later.

Carmela 7 months ago

I agree, D allows for quick feedback.

Viola 7 months ago

B seems too rigid, we need flexibility in our planning!

Eva 7 months ago

Not sure about D, what if the enhancements take too long?

Antonio 7 months ago

Wait, isn't A more efficient for UI-heavy projects?

Joanna 8 months ago

Totally agree, starting simple makes sense!

Ariel 8 months ago

I think D is the best approach for quick wins!

Jesusita 8 months ago

B) Implement the database structure first and then implement the business logic and user interface. Gotta have a solid foundation before building the house, am I right?

Tasia 8 months ago

Haha, I bet the correct answer is "D) Implement the simplest variant of the functionality first and then implement the rest as an enhancement." Who needs all the bells and whistles when you can get the job done quickly?

Nu 8 months ago

D) Implement the simplest variant of the functionality first and then implement the rest as an enhancement. This is the most efficient way to deliver value quickly.

Percy 9 months ago

A) Develop the user interface (UI) with sample business logic and database access and then add the actual functionality behind the UI. This ensures the UI is ready for the actual implementation.

Melda 9 months ago

D) Implement the simplest variant of the functionality first and then implement the rest as an enhancement. This approach allows for quick delivery of core features and iterative improvements.

Junita 9 months ago

I’m leaning towards option D too, but I’m a bit confused about how enhancements fit into the overall planning process.

Justine 9 months ago

I’m not entirely sure, but I feel like we discussed implementing the UI first in one of our practice sessions. Was that option A?

Temeka 9 months ago

I'm not totally sure about this one. I think I'll need to review the material again before deciding on an approach.

Carin 10 months ago

Hmm, I'm leaning towards option A. Developing the UI with sample logic first seems like a good way to get a feel for the overall system.

Ruthann 10 months ago

Option B seems like the logical approach to me. Get the database set up first, then build the rest on top of that.

Andree 10 months ago

I think I remember that the simplest variant approach is often recommended, so maybe D is the right choice?

Whitney 10 months ago

I think option D is the best. Start simple, then enhance.

Britt 11 months ago

I recall something about starting with the database structure, but that seems more complex than just implementing the simplest version first.

Shalon 11 months ago

I prefer B. Database structure is foundational.

Rana 11 months ago

I'm a bit confused on this one. I'm not sure if I should focus on the UI first or the database structure. Any tips?

Stefania 11 months ago

I think option D is the way to go. Start with the simplest functionality and then build on it.

Skye 5 months ago

↳ replying to Stefania

Exactly! Iterative improvements are key.

Genevieve 6 months ago

↳ replying to Stefania

Plus, it reduces risks in the early stages.

Myra 6 months ago

↳ replying to Stefania

Definitely! It allows for quicker feedback.

Carey 6 months ago

↳ replying to Stefania

Yeah, enhancements are easier to manage.

Billy 10 months ago

↳ replying to Stefania

I agree, option D makes sense. Start simple!

Scaled Agile SP-SAFe-Practitioner Exam - Topic 1 Question 48 Discussion