## Introduction

The number of myths around [Scrum](/blog/first-steps-to-learn-scrum/) is still growing. Let’s be honest, frameworks or methodologies that use  [Scrum](/blog/first-steps-to-learn-scrum/) terms incorrectly do not help.

Today I would like to list the most common  [Scrum](/blog/first-steps-to-learn-scrum/) myths that I’ve seen in my career. I know that these myths have been constantly repeated and passed from company to company. But as you know, this blog is about education, so I want to debunk these myths. 

## Myth 1 - Scrum is just about Scrum events and roles

Many organizations decide to implement  [Scrum](/blog/first-steps-to-learn-scrum/), but they **end up only using roles, events & sometimes artifacts**. 

What is the result? They focus only on the way how to change processes or the way of working without really using [Scrum values](/blog/the-importance-of-scrum-values/) & **empirical approach principles**. This behavior is called: **"Mechanical Scrum"** and doesn’t work well in the long term. 

To be honest, [Scrum](/blog/first-steps-to-learn-scrum/) is much more about **changing the mindset and empowering teams** than anything else. I am not saying that events and roles don’t really matter, but they will not work without proper mindset and values. 
Implementing  [Scrum](/blog/first-steps-to-learn-scrum/) is the same like building the house, you need to have the proper **foundations**. 

## Myth 2 - Daily Scrum is a status report meeting

[Daily Scrum](/blog/scrum-events-3-daily-scrum/) is frequently misused by the [Scrum](/blog/first-steps-to-learn-scrum/) Teams as a **status report meeting** where individuals mention what they did, what they plan to do and what are their impediments.
You can ask - "Wait, but what is wrong with that? Aren’t these just the examples of the questions listed in the Scrum Guide version from 2017?"

The answer is - "Nope". There is one really important part missing here - the [Sprint Goal](/blog/sprint-goal-why-do-we-need-it/). The [Sprint Goal](/blog/sprint-goal-why-do-we-need-it/) is frequently treated by Scrum Teams as an unwanted element.They either don’t have one or they have multiple, so they don’t really use them.

What does [Scrum Guide 2020](https://scrumguides.org/scrum-guide.html#daily-scrum) say about [Daily Scrum](/blog/scrum-events-3-daily-scrum/)?

> The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.

[Daily Scrum](/blog/scrum-events-3-daily-scrum/) is not about **discussing the status** of individuals’ work. It should be time when Developers discuss **their progress toward the [Sprint Goal](/blog/sprint-goal-why-do-we-need-it/)** and **create their plan for the next day of work**.

Again, it’s about their plan **collectively** as a group of people who want to achieve the same goal. When we focus only on individuals, this element of **teamwork** can be easily lost and it prevents them from collaboration.

![Status report](img/status_report.jpg "Status report")

## Myth 3 - Agile means Scrum

It is a common mistake that people use terms **Agile & Scrum interchangeably**. There is no point to blame anyone, because it can be really confusing to remember all **Scrum** related terms plus using **"Agile"** term has been popular and fancy recently.

Let me make this one straight:

* Term **"Agile"** has been used in [“Manifesto for Agile Software Development”](https://agilemanifesto.org/) created in 2001. It reflects the **set of values & principles** that people who wrote manifesto wanted to promote in software development. Nowadays Agile is way above software development.  It remains a **philosophy** that can be used in many fields & industries. 
* **[Scrum](/blog/first-steps-to-learn-scrum/) is a framework** dedicated for generating value in a **complex** environment. Term [Scrum](/blog/first-steps-to-learn-scrum/) was used first time in 1986 and popularized in the early 1990s by Ken Schwaber and Jeff Sutherland.

**These terms are not the same.**

[Scrum](/blog/first-steps-to-learn-scrum/) can be recognized as one of the **Agile practices**. I really like using the below visual representation of the [relationship between Agile & Scrum](/blog/relationship-between-scrum-and-agile/). I hope it will help you to understand the difference. 

![Agile mindset vs Agile practices](img/Agile.png "Agile mindset vs Agile practices")

Source: https://www.agilesherpas.com/agile-mindset-marketing-agility/

## Myth 4 - Sprint Review is just a demo

Another common myth is treating [Sprint Review](/blog//scrum-events-4-sprint-review/) as **just a demo** of the work that was accomplished during the [Sprint](/blog/scrum-events-1-the-sprint/). Of course we want to show what was done, but that’s not the only purpose of this event.

What can we read in the [Scrum Guide](https://scrumguides.org/scrum-guide.html#sprint-review) about it?

> The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed.
>
> During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and what has changed in their environment. Based on this information, attendees collaborate on what to do next.

[Sprint Review](/blog/scrum-events-4-sprint-review/) is another opportunity for **inspection**, but also a really important moment in the [Sprint](/blog/scrum-events-1-the-sprint/) when the **Scrum Team can collaborate with stakeholders** and get their **feedback**. We don’t want to just show whatever was done and move on to the next [Sprint](/blog/scrum-events-1-the-sprint/).

It should be a moment to **stop, reflect** on what was done. We want to **adjust the [Product Backlog](/blog/scrum-artifacts-1-product-backlog/)** based on stakeholders’ feedback and discuss the future direction. 

## Myth 5 - Scrum Master doesn’t do anything

This one is the most painful myth for me as a [Scrum Master](/blog/scrum-roles-3-scrum-master/), because I know how many things that [Scrum Master](/blog/scrum-roles-3-scrum-master/) does are **invisible** and do **not recognized** by people.

Of course there are people out there who don’t do their job well and maybe they really don’t do anything. But to be honest the [successful Scrum Master](/blog/secrets-of-the-successful-scrum-master/) **shouldn’t be really too shiny and loud**.

There are so many small steps that need to be done by SM everyday that simply **will not be visible** for people if they don’t know about them. I am talking about **asking the right questions**, **talking** to individuals, **coaching** Product Owner, **searching** for new techniques that can help the team, **analysing** behaviours, preparing for workshops and so on.

I hope I made it clear enough, [Scrum Master](/blog/scrum-roles-3-scrum-master/) is not just drinking coffee and chatting. Although a lot of coffee & talking to many people is part of that role. :D 

![Coffee](img/coffee.jpg "Coffeee")

## Summary

If you believed in any of the above myths, I hope this post helped you to learn something new today.

* [Scrum](/blog/first-steps-to-learn-scrum/) is a framework is not just about events & roles.
* [Daily Scrum](/blog/scrum-events-3-daily-scrum/) is not really a status report meeting.
* [Sprint Review](/blog/scrum-events-4-sprint-review/) doesn’t mean only demo.
* Agile doesn’t equal [Scrum]([Scrum](/blog/first-steps-to-learn-scrum/).
* [Scrum Master](/blog/scrum-roles-3-scrum-master/) does more than drinking coffee.

Do you know any other interesting Scrum myths? Feel free to share them here or in Let's Scrum it on social media.



Is Agile the same as Scrum? Have you ever thought that Daily Scrum is the status meeting and Sprint Review means demo? These are some of the Scrum myths I debunk in this article. Check it out!

5 Common Scrum Myths

## Introduction

[The Scrum Master](/scrum-roles-3-scrum-master/) role is not easy. It requires **patience** and **curiosity** to learn something new every single day. Being a successful Scrum Master doesn’t mean that you are perfect and don’t make any mistakes. Of course you will make them, but you are also able to learn from them. 

What I will describe today is a process and continuous journey that never ends. You cannot just **become a successful Scrum Master** and then stop doing anything. Be **open-minded** and try to avoid common mistakes that will not serve you. 

## Active Teacher of Scrum

Let’s start from the quote from [Scrum Guide](https://scrumguides.org/scrum-guide.html#scrum-master):

> The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization.

Does your team and organisation **know what [Scrum](/blog/first-steps-to-learn-scrum/)** is? Did they read the latest version of the [Scrum Guide](https://scrumguides.org/scrum-guide.html)? 

Successful Scrum Master should be a **teacher** who is able to explain [Scrum](/blog/first-steps-to-learn-scrum/) framework in an **interesting** and **engaging** way. You want to teach [Scrum](/blog/first-steps-to-learn-scrum/) continuously on a daily basis. You really want to make sure that your team and organisation **understand [Scrum](/blog/first-steps-to-learn-scrum/) framework** and they are able to use principles and [Scrum values](/blog/the-importance-of-scrum-values/) in their work. 

### Exercise - Scrum teaching

* Draw the empty version of the **Scrum diagram**. You can use the classic [Scrum.org](https://scrumorg-website-prod.s3.amazonaws.com/drupal/2021-01/Scrumorg-Scrum-Framework-tabloid.pdf) diagram or draw your own version. 

![Scrum-diagram](img/scrum_diagram.png)

* Write all the [Scrum](/blog/first-steps-to-learn-scrum/)**roles, events & artifacts** on sticky notes. 

* Ask the team members to place the **sticky notes** on a diagram and discuss the **most important facts** about the element they put on the board. Allow other attendees for additional insights and thoughts. 

- Don’t correct the **wrong answers straightaway**. Allow the team to help out and correct misunderstandings. Let them self-organize and collaborate as a team. 

*Repeat this exercise **every few months** to build the shared understanding of the [Scrum](/blog/first-steps-to-learn-scrum/) framework and to give the opportunity for clarification. 

## Servant leader not a Scrum Lord

Following the [Scrum Guide](https://scrumguides.org/scrum-guide.html#scrum-master):

>Scrum Masters are true leaders who serve the Scrum Team and the larger organization

Successful Scrum Master should **give the power back to [Developers](/blog/scrum-roles-1-development-team/)** and **trust** that they know how to achieve the [Sprint Goal](/blog/sprint-goal-why-do-we-need-it/). 

One of the really toxic Scrum Master’s antipatterns is becoming a **Scrum Lord** with a **command and control** mentality who assigns tasks and sets deadlines. You don’t want to do that! 

[Developers](/blog/scrum-roles-1-development-team/) should be able to **autonomously** decide how they will work and what serves them well. Even if you don’t agree with their choice, give them the space to experience what they selected. They can use **empiricism** to inspect and adapt if whatever they implemented will not serve them. 

Becoming a successful Scrum Master requires a lot of **self-awareness**. Whenever you try to help your team, ask yourself:

> Am I serving someone else’s needs right now or my own agenda?’

You can use this question as the beginning of **self-retrospection** to analyse what you **can do better to serve others**. 

You can apply the same behaviour when it comes to interactions with [Product Owner](/blog/scrum-roles-2-product-owner/) or stakeholders. Before advising them what they should or shouldn’t do, **listen carefully** and try to understand **what they need**. The best way to serve other people is by addressing their needs and pain points. 

![Leader](img/lead.jpg)

## Quiet Listener and Observer not a Superhero

Are you addicted to the **adrenaline rush** and the **attention** that comes whenever you **solve the problem** for your team? Do you like to **propose solutions** to fix the problems within your Scrum Team? 

If the answer is yes, I must disappoint you. That’s not what a successful Scrum Master does.  When you try to solve problems in your team by yourself, you focus on your personal need to become a **Superhero**, not on **serving the Scrum Team**. 

To be successful in the Scrum Master role you need to **calm down your ego** and be a **quiet listener** who observes what others need.

Does it mean no action? Of course not! You still want to cause the removal of the impediments and facilitate discussions, but it requires **listening** and **observing**. Sometimes it’s better to be quiet to allow people in the room to **express their thoughts and needs.** 

![Silence](img/quiet.jpg)

### Exercise - The Power of Silence 

Whenever you notice that you **talk too much in meetings** e.g. you ask a question and answer it straight away, because people don’t talk, pause for a moment. 

Instead of answering the question by yourself, allow the **power of silence** to do its magic. **Wait for a minute** or even longer if needed. I guarantee you, someone **will finally speak up**, because they will start feeling uncomfortable with silence. 

**Listening and observing** is a powerful mix of skills that will allow you to become a successful Scrum Master. People don’t speak only by words. They show a lot by their **facial expression, tone of the voice or even body posture**. 
Listen & observe others to understand what they need. 

## Facilitator not Scrum Secretary

In many Scrum Teams, Scrum Master acts like a **[Scrum](/blog/first-steps-to-learn-scrum/) Secretary** by updating the statuses, taking notes or even bringing the team coffee. There is nothing wrong in bringing coffee to the team once in a while, but don’t forget what Scrum Master role is about. 

Successful Scrum Master should use **focus** one of the [Scrum Values](/blog/the-importance-of-scrum-values/) to invest time in the most important activities. One of them is not making or bringing coffee, but **facilitating discussions and stakeholders collaboration**. 

As it it mentioned in the [Scrum Guide](https://scrumguides.org/scrum-guide.html#scrum-master) Scrum Master should help the team to focus on:

> creating high-value Increments that meet the Definition of Done.

It requires **asking the right questions** and **challenging the team** whenever it’s needed. Scrum Master needs to keep **coaching the Scrum Team** in self-management and cross-functionality by facilitating discussions and promoting empiricism. 

## Summary

What are the secrets of a successful Scrum Master?

* **Actively teaching** the Scrum Team and organisation how to understand Scrum in theory and in practice. 
* **Serving** instead of a command and control mentality. 
* **Listening and observing** behaviours to understand how to serve and help others instead of being a Superhero.
* **Facilitating and coaching**, not working as a Scrum Secretary. 
What do you think about these secrets? Do you agree with my perspective? If not, what would you change or add?
------------------------------------
#### Sources:
1) Schwaber Ken; Sutherland Jeff. Scrum Guide, https://scrumguides.org/scrum-guide.html. November 2020.
2) Ripley Ryan; Miller Todd. Fixing Your Scrum. Pragmatic Bookshelf. Kindle Edition. January 2020. 

What does it mean to be a successful Scrum Master? What are the behaviours that can help you or stop you from serving others?

Secrets of Successful Scrum Master

## Introduction

In my last 2 posts from Scrum Roles series I explained who is the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) and the [Product Owner](https://letsscrumit.com/scrum-roles-2-product-owner/).

Today I would like to tell you more about the role of Scrum Master that is close to my heart, because I act as the Scrum Master in the Scrum Team. 

![Scrum-Master](img/scrummaster.png)

## Who is the Scrum Master?

Before we will start analyzing deeply the role, let’s check what Scrum Guide says about it:

> The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.

The most important responsibility of the Scrum Master role is to help everyone in understanding and using the Scrum framework. This will maximize the value created by the Scrum Team and will help them to build high-performance culture. 

It can sound simple, but there are a lot of skills and actions required from the Scrum Master in order to achieve the above. 

## Scrum Master - servant leader

One of the important things to remember is that: > The Scrum Master is a servant-leader for the Scrum Team. 

It is definitely not the traditional project manager, but the leader who serves the Team and helps them to understand what Scrum is and how they can use it on a daily basis. 
Scrum Master should serve the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/), [Product Owner](https://letsscrumit.com/scrum-roles-2-product-owner/) and the Organization.  

As a servant leader Scrum Master is responsible for: 
* Removing all impediments during development process 

* Helping to create collaborative and safe culture within the Scrum Team and organization - Finding and proposing new solutions that will help in more efficient development of the product  

* Understanding Scrum Team and organization needs and how they can be fulfilled using an agile approach.

![Servant-Leader](img/servant_leader.jpg)

## Scrum Master - teacher & coach

When I was a young girl, I wanted to become a teacher. What is more, I have even a degree in Early Childhood Education, because teaching others and helping them to grow was always my passion.  After a lot of adventures and changes in my life I become a Scrum Master and I believe that my teaching skills are really useful in this role. 

Scrum Master needs to use coaching skills and teach all below on a daily basis. 

#### Product Owner

*  Clear expression of the business goals, scope and the purpose of the product

* Product Backlog management by finding more effective ways and techniques. This includes making sure that Product Backlog items are clear and understandable for everyone. It should be explained and arranged the way that will maximize the value of the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) work. 

* Understand and practice agility and empirical approach in all Scrum activities.

#### Development Team:
* Self-organization and cross- functionality that are crucial part of their growth

* Understand the purpose of the Scrum and practicing it in an agile way on a daily basis

* Create high-value products 

* Resolve conflicts and discuss issues when they appear.

#### The Organization:

* How Scrum can be adopted and what is required from the Organization

* The value of the Scrum in organization and what does it mean to use empirical process in development of the product

* Plan Scrum implementations, cooperate with other Scrum Masters to increase effectiveness in Scrum adoption in organization

* How Organization should interact with the Scrum Team and what will increase the productivity and what won’t.

![Teacher](img/teacher.jpg) 

## Scrum Master - Facilitator

Scrum framework consists of events that increase communication and effectiveness within the team like : [Sprint](https://letsscrumit.com/scrum-events-1-the-sprint/), [Daily Scrum](https://letsscrumit.com/scrum-events-3-daily-scrum/), [Sprint Planning](https://letsscrumit.com/scrum-events-2-sprint-planning/), [Sprint Review](https://letsscrumit.com/scrum-events-4-sprint-review/) and [Sprint Retrospective](https://letsscrumit.com/scrum-events-5-sprint-retrospective/).

Scrum Master needs to facilitate some of these events if it is requested or needed. He or she also needs to make sure that events are organized and the team doesn’t exceed the maximum time dedicated for each event. 

Scrum Master should listen to the team’s discussion and issues they are struggling with and ask the right questions in the right moment.  I would say that one of the most important, but also difficult skills for the Scrum Master is taking the step back and creating space for the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) to express their ideas and solutions. 

A lot of Scrum Masters who transformed from the traditional project management approach would like to propose the solution right away instead of giving the freedom to the [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) to find it by themselves. 

The only way to help the team to be self-organized is to trust them and allow them to make their own decisions and mistakes. This empirical process is the best way to learn and grow. 

![Facilitator](img/facilitator.jpg)

## Summary

* Scrum Master is the role in Scrum Team who **promotes Scrum** and **helps** everyone to **understand** and **practice** it on a daily basis.

* He or she should be the **servant - leader** who supports [Product Owner](https://letsscrumit.com/scrum-roles-2-product-owner/), [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) and the Organization in their Scrum journey. 

* Scrum Master is responsible for **helping [Product Owner](https://letsscrumit.com/scrum-roles-2-product-owner/) in Product Backlog management** and making sure that everyone in the Scrum Team understands it.

* The [Development Team](https://letsscrumit.com/scrum-roles-1-development-team/) should be **coached** by the Scrum Master how to become a **self-organized and cross-functional team** and deliver the high value products. Scrum Master needs to support them and promote an agile and collaborative approach. 

* Scrum Master has multiple functions such as: **servant-leader, teacher, coach, facilitator** and more depending on what is needed. She or he needs to be the person who adapts to change quickly and helps everyone else to do it. 

Would you like to know who is the Scrum Master? What is her or his role in the Scrum Team?

3 posts tagged with #scrum master