6 tips on how to implement Scrum
May 11, 2020 • 6 min to read
If you think about implementation of the Scrum, but you don’t know where to start, this is the right post for you.
Table of Contents
There are multiple reasons why people want to implement Scrum like:
- increase efficiency,
- improve work
- create better products
- become more interesting for clients
- Better market position
- 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.
I recommend you to read my other post with First steps to learn Scrum where you can find all that you need at the beginning of your Scrum journey.
Once you have all the basic knowledge about 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 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.
3. Find your allies
In order to implement 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 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 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 is a totally new idea in your company. Before you will start using Scrum, you need to teach others. Spread the knowledge that you already have, print multiple copies of Scrum Guide 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 and how it will help them.
Remember that 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 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, it’s time to have some agreements.
- Scrum Team roles and responsibilities
In order to start using 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, Scrum Master, Developers. It is also important to define responsibilities and expectations from each team member.
- Scrum Values
Analyze with your team what each Scrum Value 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?
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 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. 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 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 related terms can create a lot of issues during development. Once you clarify it, work can be much easier.
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 journey!
Do you need support in the implementation process? Register for consultation with me. I will help you to prepare & start using Scrum.
Would you like to read more about education?
Sign up for the Newsletter & join Let's Scrum it community!