My Scrum Master Backlog
As an external consultant, I've had to roll onto projects at several clients, across a handful of industries and in several countries. I needed to orient myself and begin finding solutions to the areas which could be improved as soon as possible.
When the contract is to be a Scrum Master or Agile Coach, I look for telltale signs of the most fundamental concepts/practices I expect from a Scrum team.
These include, but are not limited to, what you'd typically expect:
- Definition of Done
- Definition of Ready
- Product Backlog
- List over blockers
- Team Working Agreement
- Explicit role expectations
These are examples of items on my Scrum Master Backlog.
The list is not a sequential, step-by-step list that I have to follow, but it's more like a catalog of "Greatest Hits" containing what's worked for me before and from which I can use as inspiration.
Scrum Master Backlog?
The Scrum Master Backlog is a term I started using after having to explain to the teams/stakeholders I work with, my somewhat structured plan for team development. Currently, I define the Scrum Master Backlog as:
A series of building blocks, which Scrum teams need to become proficient in, before they can achieve success