Cross-Functional, Self-Managing Team Collaboration and the Accountabilities of Developers
What this domain tests
Questions here probe the boundaries of self-management, who is accountable for what, and what "cross-functional" actually means on a software team.
Accountabilities of the Developers
The Developers are accountable for (1) creating the Sprint Backlog, (2) instilling quality by adhering to the Definition of Done, (3) adapting their plan each day toward the Sprint Goal, and (4) holding each other accountable as professionals. Self-managing means they decide who does what, how, and when - no one outside the team assigns tasks or dictates technical approach.
Cross-functional means the team collectively has every skill needed to create the Increment. It does not mean every person can do every job; it means the team does not have to hand work to an outside group to finish it. A team that must queue for a separate database or security specialist every Sprint is not yet cross-functional.
Collaboration mechanics
- The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog - not a status report to a manager.
- Sprint Planning is collaborative: the Product Owner brings a Product Goal and ordering, and the Developers do the selection and decomposition.
- Refinement is continuous conversation, not a scheduled hand-off of specifications.
Worked example
A delivery manager asks the Scrum Master to assign tasks each morning so everyone stays fully utilized. The reasoning: assignment destroys the team's ability to self-organize around the Sprint Goal and creates a bottleneck at the manager. The Scrum Master coaches the manager on why the team pulls work, and treats the manager's expectation as an organizational impediment to remove - the Scrum Master does not become the task assigner to keep the peace.
Traps that cost marks
Reading self-managing as "no rules" (the framework rules still apply); casting the Scrum Master as taskmaster or proxy Product Owner; letting the Product Owner direct the Daily Scrum; and treating cross-functional as "everyone is a full-stack generalist".