Community Blog

We talk about coaching a lot in the agile world. However, what we are actually expected to do is not usually about coaching.  We do other things. We teach.  We facilitate.  We advise. We solution.  We manage.  

The Scrum Guide talks about coaching as a part of the Scrum Master role.  First, let's define what coaching is.  You can find many definitions, and here is how I describe coaching.

Per a January 20th, 2017 article by Daniel Shapero, VP of Talent Solutions and Careers at LinkedIn, the role of Scrum Master is in high demand. It’s ranked number 10 on his list of most promising jobs of 2017.  

The Scrum Team consists of 3 distinct Scrum roles that promote Self-organization: the Scrum Master, the Product Owner, and the Development Team. The accountability of each role complements the accountability of the other roles.

Clients and training attendees ask me "Can you use Scrum for something else than software?”. What they usually mean is building some other products or organizing team’s work. Let’s explore a more exotic idea.

One of the arguments used against Scrum and a common misconception at the same time is the idea that quality is traded for speed in Scrum. As a PST with years of experience in Quality Assurance I decided to challenge this myth.

The Daily Scrum, or most of the time referred to as  the "stand up." Probably the most well-known event when we talk about Scrum.

Recently I published the whitepaper "The 8 Stances of a Scrum Master".

According to the Scrum Guide, the Scrum Master is responsible for ensuring Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules.

Today I changed my Twitter and LinkedIn profile. I removed Agile Coach and replaced it with Scrum Master. 100% Scrum Master.