Scrum Training – Presentations Introduce Scrum
Scrum - Introduction for the Customer
The Introduction for the Customer presentation is 15 minutes long. It emphasizes that the customer will primarily work with the Product Owner, to indicate, what they consider to be the most valuable items for the product being developed. It also goes through the Scrum events they will be part of, while also introducing some of the terminology and artifacts used in the Scrum framework.
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 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 Sprint and Sprint Review
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. At the end of a Sprint the team conducts a Sprint Review. 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.
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. 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.
Here is a snapshot of the presentation's agenda:
