Scrum Training – Presentations Introduce Scrum
Scrum Overview
The Overview of Scrum presentation, goes through a cycle of the Scrum events, describing each Event, the Roles of Scrum and the Artifacts used by Scrum Teams. It is 6 minutes long, with the intention of giving a quick overview of Scrum to those that are new to the Agile framework.
In this presentation it 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
The Overview points out that the Product Owner works closely with the customer and maintains the Product Backlog. The Development team consists of 3 to 9 members, that are cross functional, self-organized and they create the deliverables. The Scrum Master is a servant leader and helps the Scrum Team follow the rules of Scrum.
Scrum Artifacts
The presentation describes the artifacts of the Scrum framework. How the Product Backlog is maintained by the Product Owner and contains a prioritized list of requested deliverables for the product. How the Development team selects items off the top of the Product Backlog and moves them to a Sprint Backlog to be worked on. These documents are used to plan an increment of development. Other documents mentioned include Burndown Charts and a Scrum Board.
Scrum Events
The presentation goes through a Scrum cycle or iteration, known as a Sprint. Within a Sprint it describes how a Scrum Team starts with Sprint Planning to review the items at the top of a Product Backlog, and the Development team selects items off the top of the Product Backlog, then moves them to the Sprint Backlog. Points out that the Development Team uses Daily Scrums to communicate what work has been completed, what will be worked on next, and any issues that are encountering. Towards the end of the Sprint, the Scrum Team has a Sprint Review to show the Customer the Increment of development completed during the Sprint, and discusses what would make the product even more valuable to the customer. Then at the end of a Sprint, the Scrum Team will have a Sprint Retrospective, to look at how they can improve their process for future Sprints.