Scrum Training – Presentations Introduce Scrum
Scrum via Sprints
The Scrum via Sprints presentation, takes the audience through 3 cycles of Scrum events known as Sprints. In the presentation a Scrum team receives a project, sets up the artifacts to support the project using Scrum, and goes through the Scrum Events, showing iterations of incremental development. The 43-minute presentation, shows a product going from conception, to a production ready, potentially releasable product.
​Three Scrum Sprints
The Scrum Team receives a project and starts off listing the deliverables on a white board. They decide how long each iteration should be and what is realistic to complete in the first iteration. During the Daily Scrum the Development Team points out an issue encountered with some stakeholders, and the Scrum Master indicates he will address the issue with the stakeholders. At the end of each iteration, the team reviews what had been completed in the Increment of development in a Sprint Review, and talks about what changes could be made to make the process better for the team during a Sprint Retrospective. In the second iteration they start using Scrum terms like calling the iterations Sprints. The Product Owner replaces the list of requirements on the white board, with a Product Backlog in a spreadsheet. In their Sprint Planning they start using Story Points for estimates and create a Sprint Goal. During the Daily Scrum the Development team points out that they started using a Scrum Board as a Sprint Backlog to track their work. In the third Sprint, the Product Owner points out that the team completed more Story Points in Sprint 2 than they did in Sprint 1, by showing them a Burndown Chart that included a trend line of their Velocity. The team included some late changes into their list of deliverables and used their Velocity from past Sprints to decide what realistically could be completed in the next Sprint. They also decided to adjust their Definition of Done. At the end of the Sprint the Product Owner indicated that once gain the amount of Story Points completed increased compared to earlier Sprints. It closes with the team showing their customers the final Increment of development and the documentation hand-outs.
​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. 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 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 Development Team, Sprint Backlog and Daily Scrum
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. It note that the team should avoid creating a complete design up front. The Development team conducts a Daily Scrum to keep fellow team members up to date on what has been completed, what each member plans on working next, and what obstacles may be impacting them.
​Burndown Chart and Scrum Increment
​Burndown Charts can be used to graphically show progress completed on either 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. By 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
​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.
Scrum Sprint Review and Sprint Retrospective
​Two 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 Overview
The presentation ends with an Overview of Scrum that goes through a cycle of the 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.
