Answering: “Which approach is best for Scrum Teams in order to produce valuable Increments?” (PSM I)

The best approach is for each Scrum Team to build functionality end to end, from beginning to finish. Splitting teams by component or layer creates hand-offs and delays a usable Increment.

Exam Question

Which approach is best for Scrum Teams in order to produce valuable Increments? (choose the best answer)

• A. Each Scrum Team is accountable for developing functionality from beginning to end.
• B. Each Developer works on the component where they feel they can contribute.
• C. Each Scrum Member works only as an independent layer of the system.
• D. Each Scrum Team works on an independent set of components.

Correct Answer

A. Each Scrum Team is accountable for developing functionality from beginning to end.

Why This Is the Correct Answer

The Scrum Guide says “Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint.” A team that can build a feature across every layer can finish a usable Increment without waiting on anyone. It also says “The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.” Component or layer teams only produce parts. Those parts must be integrated by someone else before any value reaches users, which adds dependencies, delays feedback and hides risk until late.

Why the Other Options Are Wrong

B. Each Developer works on the component where they feel they can contribute. This focuses on individual comfort and component ownership. It does not ensure that a complete, valuable feature gets done.

C. Each Scrum Member works only as an independent layer of the system. Working in isolated layers creates silos and hand-offs. No one owns the working feature.

D. Each Scrum Team works on an independent set of components. Component teams cannot deliver value alone. Every feature then depends on coordination across teams.

Exam Tip

Feature teams beat component teams on Scrum.org exams. If an option splits work by layer or component, treat it as a distractor.

Key Takeaways

• Cross-functional teams deliver working features end to end.
• Component and layer teams create dependencies and hand-offs.
• The whole Scrum Team is accountable for a valuable Increment.