Scrum Training – Presentations Introduce Scrum
Scrum - Introduction for a Product Owner
​You can use this presentation to learn, or teach the role of a Scrum Product Owner. The presentation describes in detail the role of the Product Owner, the artifacts they maintain and events of Scrum. It describes how to write user stories. This presentation reviews the Scrum framework from a Product Owner’s perspective.
Scrum Product Owner, Product Backlog and Stories
This presentation gives a more detail description of the role of the Product Owner and the Product Backlog they maintain. Pointing out that there is only one Product Owner per product and they maintain the list of requested deliverables put on the Product Backlog. It notes that the items on the Product Backlog 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 items on the Product Backlog may be described in a format known as user stories, so the presentation includes a slide about writing user stories.
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 Overview
​Scrum Sprint, Sprint Planning and Daily Scrum
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.
Scrum Increment, Sprint Review and Sprint Retrospective
​Each Sprint the team works towards creating an Increment of development. An Increment needs to meet the team’s Definition of Done, be in a usable condition and potentially releasable. 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 Development Team and Sprint Backlog
In this presentation it describes a few key items about the Development team and the Sprint Backlog they maintain. The presentation points out that the Development team is self-organized and cross functional. The team is responsible for maintaining the Sprint Backlog and that the description of the work should contain just enough detail so the Development Team knows what needs to be done. That the team should avoid creating a complete design up front.
Scrum Master
This presentation describes a few key items about 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.
​Product Owner Certification
In preparation for acquiring a Product Owner Certification, this presentation can be the first step, or be used in conjunction with other resources, to learn in detail all aspects of the Product Owner’s role, the events they attend, and the artifacts they maintain.
Here is a snapshot of the presentation's agenda:
