Discussion about this post

User's avatar
Gabor Bittera's avatar

This is why it is a set of accountabilities rather than a role. This way we can dip in and out of the accountabilities. Anybody that is causing the removal of impediments is exercising one of the scrum master accountabilities. Anybody that adapts the sprint backlog to align with the sprint goal has been exercising the Developer accountability. All members of a Scrum Team are equality accountable for creating a potentially shippable increment of value.

Expand full comment
William Meller's avatar

Great reading! What often gets lost in conversations about Scrum roles is that high-performing teams don’t obsess over boundaries, they operate through trust, flow, and mutual challenge.

One thing I’d add: role "fluidity" doesn’t mean role ambiguity.

In great teams, responsibilities are clear, but no one hides behind them.

Expand full comment

No posts