This is the third post in a series related to the Zen of Scrum presentation available on SlideShare.net.
In the previous post I wrote about Scrum's five values. Now it's time to list the roles, events and artifacts defined by Scrum.
Some of the things associated with Scrum is actually XP practices and not dictated by Scrum at all, though they have become de-facto standards and considered best practice by many.
The Scrum guide, the Scrum guidance document, is regularly revised. This is to be expected, of course, as Scrum adheres to agile principles of which continuous improvement is one.
For example, burndown charts were recently removed giving teams more freedom to decide how to visualize progress (remaining work) in sprints.
Scrum defines three roles, four meetings (ceremonies) and three artifacts. These are listed below but only described briefly as I plan to write about them in more detail in coming posts.
The number of roles is deliberately held to a minimum: more roles has a negative impact on communication.
Scrum defines three roles:
- Product Owner, responsible for the product backlog and to maximize ROI (Return On Investment).
- Scrum Master, ensuring Scrum is understood and enacted.
- Team, which is self-organizing and cross-functional.
Scrum defines four meetings:
- Sprint planning, whose purpose is to select and estimate work for the coming iteration.
- Daily scrum, which is a short stand-up meeting to synchronize the team.
- Sprint review, where the team demonstrates what has been done, and talk about what is planned next.
- Retrospective, to inspect and adapt the process; improving how the team applies agile and Scrum.
Scrum defines three artifacts:
- The product backlog, an ordered list of everything that might go into the product.
- The sprint backlog, which is the work forecasted by the team to be completed in the next sprint.
- Product increment, the result of the efforts up to the current sprint.