Scrum Training – Presentations Introduce Scrum
Scrum - Introduction for a Development Team
The Introduction for the Development Team presentation, describes the role of the Development Team, the artifacts they maintain and the events of Scrum. It describes how a team becomes self-organized. This presentation reviews the Scrum framework from a Development Team’s perspective.
Scrum Development Team and Self-Organized Teams
This presentation has a more detailed description of the role of the Development team. The team is cross functional and that the team as a whole is accountable for each item to be delivered. They should work at a pace that can be sustained forever. The team is Self-Organized, so the presentation includes a slide about Self-Organized teams. They should have authority, the required resources, the necessary information and be accountable.
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 Sprint and Sprint Planning
The heart of Scrum are iterations known as Sprints. This presentation indicates that a Sprint consist of 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. It also 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.
​Scrum Sprint Backlog and Sprint Burndown Chart
The presentation points out that the Development 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. Burndown Charts can be used to graphically show progress completed on 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.
​Daily Scrum and Scrum Board
The Development team will conduct 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. The Development team may choose to use a Scrum Board to visually see the Sprint Backlog and the progress that has been made.
​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 Product Owner and Product Backlog
In this presentation a couple of slides go over a few key items about the Product Owner and Product Backlog. Pointing out that the Product Owner maintains the list of requested deliverables put on a Product Backlog. It notes that 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.
​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.
Here is a snapshot of the presentation's agenda:
