Community Blog

A few years back I wrote 2 popular posts that talked about the best Scrum Masters I ever worked with. This time around I am going to share some stories about the best Product Owners I have encountered. This post is about Gerry, the proxy Product Owner who was successful!

A few years back I wrote 2 popular posts that talked about the best Scrum Masters I ever worked with. This time around I am going to share some stories about the best Product Owners I have encountered.

When people form a Scrum Team they have to figure out how to become a real team, rather than a collection of individuals. The Scrum Team Charter Canvas is a helpful tool to facilitate Scrum Team formation.

At a recent Scrum.org Professional Scrum Master II class, I asked the group to write down some learnings from the class that may help other Scrum Masters. One statement that came up has stuck in my mind ever since: “Don’t be a comfortable Scrum Master.” – Unknown Scrum.org Professional Scrum Master II Attendee.

TheScrumMaster.co.uk has created The Simple Guide To Scrum – 1 Pager. A condensed and visual representation of Scrum on 1 page.

Scrum is hard. To be more specific, learning Scrum is easy, using Scrum to develop complex products is hard.

Here are some simple examples of Product Goals, Sprint Goals and the relationship between them.

One of the most common questions I receive via the Contact Us page on TheScrumMaster.co.uk is – How can I get my first job as a Scrum Master?

At a recent class, a new Scrum Master asked me for a simple example of a Definition of Done. This post captures my answer to them and I hope it will help simplify this concept for you.

According to the Scrum Guide, the purpose of the Daily Scrum “is to inspect progress toward the Sprint Goal” and “adapt the Sprint Backlog as necessary” and “it is held at the same time and place every working day of the Sprint.” So what is the best time to hold the event each day?

At a recent course, one of my students asked me to share what Scrum “looked like” for me at TheScrumMaster.co.uk. This post is my response to that question. This describes my current process which has evolved via inspection and adaptation over 5 years.

At a recent course, one of my attendees talked about his use of a "to delete" status for items in his Product Backlog. Where items had been in his Product Backlog for more than 3 months he tagged them as "to delete".

Over the past 10 years I have worked with many organisations and helped them to use Scrum to create innovative and sometimes market leading Products. I have seen a lot of Scrum during this time, much of it done well, but some of it done badly.

The most common question I am asked at my courses is - what makes a good Scrum Master? I always answer this question with a story from my own experience working with Scrum Masters (good and bad) over the years.

The most common question I am asked at my courses is - what makes a good Scrum Master? I always answer this question with a story from my own experience working with Scrum Masters (good and bad) over the years.

Yes, of course it is! Scrum is a framework to help teams and organisations on their path to agility, but it is by no means the only way to be agile.