What Development Team structure is best suited to produce integrated increments?

Question

Options

• AEvery Development Team has the abilities to develop functionality from beginning to end
• BEach Development Team specializes in one technical layer of the system (e.g. GUI, database,

• A
  93% (26)
• B
  7% (2)

Explanation

Option A is correct because a cross-functional Development Team - one where members collectively possess all skills needed to take a feature from concept to "Done" - can build and integrate a complete, shippable increment every Sprint without depending on other teams or hand-offs. When each team owns the full vertical slice of work (UI, backend, database, testing), integration happens continuously within the team rather than as a painful end-of-Sprint synchronization step.

Option B is wrong because layer-specialized teams (GUI team, database team, etc.) create horizontal dependencies: a feature needs all teams to contribute before anything is integrated, which delays integration, introduces merge conflicts, and makes a single integrated increment nearly impossible to produce each Sprint.

Memory tip: Think of option A as a "full-stack team" - like a food truck that can take an order, cook it, and serve it all by itself, versus a kitchen split into separate stations that must coordinate before a single dish leaves.

No community discussion yet for this question.