scrum makes one promise only: It will help you fail in thirty days or less. That’s it. Organizational dysfunction will begin to surface as the work plays out. Healing from that dysfunction is up to you.

the people writing the software are, unsurprisingly, those who know best how to write the software.

Successful product development comes from happy, impassioned individuals and highly motivated, energized teams.

Empathy and compassion as agents of change need an advocate too.

One of the kindest services a scrum master can do for his or her team and for the organization as a whole is to create transparency—to radiate information. Transparency allows us to see flaws, and when we see the flaws we can make the choice to do something about them. We can stop being victims of process and start being warriors of change.

Scrum is a framework for organizational change and personal freedom. It is not a methodology, it is not a process, and it is much more than a tool.

The workflow board, when truly understood, becomes the spiritual home of the team, its church if you like. Team members gather around the board to argue, discuss and innovate, to align themselves with each other, to course-correct, to learn, to celebrate.

Change is so vital to the technology industry that it cannot possibly be represented by process alone.

We keep wanting to pretend what we do is an engineering discipline, but unfortunately, it’s a craft where the skill of the craftsperson dictates success.