what is scrum? project management beyond the promise
TRANSCRIPT
What is Scrum?Project Management beyond the promise
@bartvermijlen
Overview
• introduction
• roots
• principles
• a framework
• roles
• timeboxes
• rules
• artefacts
• money for nothing and change for free
Introduction
A project has 4 fixed aspects• Time• Budget• Quality• Scope
Introduction
A project has 4 fixed aspects• Time (?)• Budget• Quality (?)• Scope (?)
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!
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)
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)
Scrum Principles
Agility = Responsiveness to change
Transparency
Inspection
Adaptation
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
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
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
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
Scrum artefacts
Product backlog• Managed & prioritised by PO• User stories
Sprint backlog• Quantified tasks (derived from product backlog)• Managed by Team
Scrum artefacts - Burndown chart
hours/points
times1 s2 s3
Scrum artefacts - Burndown chart
hours/points
times1 s2 s3
Scrum artefacts - Scrumboard
Change for free
= obvious
PO can reorder priorities at every sprint planning
Money for nothing
hours/points
times1 s2 s3
pay back
70% to
customer,
Keep 30%
Remove functionality
Further reading
- agilemanifesto.org
- scrumalliance.org
- scrum.org/scrumguides
- scrum.jeffsutherland.com
- Ken Schwaber: “Agile Project Management with
Scrum” (Microsoft Press)
@bartvermijlen