Last year, I ran a (non-representative) survey on how Scrum Masters are allocating their time when working with a single Scrum Team. Much to the surprise of many readers, the direct Scrum Master engagement with a single Scrum Team of average size and a typical 2-week Sprint turned out to be about 12 hours per week.

TL;DR: Scrum Master Duties, Serving a Single Team Scrum Master Duties: supposedly, a great Scrum Master serves only one Scrum Team—that’s at least a popular narrative in the Scrum community.

‘Autonomy without accountability equals anarchy’ summarizes an essential design element of any agile organization. Without these checks and balances in place any aspiration to transform an organization is likely to fail.

A meta-retrospective is an excellent exercise to foster collaboration within the extended team, create a shared understanding of the big picture, and immediately create valuable action-items.

Learn more on how to tackle impediments as a team by running experiments, iterating and visualizing on the solution.

This post covers four team building mental models — or concepts — that have proven useful in understanding the context of creating agile teams: from Taylorism to Tuckman to Lencioni to Dan Pink.

Popularized by Elon Musk, utilizing first principles thinking to solve problems in an innovative, creative, and less biased way has proven popular in the tech community.

The Scrum Guide Reordered is based on about 90 percent of the text of the 2017 Scrum Guide, extending its original structure by adding additional categories.

Why run a Liberating Structures immersive workshop? Since the beginning of 2019, the Hands-on Agile meetup in Berlin has been exploring how to apply Liberating Structures to Scrum.

I recently started aggregating my notes, links, and references related to agile leadership to understand better what it — in the context of an agile transition — may look like.

TL; DR: Ideas on How to Improve Your Product Backlog Management Techniques Scrum is a simple, yet sufficient framework to build emerging products, provided you identify in advance what is worth building.

If technical debt is the plague of our industry, why isn’t the Scrum Guide addressing the question of who is responsibly dealing with it?