What is the best way to split up teams on a large project which is implemented using Scrum?

Question

Options

• AGroup by domain expertise.
• BGroup by features being developed,
• CGroup by specialty of the team members.

• A
  10% (5)
• B
  71% (34)
• C
  19% (9)

Explanation

Grouping by features (B) aligns with Scrum's core principle of cross-functional, self-organizing teams - each team owns a vertical slice of functionality end-to-end, minimizing dependencies and enabling independent delivery. Option A (domain expertise) creates horizontal silos where, say, all database experts work together but no single team can ship a complete feature without coordinating with others. Option C (specialty) is essentially the same anti-pattern as A - organizing around roles like "front-end team" or "QA team" contradicts Scrum's emphasis on teams that contain all the skills needed to deliver a done increment. Memory tip: Think of Scrum teams as mini-startups - each one should be able to build and ship something valuable on its own, which only works when they're organized around what they're building (features), not who is building it.

No community discussion yet for this question.