I've learned and experienced that most symptoms can be traced back to not adhering to the Scrum Roles. Let's have a closer look at the Scrum Master role.

What are the most common mistakes with Scrum that lead to dysfunctional Scrum? This time we take the perspective of the Scrum Development Team.

I've learned and experienced that most symptoms can be traced back to not adhering to the Scrum Roles. Let's start with the Product Owner role.

Fighting organizational impediments as a Product Owner? Combine powers and utilize the Product Owner and Scrum Master symbiosis. And create more focus at the same time.

I will make a case why the Sprint Goal should take center stage in any Sprint. If it seems difficult, it is an opportunity to improve.

The role of Scrum Master is often completely new for many organizations, and often misunderstood. So what are the responsibilities of the Scrum Master? And what is a Scrum Master supposed to do the whole day?

Why is it that when the going gets tough, “agile” gets the blame? There is so much online bashing of [insert random agile framework or method] going on, that it made me wonder if there is a pattern behind it. I believe there is.

How effectively are you maximizing value when dependencies tell you what to do first? Dependencies impact the core of the role of Product Owner.

What do you need to get a job done? You need the right tools and the right skills (and you might need some form of process – more about that later). But the wrong tools in the right hands is a recipe for disaster.

Last year I reached a very important goal I had set for myself: I became a Professional Scrum Trainer (PST) on behalf of Scrum.org. But why was this so important to me, and how did I get on this path?

The latest release of the Scrum Guide is all about addressing common Scrum misunderstandings. In this blog post I will present the top 5 misconceptions that are set straight in this latest release of the Scrum Guide.