Sprint Task Distribution

Let's go back a step. Who ought to be responsible for the way work is distributed?

This is from the Scrum Guide section describing the Sprint Backlog (emphasis by me)

Topic Three: How will the chosen work get done?

For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. This is often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value.

And this is from the Scrum Guide section that describes the Developers (again emphasis by me)

The specific skills needed by the Developers are often broad and will vary with the domain of work. However, the Developers are always accountable for:

• Creating a plan for the Sprint, the Sprint Backlog;

• Instilling quality by adhering to a Definition of Done;

• Adapting their plan each day toward the Sprint Goal; and,

• Holding each other accountable as professionals.

Given all of that, do you think that there is one person responsible or would it be something that they Developers decide as a self-organizing, self-managing team?

@Daniel Wilhite@ Ian Mitchell  

 Thanks for the responses. I understand those team dynamics and thanks for increasing my understanding. It therefore goes that the onus to distribute tasks is the sole responsibility of the developers and the Scrum Master has no need to understand how the team does the task distribution. Got it!