What is Scrum? Principles, rules, roles, artefacts, timeboxes of Scrum.

1. What is Scrum?
Project Management beyond the promise
@bartvermijlen

2. Overview
• introduction
• roots
• principles
• a framework
• roles
• timeboxes
• rules
• artefacts
• money for nothing and change for free

3. Introduction
A project has 4 fixed aspects
• Time
• Budget
• Quality
• Scope

4. Introduction
A project has 4 fixed aspects
• Time (?)
• Budget
• Quality (?)
• Scope (?)

5. Introduction
A project has 4 fixed aspects
• Time
• Budget
• Quality (?)
• Scope
A scrum project has 3 fixed aspects
• Time
• Budget
• Quality
Scope is not fixed!

6. Scrum Roots
Agile Software development:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
(Agilemanifesto.org)

7. Scrum Roots
Agile Software development:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
(Agilemanifesto.org)

8. Scrum Principles
Agility = Responsiveness to change
Transparency
Inspection
Adaptation

11. Scrum = a framework
Roles
• Team
• Product Owner
• Scrum Master
Timeboxes
• Sprint
• Sprint planning
• Sprint review (+ retrospective)
• Daily Scrum
Artefacts
• Product backlog
• Sprint backlog (-> Scrumboard)
• Burndown chart

12. Scrum Roles
Team
• developers, testers, UX designers, SEO/Analytics,…
• 2-7
• self organising
• split product backlog into tasks
Productowner
• define & prioritise product backlog / user stories
• negotiate definition of "Done"
Scrum Master
• guard scrum process
• remove team impediments

13. Scrum Timeboxes
Sprint
• 1-4 weeks
• ends with potentially shippable products (working software)
Sprint planning (SM, Team, PO)
• 1-8 hours
Daily Scrum (SM, Team)
• 15 mins
• yesterday/today/impediments
Sprint review (SM, Team, PO)
• 30 mins - 4 hours
• Demo or Die
• acceptance of user stories by PO
Sprint retrospective (SM, Team) !
• lessons learned

14. Scrum Rules
• Priorities never change during a sprint
• Nobody (neither PO) must interfere during a sprint
• Team can ask new user stories when finished early to PO
• Team is self-regulating

16. Scrum artefacts
Product backlog
• Managed & prioritised by PO
• User stories
Sprint backlog
• Quantified tasks (derived from product backlog)
• Managed by Team

17. Scrum artefacts - Burndown chart
hours/points
s1 s2 s3 time

18. Scrum artefacts - Burndown chart
hours/points
s1 s2 s3 time

19. Scrum artefacts - Scrumboard

20. Change for free
= obvious
PO can reorder priorities at every sprint planning

21. Money for nothing
hours/points
pay back
70% to Remove functionality
customer,
Keep 30%
s1 s2 s3 time

22. Further reading
- agilemanifesto.org
- scrumalliance.org
- scrum.org/scrumguides
- scrum.jeffsutherland.com
- Ken Schwaber: “Agile Project Management with
Scrum” (Microsoft Press)

23. @bartvermijlen