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

Jump in here to explore eduScrum framework - innovative way of working with students. I explain in this post what is the foundation of the framework and how it relates to roles, events and artifacts.

What is eduScrum?

##Introduction

You will learn today about **[eduScrum](https://eduscrum.com.au/)** - a framework that I fell in love with and I would like to spread knowledge about it everywhere in the world. 

Initially I was planning to write just a post about [eduScrum](https://eduscrum.com.au/) basics, but then I realized that before explaining **WHAT** is [eduScrum](https://eduscrum.com.au/) I need to tell you more about **WHY**. 

Why do we need it in Education? Why could you even think about using that framework? Why do I like this framework so much?

## The origins of eduScrum

To fully understand [eduScrum](https://eduscrum.com.au/) you need to know its origins.  That’s how it is described by the founder of [eduScrum](https://eduscrum.com.au/) - **Willy Wijnands**:

> It starts with a bottle of beer and a barbeque in the summer (June) of 2011 with Mark Reijn. Mark just finished a Scrum course given by Jeff Sutherland at the company Schuberg Philis in Amsterdam, where Mark works as a software engineer. Mark was very enthusiastic about Scrum, inspired by Jeff and he explained Scrum to me on one single paper.  > >He was the sparkle who put me on fire. In August 2011 I started one class using Scrum to try-out if it works in the classroom. In the beginning I was surprised that it was working. So, I began to use Scrum in all my classes with success. And so the name eduScrum was born.

When I read this story I can feel a huge inspiration and I am grateful that Willy discovered what Scrum is and implemented it in the classroom. 

## Why did I fall in love with eduScrum?

I am sure that behind Willy's story there are problems that teachers experience in their life every day. He was talking with Mark , because he was looking for inspiration. He really wanted to help his students to collaborate better and to use their potential in the learning process.

I personally believe that the heart of [eduScrum](https://eduscrum.com.au/) is **care for students and discovering what can help them to thrive**. That’s my **WHY**, the reason why I like [eduScrum](https://eduscrum.com.au/) so much.  I am inspired by this framework, because the main mission in my life is to help people to discover their potential and thrive. 

If you ever plan to implement [eduScrum](https://eduscrum.com.au/) in your classroom or project, remember - the purpose is not to give you another technique. [eduScrum](https://eduscrum.com.au/) is not a silver bullet and it will work only if you will care about your students and give them the wings to fly.

![fly](img/fly.jpg)

## eduScrum & Scrum

As you could find out in Willy's story, he created [eduScrum](https://eduscrum.com.au/) after discovering what **Scrum** is. 

If you are reading this post and it’s the first time when you’ve heard term Scrum, feel free to check out my previous posts: 
* [First steps to learn Scrum](/blog/first-steps-to-learn-scrum/) 
* [Relationship between Scrum and Agile](/blog/relationship-between-scrum-and-agile/)

[eduScrum](https://eduscrum.com.au/) & Scrum have a lot in common, but I will explain it in the following posts.  Today I would like to fully focus on **WHY**.

## Why do we need eduScrum in Education, what are the benefits?

I’ve done some analysis below and explained **3 WHY’s** to show you the reason why we need change like [eduScrum](https://eduscrum.com.au/) in Education and what are the benefits.

### Education now vs 100 years ago - linear teaching transformation

Initially, when I started writing this part of the post I wanted to mention that education didn’t change too much over the last 100 years. I will not do that, because I would be lying. 

Let’s take a trip down the memory lane- **what changed over the last 100 years?**
* 100 years ago education was available to limited number of people. Currently that’s the case only in some underdeveloped countries. As women we are in much better position now, because in the past we wouldn't have access to education.
* Schools are not using corporal punishment anymore. It is not legal in most of the countries in the world while it was a common approach in the past. 
* Technology is much more advanced - schools use active boards, computers, tablets. 
* In the past the teacher "was always right" even if that wasn’t the truth. Nowadays, there is more space for mistakes and teachers can make them too, because they are human beings, not robots.

**What didn’t change?**

I found a great picture on https://educationrickshaw.com/ that explains it well. 

![Teaching vs learning](img/direction.png "Teaching vs learning")

I wish I could tell you: the left hand side represents education 100 years ago, while the right hand side represents education now.  Unfortunately that wouldn’t be true, because we still teach the way represented on the left hand side. Of course, there are some adjustments like rearranged desks, but one thing still didn’t change:

**The direction of the arrow - it points from the teacher to the student.**

T - represents **teacher**, S represents **student** and arrow shows the **direction of teaching**. As you can see in the picture on the left hand side, the arrow is going from the teacher to students.

**What does it mean in reality?**
* Teacher is the source of truth 
* The role of teacher is to create creative, enjoyable lessons and make sure that students will remember  what they are taught 
* Students job is to remember the lessons

There are few aspects in that approach that **don’t really work:** 
* Teachers can be great people but they they shouldn’t be the only source of truth & knowledge for students
* Responsibility for the learning process shouldn’t be only on teachers shoulders 
* In this approach student is passive and only "receive knowledge", while in reality that’s not the way how we learn

### 1. WHY: change of direction, students empowerment

Based on the analysis of the past and current approach, we can see that something doesn’t really work and that’s how we discover our first **WHY**:

**To change the direction of the arrow. Let's turn it all around and allow students to drive their own learning process.**

Following the [eduScrum guide](https://drive.google.com/file/d/1BX4IbmTgcbo0LlupOlHCDUlLpZ0YO0aD/view?usp=sharing):

> eduScrum is a co-creative process in which students are no longer held responsible, but feel responsible for their own work and learning process.

![student](img/student.jpg "student")

**The benefits of that approach:**
* Changing the responsibility for the learning process from teachers to students 
* Teacher’s role is to inspire, support & guide - Students are more motivated, because they have autonomy and they can make their own decisions. 
* It’s easier to recognize when individuals have troubles and more space to help them 
* Students can teach each other & spread their knowledge instead of being only receivers- double benefit, because they can also learn by teaching 
* Teacher can have more time for supporting and guiding students

### 2. WHY:  21st Century skills

In 2015, the World Economic Forum published a report titled ["New Vision for Education: unlocking the Potential of Technology"](http://www3.weforum.org/docs/WEFUSA_NewVisionforEducation_Report2015.pdf). 

The report describes 16 crucial skills for education in the  21st century: 

* Foundational Literacies 
* Competencies 
* Character Qualities

![21st century skills](img/21stcentury.PNG "21st century skills")

As they mention in the report:

> To thrive in a rapidly evolving, technology-mediated world, students must not only possess strong skills in areas such as language arts, mathematics and science, but they must also be adept at skills such as critical thinking, problem-solving, persistence, collaboration and curiosity. (...)  in today’s innovation-driven economy workers need a different mix of skills than in the past.

**Do we currently develop all those skills at school?**

I am afraid that in the traditional linear way of teaching, we focus mostly on Foundational Literacies, while Competencies & Character Qualities are left behind. 

That’s where we found our second **WHY:**

**To help students develop 21st century skills that are required in our rapidly-changing world.**

That's exactly the purpose of [eduScrum](https://www.eduscrum.nl/img/The_eduScrum_guide_English_2.pdf):

> In eduScrum learning is central: learning smarter, learning to collaborate better and getting to know yourself better. In addition, this way of working provides more responsibility, pleasure and energy, resulting in better results and shorter lead times.
>
> ![Agile learning compass](img/compass.jpeg "Agile learning compass")

Source: https://www.eduscrum.nl/resources

**The benefits:**
* We create better future & society members who will be able to adapt to changes. Students can learn how to collaborate. They will need that skill in their future work, relationship and family.  
* We shape human beings who are not only receivers, but they can think critically, have their own opinion and are able to decide what is the best solution. Their persistence, creativity & curiosity will help in solving problems in our society.  
* What is more, they can critically observe their own actions and improve themselves. 
* Communication skills will help students to express their needs, but also to be mindful about others, listen to them & develop empathy.

### 3. WHY: motivation & results

Some of you can think - "Wait a second, it sounds like a beautiful story, but we still need to prepare students to pass exams, we still need to help them to have the best results".
That’s the moment when part of myself is sad, because I know how much we are driven by results and I know that during that process of achieving more and more it is easy to forget about **people**. 

But, don’t worry! [eduScrum](https://www.eduscrum.nl/img/The_eduScrum_guide_English_2.pdf): has it all covered:

> eduScrum is a framework within which teachers and pupils tackle complex, challenging problems and pursue learning goals of the highest possible value in a productive and creative manner.

Teachers are frequently struggling with students’ lack of motivation.  That’s the reason for our third **WHY**:

**To motivate students intrinsically by giving them autonomy what leads to improving academic results.**

**The benefits:**
* Initially it will require more effort to change the approach, but once students discover their strengths, they will get motivated and their results will become better. 
* Students will not be learning only to get better results, but they will become more curious.  
* Teachers don't need to explain how students need to achieve learning objectives, they determine only why and what.  
* At some point, students will not be learning only based on Curriculum, but they will be discovering more out of curiosity. 

## What is your WHY?

I know that this post is long and I didn’t really explain exactly what [eduScrum](https://eduscrum.com.au/) is, but don’t worry, I will explain it in the following posts. I wanted to start by analysing our world’s needs in education first, so that you can use it later as a reference.

I could explain more and more reasons why I believe that we need a framework like [eduScrum](https://eduscrum.com.au/) in Education, but I will leave some space for your personal reflection. 

**Why do you think we need some change in Education? Have you ever experienced difficulties at school either as a teacher or as a student? Is there anything that you could make better in education if you could?**

Please let me know if you find this topic interesting and what parts you would like to explore more. If you would like to learn more about eduScrum, I invite you to my eduScrum Basic Training.

This post is dedicated to everyone who cares about Education and who would like to discover some innovative ideas on how to help students to grow.

eduScrum - why do we need it in Education?

## Introduction

Today I would like to write a little bit about a subject that we all know about, but it’s been always difficult to deal with - **failure**. It is part of your life, it’s part of my life and no matter how much we try, we are not able to prevent it. Actually, we can prevent it, by not doing anything, but… Wait, isn’t it a failure too?

In my last post I quoted **Brené Brown** and I would like to do it again, because I strongly believe in her words: > There is no innovation and creativity without failure. Period.

Failure will always be part of our lives, but we can experience it and learn from it or struggle with moving forward. **What do you choose?**

![Failure](img/failure_scrum_blog.png)

## Scrum & Failure

You could wonder - "Why is she talking about failure, if this blog is about Scrum, Agile etc?". The answer is simple - failure is an inevitable part of the Scrum framework and Agile way of working. 

As you may remember, Scrum is founded on empiricism and following the [Scrum Guide](https://scrumguides.org/scrum-guide.html):

> Empiricism asserts that knowledge comes from experience and making decisions based on what is observed.

If knowledge comes from experience, it means that we learn based on events that occur in our lives - either positive or negative like failure.  Following this conclusion, failure is an important part of the Scrum, because we can learn from it and adapt our behaviour. 

## Failure & Agile mindset 

Nowadays there are many ways of interpreting **Agile**, but I will keep repeating like a broken record that it is not a methodology, it is a **mindset**.  I wanted to highlight it, because to be able to deal with failure, we need to have the right mindset.  Being open for changes, even if they potentially can bring failure is important. 

With that mindset it is easier to find better solutions when you experience failure or any issues in your life. 

I keep learning every day to stay focused on the positive impact of every situation in my life, even if it’s not easy for me. That’s how you can not only **"do Agile"**, but **"be Agile"** in your daily life. 

![Mindset](img/mindset.jpg)

## Failure and environment

There is one crucial aspect in dealing with failure that can change everything - **environment**, conditions in which you operate. 

It is easy to say "I cannot understand how she/he didn’t deal with that failure and what they did with their lives. If I were she/he in this place, I would overcome it easily or solve it differently."

The thing is - **you are not in her/his place**, because you probably have a totally different environment that would help you to deal with failure. Not everyone is so lucky e.g. losing a job for someone who has a supporting partner, family will be a totally different experience than losing a job for someone who has depression and is fighting with their family everyday. 

One of the Agile principles in the [Agile Manifesto](https://agilemanifesto.org/) is saying:

> Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done

I would like to highlight two parts of this principle **"environment"** and **"support they need"**. To be able to learn from your failures require the right environment and support that you need. 

In the business context it is not as easy as it sounds, because in many organizations there is no space for any failure or mistake. 

What does it mean for people? They will not even try, they will not be creative, because they will be afraid of making mistakes and being punished for that.  That’s definitely an environment that we would like to avoid.  Employees are the most creative when they have space to try new things and they have support from the organization.
![Support](img/support.jpg)

## Failure and Perfectionism

I am one of the people who are struggling with **perfectionism** in their life. Sometimes it is a blessing for me, because I aim to do everything the best I can.  Unfortunately, it is also an issue, because I am struggling if I don’t achieve 100% and I don’t deliver something perfect. You can imagine what happens in my mind when I fail. 
For a long period of time in my life, I was blaming myself for every mistake, even small. I couldn’t stop thinking about it and it was impacting my next actions. 

I learned how to stop doing it through Ultimate Frisbee - a sport that I play. I noticed that every time when I was blaming myself for mistakes on the field, I was making even more mistakes and it was stopping me from enjoying the game.  At some point I decided to focus only on my next move, instead of thinking about the past mistakes. 

![Perfectionism](img/perfectionism.jpg)

It is easier in sports than in daily life, but I try to apply it to my work & other personal activities as well. I am sure that I am not the only person who is struggling with perfectionism, because I’ve met many people like me in my career. 

If you are one of these people and you are struggling with thinking about your mistakes, failures, **don’t be harsh on yourself**. I know how difficult it can be, but I also know how important it is for mental health to focus on your current or next steps instead of blaming yourself for mistakes.  Whatever you think, ask yourself if you would say the same words to your close friend if they would make the same mistake. Most of the time, the answer would be "no", so analyse if you want to talk to yourself that way. 

Understanding that nothing is perfect is an important part of the Agile way of working. It allows people to fail and try new solutions or discover why the action didn’t bring any value. 

## Summary

To summarize, failure is an important part of Agile/Scrum, but what is more important - it is inevitable part of our lives!  Think about it as an experience that you can learn from. Don’t forget about support for people around you who are struggling with failure in their lives. **Your few empowering words can change someone's day and help them to move forward**. 

Last, but not least, **don’t be harsh on yourself** when you experience failure in your life. Treat yourself the same way as you would treat your friend. 

Let me know what you think about failure. Do you agree with my opinion that it is part of Agile & Scrum? Feel free to comment here or start discussion on LinkedIn/Instagram.

Have you ever thought about failure in regards to Scrum, Agile? How do you deal with failure? In this post you will have a look at a failure from a different angle and discover its value.

Scrum, Agile and failure 

## Introduction

It’s been a while since I wrote the last post here. I’ve started thinking about it - how did it happen that I stopped writing?  There are many reasons, but today I would like to focus on one that was the most important: **change**. 

People frequently underestimate how even small changes can affect their lives. In my case I changed a job, so it was a significant disruption of my life. I had to get out of my comfort zone and face the new environment, people & standards again. 

I have a love-hate relationship with change. I am always super excited before it comes. When it really happens, I get stressed and overwhelmed. Then I experience new things, learn and at the end I am really happy that I welcomed change in my life. 

I strongly believe that one of the **Agile values**: 

>Responding to change over following a plan

can be applied not only in a business, but also in a personal life context.  Nowadays, no matter how much we try, we will not be able to avoid changes. They will be happening even if we will have wonderful fully-detailed plans. The question is not if they happen, but how we will respond when they do. 

![Change](img/change_2.png)

## How to adapt to change? 

There are few things that I believe can help when we try to adapt to change in both scenarios - business & personal life.

## 1. Don’t be too hard on yourself - failure is inevitable 

Being hard on myself - that’s a mistake that I still make, but I try to minimize it every time when change comes.  No matter how much we try, we will fail and we will be making mistakes. Blaming ourselves or anyone else doesn’t bring any value but makes the process even more difficult. 

Accepting that issues will appear can help to change the focus from mistakes to small achievements during the process of change.  That on the other hand will boost up your energy level and help you to deal with difficult parts.

Whenever you try to adapt to change and make mistake, keep the words of Brene Brown in your mind:

>There is no innovation and creativity without failure. Period.

## 2. Start from small steps & be consistent

I started this blog by developing a simple habit - writing a minimum 15 minutes daily. That was back when I was working from home every day and I was always writing at the same time.  When changes came into my life (e.g. working partially in the office) I had to start development of my habits again. I must admit - it is hard!  I know that what really helps me adapt to change are small steps. These 15 minutes of writing were no longer easy for me due to different circumstances in my life. I had to approve it and figure out my starting point - the smallest steps possible like writing even a few words or thinking about what I would like to write about. 

In the business it’s exactly the same. When change comes, not everything will be working as we planned, but we need to slowly adapt - step by step.  There is one sentence that I saw so many times in Scrum/Agile materials and I believe it is really important: 

> consistency reduces complexity

Even the smallest steps can help to develop habits if we will be taking them consistently at the same time and place. 

![Steps](img/steps.jpg)

## 3. Feel the fear & take action anyway

It is OK to be afraid of change and it’s OK when you feel overwhelmed. It doesn’t matter if we are talking about your personal life here or about change in your company. We are humans and feeling fear is our natural and primitive human emotion. It is a survival mechanism that alerts us to the present of danger. 

When we experience change, it is quite possible that we will feel fear. It is normal, but it is important to not be frozen in fear.  You need to take action anyway! That is the only way to adapt to change - by taking action. Fear will be still present in your life, so get used to it and learn how to live with it and do not let it stop you from action.

![Fear](img/fear.jpg)

## Summary

I know that there are many more ideas that can help you adapt to change, but I believe that these 3 points are the most important.  

Remember: 
* You will fail, but that’s part of the process. Don’t be too hard on yourself. 

* Adapt to change by doing small steps and be consistent. 

* Get used to feeling fear and take action anyway.
Let me know what you find the most helpful in adapting to change. Feel free to add comments here or start a discussion on LinkedIn/ Twitter. 

People frequently underestimate how even small changes can affect their lives. Changes are unavoidable, so that we need to be ready for them. In this post you can find few things that can help you in the adaptation process.

How to adapt to change?

## Introduction

Today I would like to share with you my personal experience that changed my life - journey from Education to Scrum and back.  All my previous posts were mostly informative, but this time will be different - you will find out what I dream about and what is the role of Education and Scrum in my life.

## How did I start my Education journey?

Long time ago, when I was in junior high school (it is called Gymnasium in Poland) I had a **dream to become a teacher**. I was inspired by my Polish teacher (from secondary school) who was a wonderful woman and who taught me how to believe in myself. I will never forget how much she helped me **to become a person who I am now**. 

To achieve my dreams, I started working with children voluntarily by organizing Christian and music classes next to my church.  I was religious back then, but that’s not a point.  The most important thing for me was time when I could organize activities for children and **enjoy it**! I was playing with them, organizing events for all church celebrations, teaching at summer camps etc. 

I could see how **children were growing**! And I don’t mean the religious part, but their confidence. I remember many of them who were shy, didn’t believe in themselves, but after a few weeks of activities organized by me and my friends they started changing. They were more confident, full of ideas and they started collaborate with other children.

**Seeing how people grow and use their potential is an amazing experience!**

![growing](img/children.jpg)

## Working at school

After high school I decided to study **Early Childhood Education**. It was such an interesting time for me. I’ve met so many inspiring people and learned a lot about children - they mind, behaviour, teaching ways and more.

In my last years of studying I was working as an intern in private kindergarten and private school. It was a great experience, because both places were focused on **children's creativity** and teachers were full of amazing ideas. 

Then, I had my last internship - in Polish public school. I must admit that the difference between private and public school was enormous.  First of all, the number of students in  a class was 3 x bigger than in private school. I know that you can say, it is a normal thing, but I was wondering how easy it will be to **not notice someone's needs** if class is so huge.

Another thing that I noticed, was killing students’ creativity. They had to follow rules, write or read something in their coursebooks, but there was **no space at all for their own thinking process**. 

![school](img/school.jpg)

I believe that **the role of a teacher is important** and **it can change students lives for better or worse**.  As a teacher I wanted to **help children to grow**, to **discover their potential**, not to kill it...

Maybe I was a coward, but I was devastated by the education system and how it was used in public schools and I decided that I don’t want to be part of a system that doesn’t focus on students' needs. 

When I was organizing after school activities for children I experienced how **creative** they are. It was amazing to observe how many **ideas** they can have and how quickly they can find solutions if you **give them freedom**. Unfortunately I didn't see too much space for that in school.  I was also afraid that I could have a negative impact on an individual's life if I simply do not notice them in the class of more than 30 students.

I know, if you are a teacher you probably think that these are things that you can work around and they shouldn't stop me from continuing my career as a teacher.  Maybe you are right, but that was the **first lesson about myself** - I found out what **my values** are and how I want or don't want to **impact someone's life**.

## New direction - Economics and Finances

After graduating I moved in a totally different direction - I started studying **Managerial Economics** and working in a financial company as a fund accountant.  It was still time when **I was looking for the best path for myself**.

My fund accounting career took almost 4 years and it was time when I learned a lot about myself. I discovered how **I love problem solving and collaboration with people**.  In my last position - supervisor, I had a chance to be a leader and do what I liked the most - help people to discover their potential and to grow.  After solving a lot of issues, creating some structures in the team I started feeling that I need more challenges and I need to be passionate about my job.

![direction](img/direction_.jpg)

## Discovering Scrum

That was the moment when I discovered **[Scrum](/blog/first-steps-to-learn-scrum/)**. My boyfriend, who is a developer, was using it daily in his workplace and told me about the framework.  As soon as he explained to me some rules and values, I started reading about it and became more and more curious.

**Collaboration** with the team and stakeholders, **adapting to changes** and discussing **how the work can be improved** were exactly what I would imagine in every workplace.  I was trying to use **[Scrum and Agile values](https://letsscrumit.com/the-importance-of-scrum-values/)** in my fund accounting job, but I knew it wasn’t possible to implement the whole  framework there, because we didn’t work on projects. 

![Scrum](img/scrum.jpg)

I knew from my boyfriend that **[Scrum](/blog/first-steps-to-learn-scrum/)** was the most popular in IT companies, so I started looking for a new job in an IT company. I wanted to learn as much as possible about project work and I started dreaming about **becoming a [Scrum Master](https://letsscrumit.com/scrum-roles-3-scrum-master/) in the future**.

That was the moment when I started working as a Project Management Officer. It was such a great experience, because I could see how project work looks like. I’ve met many wonderful people and I learned a lot from them.  It wasn't a long period, because I got an opportunity to study **IT Project Management in Australia**. 

## First steps in Australia

Even if I felt wonderful in Polish IT company and I didn’t really want to leave, I knew that the **opportunity to study and live abroad may not happen again**.  That’s why I decided to move to **Australia** with my boyfriend and discover what is waiting for me on the other side of the globe. 

As I already mentioned I started from studying **IT Project Management** in the afternoon and during the day doing everything that was possible without a full time working visa (I had student visa) - cleaning, working in a restaurant and cafe.  It helped me to appreciate all professions and understand how hard it can be to work in hospitality.  In the meantime my boyfriend got a job in an IT company and we both received full time working visas.

![Australia](img/australia_map.jpg)

## Project Managment & Scrum

Once I finished my course I started looking for an IT job in **Project Management**.  I found a role in the IT consulting company and I started in the IT Infrastructure project in Project Management team. 

In the meantime I discovered that there is a Information Solution (software development team) in the company and they were using **"Scrumish"** in their projects.  As soon as my first project was finished I got an opportunity to join that team and help them in one of their projects. 

It was an amazing moment, because **I could finally use Scrum on a daily basis**. What is more I could finally reuse my **teaching and facilitating skills**. 

Of course, after consulting with the team I discovered that their **"Scrumish"** was far away from **[Scrum](/blog/first-steps-to-learn-scrum/)**. So I decided to help them to discover what Scrum and Agile are.  I believe that it helped the team and our clients a lot to **create great products and collaborate** better.  I am so proud of the team, their work and journey from **"Scrumish"** to proper **[Scrum](/blog/first-steps-to-learn-scrum/)**!

Since that time, I have been working on multiple projects: software development with **[Scrum](/blog/first-steps-to-learn-scrum/)** or IT Infrastructure projects with Waterfall.  **Every day is a new lesson** for me about people, their way of working and thinking. 

## Back to Education

Now you know what was my journey from Education to **[Scrum](/blog/first-steps-to-learn-scrum/)**, so let’s talk about the last piece of this post - **How did I get back to Education?**

This story started around 1 or 1,5 year ago when I read an interesting book called **"Scrum. The Art of Doing Twice the Work in Half the Time"** written by Jedd Sutherland who is co-creator of **[Scrum](https://letsscrumit.com/first-steps-to-learn-scrum/)**.  I can definitely recommend this book to everyone. It was full of real life examples describing implementation of **[Scrum](https://letsscrumit.com/first-steps-to-learn-scrum/)**. 

![The Art of Doing Twice the Work in Half the Time](img/scrum_book.jpg)

Somewhere at the end of the book, I discovered one example of using **[Scrum](https://letsscrumit.com/first-steps-to-learn-scrum/)** that I believe **changed my life**, but it can also change the lives of many people in the world. 

The example that I am talking about was **eduScrum** - the way of using **Scrum in Education, at school**. 

You cannot imagine how happy I was when I realized that someone is already using the framework that I love at school. What is more, it is **changing the way of teaching** and **helps students to take ownership of their own learning process**.  It means that there is a space for creativity, critical thinking and a lot more at school.

## eduScrum - what happened next?

Once I discovered **eduScrum**, I started reading about it. I've done a lot of research to fully understand how it can be used in **education** and how original **[Scrum](https://letsscrumit.com/first-steps-to-learn-scrum/)** has been adjusted. 

Few months ago I participated in online eduScrum training with lovely women - **Paulina Orbitowska-Fernandez and Marta Orbitowska** who are certified **eduScrum trainers** in Poland ([eduScrum Polska](https://eduscrum.info/)).  It was a great experience, because I could not only learn more about **eduScrum**, but also discover **amazing Polish teachers** who were passionate and full of enthusiasm. 

That was also a moment when I realized that **eduScrum** is not a popular framework in Australia and I started having a new dream to **promote it** and to **create a community** of people who are **interested in Education**, who would like to **help students** to discover their potential. 

![eduScrum](img/edu_scrum.jpg)

#### https://www.eduscrum.nl/resources

It’s of course easy to say something like this, but much more difficult to implement it.  So I did my first step and contacted **Willy Wijnands** who is the creator of **eduScrum**. I asked him for advice and he recommended training that was conducted by him and **Kristina Fritsch** (eduScrum trainer in Germany). 

Attending the training was a great experience. I received a lot of **practical examples** from Willy and Kristina and my knowledge about **eduScrum** became even deeper and more extensive.  Training was divided into multiple online sessions and as at the end we had homework to **create our own project with eduScrum**.  I joined the team of 2 inspiring ladies - Marija & Carina and we are preparing the workshop for Marija’s students about Learning how to learn. 

This post is really long and I appreciate it if you are still reading it! :) It’s **almost the end** - I promise. 

## Innovative Education & eduScrum in Australia

Now I am on my way to becoming an official **eduScrum trainer** and I created my vision of how I can make a positive impact on Education in Australia and overall in the world.
One of my first steps is creating a group **"Innovative Education in Australia"** that can gather all people who are interested in developing innovative solutions that can make Education better. 

If you are a **teacher, parent, coach, facilitator** or someone who would like to help students to adapt to the fast changing world feel free to join the meetup group [Innovative Education in Australia](https://www.meetup.com/sydney-teachers-meetup-group/). I will be organizing our first meetup soon, so stay tuned!

![Innovative_Education](img/innovative_education.png)

## Next steps...

As you can see from this post, my **journey from Education to Scrum and back** was long and full of changes. Thank you so much for reading my story! I really wanted to show you who I am so that you can know me better. 

I would like to continue my **eduScrum** adventure and help you to discover this topic better.  In the upcoming weeks you can expect more posts about it. 

I hope to see you soon at one of my meetups! 

What was my first dream job? How did it happen that I decided to be a Scrum Master? What is the connection between Scrum and Education? Answers for all these questions are waiting for you in this post.

My journey from Education to Scrum and back

![]()

## Introduction

There are multiple reasons why people want to implement [Scrum](/blog/first-steps-to-learn-scrum) like: 

* increase efficiency,  
* improve work 
* create better products 
* become more interesting for clients 
* Better market position 
* [Scrum](/blog/first-steps-to-learn-scrum) and [Agile](https://agilemanifesto.org/) are fancy  
* my boss told me to change something  
* it’s an interesting idea, so why not?

You have your own reason but still don’t know how to start? Here you can find some tips.

## 1. Education

No matter why you decided to implement [Scrum](/blog/first-steps-to-learn-scrum/) in your company, you need to **start from the basics - learning** about [Scrum](/blog/first-steps-to-learn-scrum) and [Agile](https://agilemanifesto.org/). 

I recommend you to **read** my other post with [First steps to learn Scrum](/blog/first-steps-to-learn-scrum/) where you can find all that you need at the beginning of your Scrum journey.

## 2. WHY?

Once you have all the **basic knowledge** about [Scrum](/blog/first-steps-to-learn-scrum/), it’s time to understand **why** you want to implement it in your company. 

**Define your goal** before you will start other actions. You will use it later for **inspection** and verification if you are going in the right direction.  List also all **benefits** that you believe [Scrum](/blog/first-steps-to-learn-scrum/) will bring into your company/team. Believe me, you will need them soon.

I want to highlight - **Scrum is not a silver bullet.** This is also the moment to analyse if this is really something that your company needs. 

![WHY](img/why.webp "WHY")

## 3. Find your allies

In order to **implement** [Scrum](/blog/first-steps-to-learn-scrum/) in your company, you will need to have **allies** who will **support** your decisions and **help** you. I know that this part can be really difficult in old traditionally managed organizations. 

Likely, you will need to show higher management **why** [Scrum](/blog/first-steps-to-learn-scrum/) is the good idea for your company and what its **benefits** are. This is the moment when you can use the list that I mentioned about in the previous paragraph. 

If you answered to yourself **why** you want to implement [Scrum](/blog/first-steps-to-learn-scrum/) and how **it will impact** the company, you shouldn’t have a problem with explaining it to the management. The key is to **know "the WHY" first and be confident about it.** 

## 4. Spread the knowledge & collaborate

In this article, I assume that [Scrum](/blog/first-steps-to-learn-scrum/) is a totally **new idea** in your company. Before you will start using [Scrum](/blog/first-steps-to-learn-scrum/), you need to **teach others.** **Spread the knowledge** that you already have, **print** multiple copies of [Scrum Guide](https://scrumguides.org/scrum-guide.html) and **give it** to your colleagues at work. 

It will be also good to do the same as you did with higher management - **explain** to your co-workers **why** you think it is a good idea to **implement** [Scrum](/blog/first-steps-to-learn-scrum/) and how it will help them. 

Remember that [Scrum](/blog/first-steps-to-learn-scrum/) promotes **collaboration**. Before any action, ask your team, what **they are thinking** about it, write down all concerns, pros and cons. It will bring them **on-board** and will help in commitment to all future  actions.

You don’t use [Scrum](/blog/first-steps-to-learn-scrum) just for the purpose of using it. If people really **would be against it, you shouldn’t force it.** Sometimes it takes time to convince people that change is needed. And that’s something that you should **respect and give space for.** 

## 5. Define terms & actions

If you are on the same page with your colleagues and you **all agreed to implement [Scrum](/blog/first-steps-to-learn-scrum/)**, it’s time to have some agreements. 

* **Scrum Team roles and responsibilities** 

In order to start using [Scrum](/blog/first-steps-to-learn-scrum), you need to **create the Scrum Team** in your company. I would recommend starting from one Scrum Team at the beginning and test how they work. Remember that team size shouldn't be more than **10 people.** Team should be **cross-functional,** which means having all necessary **skills to generate the value.**

In the next step you need to decide about **roles** in the Scrum Team - who will be the [Product Owner](/blog/scrum-roles-2-product-owner/), [Scrum Master](/blog/scrum-roles-3-scrum-master/), [Developers](/blog/scrum-roles-1-development-team/). It is also important to define **responsibilities** and **expectations** from each team member. 

* **Scrum Values**

**Analyze** with your team what each [Scrum Value](/blog/the-importance-of-scrum-values/) means for you. How do you plan to use them in daily work? 

* **Scrum Events**

What is the **purpose** of each of the events? **Where and when** will you organize them? What will be your **Sprint length?**

* **Communication**

How do you plan to **communicate** with each other- face to face, email, phone, calls, communicators (Whatsapp, Slack etc)? What about communication with the client/business? Who will be doing it and how? 

* **Product Backlog**

Talk about **tools** related to [Product Backlog ](/blog/scrum-artifacts-1-product-backlog/)**management**. Do you plan to use flipchart and sticky notes or online tools like Microsoft Teams, Jira etc? 

It is also important to **define work items** in the [Product Backlog](/blog/scrum-artifacts-1-product-backlog/). Do you plan to use Epics, Features, User Stories, Tasks, Bugs, Impediments? If yes, **define** each of them. It’s important, because in every company people can define work items differently. 

Of course, the [Product Owner](/blog/scrum-roles-2-product-owner/) is the person **responsible for managing** the backlog, but the whole team needs to be aware of rules and definitions around it. 

* **Boards and work tools**

What about **visual reflection** of the work - boards? Do you plan to track your work using **Kanban** Board? Do you want to use online tools or stick with a simple paper board?

If you decide on a type of board, define all columns or sections included on the board. For example you can have columns: “To do, Active, Test, Done”. What **does it mean** for you that the work item is in each of those columns? When can you move items between columns?

## 6. Do it!

Uff… I know it can sound like **a lot of definitions and clarifications,** but it really matters. **Communication** is a crucial element of **collaboration**, so make sure that you are all on the same page. 

I know from experience that a **lack of all definitions** and common **understanding** of [Scrum](/blog/first-steps-to-learn-scrum/) related terms can create a lot of issues during development.  Once you clarify it, work can be much easier.

![Start](img/begin.webp "start")

If you’ve done all above, **let’s Scrum it!** 


**Don’t wait** for the moment when everything will be perfect, just try, **learn from your experience** and adjust if you need it.  Good luck on the wonderful [Scrum](/blog/first-steps-to-learn-scrum/) journey!

Do you need support in the implementation process? Register for [consultation](https://letsscrumit.com/services/implementation-consulting) with me. I will help you to prepare & start using Scrum.

If you think about implementation of the Scrum, but you don’t know where to start, this is the right post for you.

6 tips on how to implement Scrum

## Introduction

*This post has been updated based on the [Scrum Guide 2020](https://scrumguides.org/scrum-guide.html)

Knowledge about **Scrum without understanding Agile** is like learning how to dance without the music. You can do it, of course, but it doesn’t seem right for a longer period of time. 

That’s exactly what was discovered by the authors of [Agile Manifesto](https://agilemanifesto.org/) in 2001. They already had a lot of great ideas on how to improve software development like: [Scrum](/blog/first-steps-to-learn-scrum), Adaptive Software Development, Crystal, Extreme Programming etc., but they knew that there was **something important missing** in all of these.

\
During discussion in the Wasatch mountains of Utah, they wrote [Agile Manifesto](https://agilemanifesto.org/) summarizing Agile values and principles. 

## What exactly is Agile?

[Agile](https://agilemanifesto.org/) described by Jim Highsmith is:

> about delivering good products to customers by operating in an environment that does more than talk about "people as our most important asset" but actually "acts" as if people were the most important, and loses the word "asset".

[Agile](https://agilemanifesto.org/) is a **mindset and philosophy** that is following values and principles described in [Agile Manifesto](https://agilemanifesto.org/). 

Key characteristics: **people-driven,  promote collaboration, process adaptability.** 
It is focused on the human aspects of the work that are frequently underestimated.

![Agile Mindset](img/agile.webp "Agile Mindset")

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

## Scrum in Agile

Ok, great, we know some basics of [Agile](https://agilemanifesto.org/), but how can we connect it with [Scrum](/blog/first-steps-to-learn-scrum)?
We already know that [Agile](https://agilemanifesto.org/) is a **way of thinking** and it can be used by **implementation of different practices**. [Scrum](/blog/first-steps-to-learn-scrum) is **one of them.** 

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

> Scrum (n): A framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

It is a **set of values and rules** that can be used in order to **deliver a product.** In that case, [Scrum](/blog/first-steps-to-learn-scrum) is a great way to adopt the [Agile](https://agilemanifesto.org/) mindset. 

## What Scrum and Agile have in common?

* They are both representing shift from work focused on directing, control and processes to **individuals and interactions** between them. 
* **Working software** (working product) is more important than comprehensive documentation. It doesn’t mean that documentation is not important, but it exists only if it has value to the product. That’s why in [Scrum](/blog/first-steps-to-learn-scrum) all requirements related to the product are in the simplified version of the **Product Backlog.**
* **Collaboration with the customer** is important. Customers are not treated as “money makers” but we treat them with respect and listen to their needs and feedback. In order to create high quality products, business people and developers need to work together.
* **Change**  - it appears everywhere, all the time and that’s what [Agile](https://agilemanifesto.org/) and [Scrum](/blog/first-steps-to-learn-scrum) are aware of. That’s why in Scrum we need to inspect work during the Sprint and adapt accordingly in order to respond to changes. It is an important difference from previous approaches that were fully focused on the plan without adjusting it when changes appeared.
* **Iterative and incremental** approach - instead of delivering product all at once, after a long time of developing, [Agile](https://agilemanifesto.org/) and [Scrum](/blog/first-steps-to-learn-scrum) promotes dividing it into smaller pieces but doing it frequently. That’s how it will have value for the customer and it is also a great opportunity for inspection and adaptation to the market. 

![Collaboration](img/collaboration.webp "Collaboration")

## Not a silver bullet

I must highlight that **none of these ([Agile](https://agilemanifesto.org/) or [Scrum](/blog/first-steps-to-learn-scrum)) are silver bullets** and will not magically solve problems for us. But I would strongly recommend practising being Agile together with using the [Scrum](/blog/first-steps-to-learn-scrum) framework. It will increase the chance of delivering high value.

Are you still struggling with understanding how exactly you can use the **Agile mindset in the Scrum framework?** Register for [consultation ](https://letsscrumit.com/services/scrum-consulting)with me. I will be more than happy to help you.

Term “Agile” became much more popular in the last few years. Find out what it is and how it is related to Scrum. 

The Relationship between Scrum and Agile

## Introduction

\*This post has been updated based on the \[Scrum Guide 2020](https://scrumguides.org/scrum-guide.html)\
\
If you’ve never heard about **Scrum** or seen it in practice, it can be challenging to learn how to use it. I was there a while ago when I heard about **Scrum** for the first time. To clarify, I didn’t have an IT background, I was working in a financial company and I was trying to find a new path for myself. Then, I found out about **Scrum** and started **discovering** it. 

Currently, I have some **knowledge and experience** in this framework and I would like to share it with you. If you are a total newbie in this topic or you would like to better understand **Scrum**, follow the steps below. 

## 1. Open your mind

"Wait, what? I just want to learn about Scrum, why are you talking about opening my mind?"

Yes, that's right. The reason is simple. **Scrum** is probably different from anything you've heard about before and it will be really difficult to learn about it without **being open-minded** (This sentence doesn’t fully apply to teachers. Scrum used in education ([eduScrum](https://letsscrumit.com/discover-eduscrum)) has many similarities with the Montessori method.). 

I know that it is easier to follow your old thinking patterns, but try to **develop new mindset** in order to understand **Scrum.** 

## 2. Read Scrum Guide

[Scrum Guide](https://scrumguides.org/scrum-guide.html) is the summary of **Scrum** written by **Ken Schwaber and Jeff Sutherland.** They created this framework in the early 1990s and published the first [Scrum Guide](https://www.qagile.pl/wp-content/uploads/2017/01/Scrum-Guide-Feb-2010.pdf) in 2010. It has been revised multiple times in the meantime to adapt to the **changing world.** 

If you really want to **learn about Scrum**, this document should be your Bible for the upcoming months or so. I know a lot of people who were trying to use **Scrum** without it and it didn’t go well. Due to the popularity of this framework, there is a lot of misinformation about it, totally against the initial concept. 

So, **read it multiple times** and have it always nearby in case of any concerns or questions. You can find it in multiple languages on [scrumguides.org](https://www.scrumguides.org/).

## 3. Learn from others

There are many people who are already using **Scrum** and have a deep practical knowledge about this subject. If you want to meet them and learn about their experience with **Scrum**, I strongly recommend being part of the community on [scrum.org](https://www.scrum.org). It is a reliable website, created by **Ken Schwaber - co-creator of Scrum**.  You can find a lot of **interesting articles** in their **blog** section and follow or join **discussions on the forum.**

What is more, they have multiple **Scrum related resources** that are well-organized and based on the [Scrum Guide](https://scrumguides.org/scrum-guide.html). I spent hours on that website and it helped me to sort out my knowledge about **Scrum**.

If you can, join the meetings of your **local Scrum communities**. You can be surprised how many great people you can meet there.

![Learn from others](img/learn_others.webp "Learn from others")

## 4. Read The Agile Manifesto

You can use Scrum without reading [Agile Manifesto](https://agilemanifesto.org/). But in my opinion, reading this document helps to **put Scrum into a broader Agile context.** 

[Agile Manifesto](https://agilemanifesto.org/) was created by 17 software development representatives in order to sum up their **new “agile” way of thinking**. They summarized it in **4 values and 12 principles.**  You can find more details on [Agile Manifesto website](https://agilemanifesto.org).

## 5. Be prepared for difficulties

As you could read in the [Scrum Guide 2017](https://scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-US.pdf):

>  Scrum is lightweight, simple to understand, but difficult to master. 

It is a perfect **description of the Scrum,** because using it daily and **“doing” it well** can be difficult.  Important success factor is being **mentally prepared** for these difficulties. 

I am sure that you will not be able to think about all the issues that will happen in the future, but prepare your mind. Write down all subjects that you think you can **struggle with** and **brainstorm** how you could avoid or minimize negative effects. 

## 6. Start implementing it and do not stop learning!

I could continue the list with multiple learning resources, but the truth is that the **biggest lesson is - using it!**  Every organization and case of implementing Scrum is different. You can have all theoretical knowledge, but it will never replace **learning from practice.**  You should already know from the [Scrum Guide](https://scrumguides.org/scrum-guide.html) that: 

> Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. 

It means that in **this framework you learn from experience.** That’s how you can discover the best solutions for yourself and improve your work every day. 

I hope that those steps will help you to **start and enjoy your Scrum journey**. I know that you can find a lot of sources of knowledge about this subject on the Internet, but remember - it is better to build a good foundation and and then discover more. 

If you know the basics, but you **still struggle with using Scrum,** feel free to reach out to me and register for my [Scrum Master consultation](https://letsscrumit.com/services/scrum-consulting).

Good Luck!

Would you like to discover what Scrum is, but you don’t really know how to start? This post is perfect for you. Jump in! 

9 posts tagged with #agile