## 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

In my last 2 posts from Scrum Events series I described what is [Sprint](https://letsscrumit.com/scrum-events-1-the-sprint/) and [Sprint Planning](https://letsscrumit.com/scrum-events-2-sprint-planning/). Today I would like to focus on the event that can be easily forgotten or incorrectly transformed into a status meeting.
 
It’s time to talk about **Daily Scrum**.

![Daily-Scrum](img/Daily_scrum_1.png)

## Definition and length

Let’s start from definition of the Daily Scrum written in the **Scrum Guide** : 

> The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours.

First of all, the same as all events in Scrum, Daily Scrum is time-boxed. The maximum duration of the event is 15 minutes. The meeting should be organized daily at the same time and place to reduce complexity and to help the Development Team get into the habit of this daily activity.

## Inspection, not a status meeting

Continuing the analogy to running, Daily Scrum is like a line that is showing you the distance to the final destination. It is a great tool that helps you to inspect how far away you are. Sometimes it can motivate you to run faster or change your previous running technique. 

Daily Scrum is the event dedicated for inspection of how far the Development Team is from achieving the Sprint Goal. It is verification if they are on the right track or they need to somehow adjust the work. 

I would like to highlight that this event is for the Development Team to inspect their work, not for anyone else. They work together to accomplish what they planned as a self-organized team.  Scrum Master should make sure that event is happening and make sure that the event is not disrupted by anyone else.  It’s important to remember that Daily Scrum is not the status meeting for Product Owner or anyone else. 

![Inspection](img/inspect.jpg)

## Mustical 3 questions?

In the Scrum Guide there is an example of 3 questions that Development Team can answer during the Daily Scrum event: 

> - What did I do yesterday that helped the Development Team meet the Sprint Goal?
> - What will I do today to help the Development Team meet the Sprint Goal?
> - Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

Let’s remember that it is just the guidance. Some teams can prefer discussion - based meetings. The most important for them is to inspect progress towards the Sprint Goal and plan work for the next 24 hours. How will they do it? It’s up to them and that’s why it’s mentioned in the Scrum Guide that 3 questions are just “an example”. 

## Sprint Goal - again?
I’ve already mentioned and described why **Sprint Goal** is an important part of the Scrum in my post [Sprint Goal in Scrum - why do we need it?](https://letsscrumit.com/sprint-goal-why-do-we-need-it/)

The main purpose of the Daily Scrum event is to discuss progress towards the Sprint Goal. I will probably sound like a broken record, but I need to emphasise Sprint Goal’s value in the event.

It is important to mention it, because the Development Team has a tendency to forget about the Sprint Goal and discuss **all work** done a day before and planned for the next 24 hours, even if it wasn’t related to the goal. It can obviously impact the length of the meeting and result in forgetting **why** the team did the work that they did.  I believe that reminding yourself **why** you are doing your work and what is your goal helps you to stay motivated and focused. 

The simple but really useful for Development Team can be a visual representation of the Sprint Goal on their Scrum board or anything else that they are using for daily inspection. It will be a reminder for them to always refer to the progress towards the Sprint Goal.

![Sprint-Gaol](img/goal.jpg)

## Too long Daily Scrum

One of the most common issues related to the Daily Scrum is extending the 15 minutes length.  First of all, Scrum Master should teach the Development Team to keep the meeting within the time frame. It can be challenging, especially with a talkative team. :D 

There are simple tricks that can help in keeping the meeting within 15 minutes time-box: 
* **Focus on the Sprint Goal** - talk only about the work related to the Sprint Goal, not everything what you did or plan to do

* **No technical details** - do not explain technical details of your work or impediments

* **Detailed discussions saved for later** - if there is a need to discuss some issues or plans in detail, it should be done after Daily Scrum. It will definitely save time for people who will not be involved in the discussed subject.

* **Set up time per person** - depending on the size, the Development Team can set up the maximum time for talking per each person. They can even use a timer to count it.

* **Stand up during the meeting** - it is easier to keep the meeting short if people do not sit down. 

## Value of the Daily Scrum

As a Scrum Master, when I hear the question: "Can we skip the Daily Scrum? We have nothing to talk about.", I know that it is the time to step in and something is wrong.  It is important to teach the Development Team, what is the value of Daily Scrum and how it can be beneficial for them. 

* **Inspection and Adaptation** - it is time for the team to inspect their work and adapt if there is a need for change. They can track if they are progressing towards the Sprint Goal or not. As soon as the team forgets about the Sprint Goal, they lose track of why they are doing their work. That’s why they don’t know what to talk about during the meeting.

* **Communication** - quick discussion about progress of a team improves communication and helps the Development Team to be on the same page in regards to what needs to be done and what issues they are struggling with.  Eliminate other meetings - Team knows what is the plan for the next 24 hours and there is no need for other long, time-consuming meetings.

* **Quick fix** - Daily Scrum promotes removing impediments as soon as possible. Early recognition of issues can help in finding the quick solution. 

* **Team support** - Daily Scrum is a reminder for the Development Team that all individual’s actions impact the team, but the team can be supportive and helpful in resolving any issues. The most important is to collaboratively strive to achieve the Sprint Goal. 

![Values](img/team.jpg)

## Summary
The most important information about Daily Scrum to remember are:
* It is a 15 minutes time-boxed event that happens daily.

* It is an internal meeting for the Development Team.

* Daily Scrum is the inspection event, not a status meeting.

* During the meeting, the team should inspect the progress towards the Sprint Goal and adapt to the situation (change their actions) if needed.
Sprint Goal helps the team to realize why they are doing their work.

* The Development Team should keep the 15 minutes time frame. 

* The Scrum Master role is to make sure that the team has a meeting and they do not extend 15 minutes.

* Daily Scrum benefits are: better communication, no need for other meetings, quick fix of issues and support of the team.

I hope my explanation of the Daily Scrum helped you to understand the purpose and value of that event. Feel free to share your thoughts about it on LinkedIn or Twitter!

Are you wondering what is the purpose of the Daily Scrum? Jump in and learn why it is not a status meeting from my third post in the Scrum Events series.

2 posts tagged with #daily scrum