Self-organisation is not a motivational poster and it is not anarchy. The team decides how to accomplish the work inside the Sprint. Your job is to build that muscle — which means resisting the urge to be the cleverest person with the plan.
What self-organisation actually means
In Scrum, the Developers own the Sprint Backlog: they choose how to turn selected Product Backlog items into an Increment. Nobody — not you, not the Product Owner, not a neighbouring architect — assigns them tasks. If you are breaking stories into tasks and handing them out before Planning ends, you are running a work-breakdown session with extra sticky notes.
Self-organisation needs constraints or it dissolves. The constraints are the Sprint Goal, the Definition of Done, the timebox, and the skills in the room. Coaching is tightening those constraints until they are honest, then getting out of the way. A team with a mushy Done and a goal that is really five goals will 'self-organise' into chaos and then ask you to manage them.
Cross-functionality is part of the same idea. If every item waits for the one person who 'owns' deployments, you do not have a self-organising team. You have a queue. Coach pairing, shared ownership, and a board that makes the specialist bottleneck embarrassing. Hiring may still be required. Pretending the board will fix a missing skill is optimism with columns.
Coach with questions. Assign only as a last resort.
Default to questions that return the problem to the team: What is the Sprint Goal asking of us today? Who is blocked by whom? What is the smallest experiment that would tell us if this approach works? People who are used to being managed will find this irritating. That irritation is often the work beginning.
Teach working agreements instead of refereeing every dispute. How do we handle review comments? When do we swarm versus split? What does 'ready' mean before Planning? Write the answers down. A team that can cite its own rules needs you less, which is the point. A Scrum Master who is indispensable in every disagreement has failed at succession.
Use the Retrospective as your main coaching arena, not a stream of mid-Sprint lectures. One improvement, owned, reviewed next time. If last Sprint's improvement vanished, that is the first agenda item. Coaching that never inspects its own advice is just a podcast the team did not subscribe to.
Accountability without a reporting line
The team is accountable to the Sprint Goal and to each other, not to your task list. Make progress visible: a board that is true, a burndown or burnup if it helps, a Daily Scrum that names risk to the goal. Visibility is a form of pressure that does not require you to perform disappointment.
When someone consistently avoids the hard work, do not become their secret manager. Start with a direct conversation, then the team, then the functional manager who actually owns performance. Scrum does not repeal employment law or the org chart. Pretending it does leaves you with a 'people problem' and no lever.
Psychological safety is not niceness. It is the ability to say 'this estimate is a lie' or 'I broke production' without being punished for the honesty. You model it by thanking the bearer of bad news and by stopping the senior visitor who uses the Review to score individuals. A team that feels unsafe will self-organise around hiding, which looks calm in your reports and expensive in your defect log.
Summary & next steps
Self-organisation means the Developers own how the Sprint Backlog gets to Done, inside clear constraints. Coach with questions, working agreements, and a Retrospective that inspects last Sprint's experiment. Hold accountability through visibility and the real org chart — not through assigned tickets.
Next: working with the Product Owner — backlog health as a partnership, without quietly doing their job for them.