Scrum Master Certified™
For you, who has to ensure a well-functioning Scrum process.
With a Scrum Master certification, you can ensure that the Scrum team has optimal working conditions for them to deliver the project.
You will learn…
✔ How to think and work in agile projects.
✔ The Scrum concepts and an understanding of their usage.
✔ Your role as Scrum Master and additional roles within Scrum.
✔ The necessary tools for you to handle and manage a Scrum project.
✔ How you can help to implement Scrum in your organisation.
You do not need any other certification to participate in this Scrum Master Certified course.
Scrum is a distinctly flexible management tool which can be adapted to many different fields, cultures and line of businesses. Everything is based upon a massive best-practice knowledge and the framework has long since proven itself. It is the world’s most commonly utilized best-practice method of agile project management and product management. In the sport rugby, Scrum is the way to restart the game after an infringement. Thus the name of the method that is often used in projects with high levels of unpredictability, and where product specifications and demands are altered throughout.
A Scrum Master guides, facilitates and teaches Scrum on a practical level to everyone involved in the project, clears obstacles for the team and makes sure that everyone adheres to Scrum processes.
Aim of the course
When you have completed this course, you will be able to handle the role of Scrum Master in a professional context.
Methods of teaching
Our Scrum Master course is based on independent studies via video-based e-learning. You can stream your lessons when and where it suits you and in whichever pace works for you. The combination of videos, quizzes, written exams and supplementary material will provide good support, both during and after the course.
About the teacher
Jesper Hansen, accredited teacher of Scrum®
Jesper is a certified project manager, internally in General Electric and Capgemini and externally in Scrum, PRINCE2®, MSP®, AgilePM® and IPMA. He has got 18 years of experience with full-time project and programme management within different lines of businesses: the public sector, insurance, instrument development, Life and Pension, finance and product development. Teaches primarily Scrum and AgilePM®.
4 hours of video
55 supplementary materials
20 hours estimated study time
12 month access
Computer, tablet and mobile
Proof of your certification
Official Scrum manual can be purchased
Buy course here!
Course content: Scrum Master Certified™
This section explains what Agile is and what it means to be “adaptive”. There are a lot of buzzwords regarding “Agile”: Agile Approach, Agile Methodology, Agile Teams, Scrum etc.
Ground rules for the course, learning goals and your benefits of the course. Description of the learning methods used in the course, and an overview of other related courses. Finally there is an introduction to the exam – for a description of the exam go directly to “Exam”.
Agility is our ability to create and react on changes aiming on enhancing productivity in a challenging environment.
Give you important knowledge about the agile manifest. It is not just the words but the mindset behind.
Agile was not developed in one day. During the last few decades the need for a flexible response to an ever changing world has been more and more evident. Adaptive project management gives more dynamics, flexibility and the possibility to react on changes.
Scrum has become the most popular agile method in the world. In this chapter you get an overview of Scrum, describing the 6 aspects, 6 principles and the 19 processes.
5 videos – 72 min.
By “Core Roles” we mean to have a key role. “Non Core Roles” is what matches the project’s stakeholders. Like all other project models, the success of a Scrum project often depends on its ability to handle the project stakeholders. An underrated discipline in Scrum. In Scrum projects, it would also be preferable to do an actual stakeholder analysis.
The Product Owner is a core role and the decision maker of the project. Often called the voice of the customer.
The Scrum Master is a core role in Scrum, and the role is based on the concept of “servant leadership”. Serves as a servant for the team removing obstacles and impediments for the team.
The Scrum Team is a core role, and is responsible for delivery of all the requirements agreed with the Product Owner. The team is self-organizing and has a collective responsibility of the deliver
Non-core roles are all the other stakeholders of the project. They are not involved in every day work in the team, but are all important stakeholders. Some non-core roles are: Customers, users, sponsors, vendors and the Scrum Guidance Body.
5 videos – 36 min.
Scrum phases are much alike phases known from waterfall methods, sometimes referred to as ‘stages’. The big difference lies in the fact that all phases are involved in a single sprint (1-6 weeks duration, typically 2-4 weeks). This in principle means that a potentially shippable product should be delivered to the customer after each sprint. In this way all the scrum phases come into play, and all integration points will be activated and tested for the actual situation. Problems and risks will also be identified at an early stage of the project, which saves valuable time and money.
The first phase in a Scrum Project is Initiate, and it constitutes the starting point of the project. The vision for the project is created, team members appointed, stakeholders identified and the overall product features are described in the form of epics. Furthermore the release plan for the project is laid down in this phase.
Plan and Estimate
In plan and estimate the Scrum Team is involved in creating, approving, estimating and committing to user stories for the following sprints. Epics are broken down to user stories and tasks are identified. Estimation and planning of the next sprint – creating the sprint backlog.
Implement is the daily team work of developing deliverables – products. In this phase the product owner also has the responsibility to keep the product backlog up-to-date and prioritized at all times.
Review and Retrospect
Firstly the team presents the deliverables produced in the sprint for the customers, and collects any valuable feedback given to them. Next the team has an internal process of looking back and learning any lessons from the preceding sprint, so that the team process may be optimized.
In the release process the team must gain the acceptance of deliverables from the customer. Also securing knowledge and lessons are documented for others to use in the next agile project.
20 videos – 64 min.
Many people believe that Scrum is only for small uncomplicated projects. That is not true – Scrum can easily scale up in relation to programs or large projects.
Transition to Scrum
Since Scrum in its project approach is significantly different from the traditional way of running projects, it is of course interesting to look at how to get started. You either choose Top Down or Bottom up.
2 videos – 26 min.
Practical knowledge of various tests
All tests are in English since the exam is in English.
These are additional tests, so see the extra tests as exam training.
Case Study 1: Create project vision
Based on the case “VMfoods”, prepare a project vision. When you have made your offer, look at what other students have come up with. The purpose is that you yourself are able to create a vision based on the information that can be generated.
Case Study 2: Create an Initial Product Backlog
To solve this case study, download the preliminary product backlog under “Materials”. The list shows examples of “Epics”. Your task is to add another 5 “Epics”. The only information you have is the case.
The purpose is for you to be able to identify and produce Epics.