Preparation for attending a Certified ScrumMaster®, Scrum Product Owner®, or Scrum Developer® course.
In order to be well prepared and able to gain the most when participating in the live sessions during the course, please perform the activities on this page.
Scrum Foundations videos (45 mins):
The following are 14 short animations covering the Theory, Team, Events, Artefacts, and Rules of Scrum.
In total they are 45 minutes in duration.
01 – Scrum Theory (5.47)
Scrum is a lightweight framework made up of a few accountabilities, events, artefacts and rules. When used to enable Empirical Process Control it allows working in highly complex, uncertain and dynamic situations. The principles of transparency, inspection and adaptation are key to effective Empirical Process Control, so the Scrum framework supports each of these principles in multiple ways.
02 – Scrum Values (3.16)
A team’s success with Scrum depends on five values: commitment, courage, focus, openness and respect.
03 – Cross-Functional and Self-Organizing Teams (1.42)
Wherever possible, Scrum Teams interact directly with stakeholders to discover and deliver incremental improvements within short iterations. The Scrum Team has all the cross-functional abilities to perform all the activities needed to evolve the product from one increment to the next. The Scrum Team also organises and manages itself, deciding what needs to be done and how to do it.
04 – Scrum Team (2.39)
Now defined as a single Scrum Team. The three accountabilities (formerly called roles) replace all existing roles involved in project planning, budgeting, research, design, analysis, development, testing, etc.
05 – Introduction to Scrum Events (3.34)
Scrum makes extensive use of time boxing; limiting an activity to a maximum amount of time. Scrum has five time-boxed events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
06 – Sprint Planning (7.35)
The first event during the Sprint is Sprint Planning. The focus of this event is for the Scrum Team to clarify and prepare for what they will likely work on this Sprint.
07 – Daily Scrum (3.40)
Even within a short iteration, things rarely go as expected for very long. The Daily Scrum is a re-planning event the Development Team performs each day, for up to a maximum of 15 minutes.
08 – Sprint Review (2.35)
The outcomes of the current Sprint are reviewed in the penultimate event, the Sprint Review. The Scrum Team and interested stakeholders review the latest increment, learning and identifying how it could be improved further. The experiences of the Scrum Team are shared to increase the understanding of the whole group and improve transparency about the impediments encountered.
09 – Sprint Retrospective (2.25)
The final event of the Sprint is the Sprint Retrospective. The Scrum Team reflects on their ways of working and identifies experiments they intend to perform in their continual search for improvements.
10 – Scrum Artefacts (3.48)
Three artefacts are used in Scrum. The most valuable is the Increment, because it provides value to the stakeholders. The Product Owner uses a Product Backlog and the Development Team use a Sprint Backlog. The Increment and Product Backlog are long-lived. The Development Team create a new Sprint Backlog each Sprint.
11 – Product Backlog (2.20)
The Product Backlog is used by the Product Owner to manage and communicate their current thinking on how the product should evolve. It is never complete and is continually evolving due to the complex, uncertain and dynamic environment in which product development is taking place.
12 – Product Backlog Refinement (2.16)
To accommodate for variable amounts of change being introduced into the Product Backlog, ongoing clarification and refinement of items nearest the top is necessary. This is carried out on an as-needed basis to keep the Items at the top of the Product Backlog ‘ready’ for taking into the next Sprint or so. Product Backlog Refinement is not a Scrum Event.
13 – Sprint Backlog (2.33)
The Sprint Backlog is used by the Development Team to manage and monitor its work during the current Sprint.
14 – The Increment and Definition of Done (1.58)
The Increment contains all the latest improvements developed during the current Sprint, added to all the existing valuable capabilities from previous Sprints. The Increment must be in a releasable state as the Product Owner may choose to release it at the end of each and every Sprint. The Scrum Team agrees what work and quality assurances are performed on the Increment each and every Sprint, to ensure it is kept in a releasable state. This agreement is known as the Definition of ‘Done’.
~~~ END ~~~