Scrum Training – Presentations Introduce Scrum
Scrum - Introduction for Scrum Masters
You can use this presentation to learn, or teach the role of a Scrum Master. It describes in detail all aspects of the Scrum framework, and describes being a Servant Leader. Since the Scrum Master is expected to know the most about the Scrum framework and helps the team members work within its rules, the Introduction for Scrum Masters presentation is 43 minutes long. It describes the role of the Scrum Master, but also the roles of the Product Owner, the Development Team, the artifacts each of them maintains, and the events of Scrum. It is a detail introduction of the Scrum framework, so a Scrum Master understands what they will be encouraging the Scrum Team to do.
Scrum Master and Servant Leader
This presentation describes in more detail the role of the Scrum Master. Noting that the Scrum Master ensures that everyone follows the Scrum and enterprises, rules and practices. That they work to remove impediments affecting the team, and make sure the Development Team and customer use terms that they both can understand. The presentation points out that a Scrum Master is a Servant Leader and it goes into more detail about being a Servant Leader
Scrum Overview
The Scrum Overview goes through a cycle of Scrum events, describing each Event, the Roles of Scrum, and the Artifacts used by Scrum Teams. The Overview notes that Scrum employees the three pillars of Empirical Process Control: Visibility, Inspection and Adaption. It shows each of these being used throughout the Scrum framework.
Scrum Roles: Product Owner and Development Team
This presentation gives a more detail description of the role of the Product Owner. Pointing out that there is only one Product Owner per product and they maintain the list of requested deliverables put on the Product Backlog. This presentation has a detailed description of the Development team. Noting that the team is cross functional and as a whole is accountable for each item to be delivered. The team should work at a pace that can be sustained forever.
Scrum Events: Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective
The heart of Scrum are iterations known as Sprints. This presentation goes into more detail about a Sprint and its four Scrum events: Sprint Planning, Daily Scrums, Sprint Review and Sprint Retrospective. Each Sprint is intended to create an increment of functionality that is production ready and potentially releasable. The presentation notes that a Sprint can only be cancelled by the Product Owner. In Sprint Planning the Scrum Team reviews the highest priority items on the Product Backlog and the Development team selects the items they think they can complete in the next Sprint while meeting the “Definition of Done”. Then the Development team discusses how they plan on completing the items they just moved to their Sprint Backlog. The Development team conducts Daily Scrums to keep fellow team members up to date on what has been completed, what each member plans on working on next, and what obstacles may be impacting them. Two more events occur at the end of a Sprint, a Sprint Review and a Sprint Retrospective. During the Sprint Review the Scrum Team shows the customer the Increment of work completed meeting the Definition of Done, and gets feedback from the customer. In the Sprint Retrospective the Scrum Team discusses how they can refine the Sprint process to make it better.
Scrum Artifacts: Product Backlog, Sprint Backlog, Burndown Charts and Increment
This presentation points out that the Product Owner maintains a list of requested deliverables in a Product Backlog. The items are prioritized, so the most valuable items are at the top and are worked on first, to maximize the product’s value. The list includes both functional and non-functional requirements. The Development team is responsible for maintaining a Sprint Backlog which contains the items the Development team pulled from the Product Backlog. The Development Team’s description of the work should contain just enough detail so the Development Team knows what needs to be done. The team should avoid creating a complete design up front. Burndown Charts can be used to graphically show progress completed on a Product Backlog or a Sprint Backlog. The average number of estimate units can be calculated as Velocity and a trend line of the Velocity can be plotted on the graph to estimate completion based on the current known items. Tracking the amount of work completed each Sprint, helps predict what can realistically be expected in the next Increment of development. Each Increment needs to meet the team’s Definition of Done, be in a usable condition and potentially releasable.
Scrum Master Certification
In preparation for acquiring a Scrum Master Certification, this presentation can be the first step, or be used in conjunction with other resources, to learn in detail all aspects of the Scrum framework, including the roles, events and artifacts.
Here is a snapshot of the presentation's agenda:
