Scrum
Based on Empiricism
Inspection
Adaptation
Transparency
'Teams'
Scrum Team
Development Team
Product Owner
Scrum Master
Development Team
Rituals
Daily Stand Up
Retro
Review
Grooming / Story Time!
Planning
Artifacts
Sprint Backlog
Product Backlog
Defined at start of sprint
Can change, dependent on if workload is less/more
Sprint Backlog belongs to the development team
Ordered by Value
Managed by the PO, responsible for stories
Items from this formulate the sprint backlog
Same time, every day, time boxed, 3 questions, a chance to speak
What can realistically be achieved in sprint, what is the goal
An opp to demonstrate what was done in sprint, get feedback from stakeholders, and what to do next
review how things went - what was good, bad, improvements
The Sprint
Team, not individuals responsible for delivering the increment
Value Maximiser
Represents and filters requests from stakeholders to the team
Defines the overarching goal for a release, who its for, why they need it.
Owns the backlog, prioritises it and fills it
Team coach - peer position, not the boss
advises team on process and progress
facilitator
removes impediments
Responsible for delivering stories and the increment
Does all development work
Self organising
Owns the estimation process
Owns the 'how to do the work' decisions
Avoids the 'not my job' mentality
7 plus or minus 2
What will we do? And how will we do it?
Small, Brief, Pointed - highlight priorities and obstacles
Advance work, prepping stories for future sprints
Do not cancel if no deliverable
Gather data
Generate insights
Decide what to do
Product Owner can terminate the sprint
Contains all the stories, tasks, bugs, issues
Items at the bottom are generally placeholders, unformulated, underscoped
Stories list is fixed, tasks can change
Measures
Burn Down Charts
Work left to be done over time
Shows scope variants
Sprint v Release burn down
Burn Up Charts
Show the teams velocity
Task Board
To Do / In Progress / Blocked / Done
Definition of Ready / Done
Designs
Testing
Documentation, artifact transparency
Unit Testing
Code reviews
click to edit
Scrum team creates the sprint goal
Estimates are the responsibility of the Development Team
15 mins
4 hours or less
8 hours or less
3 hours or less
Helps team decide what to work on, it's velocity/capacity
Dev team only
Emphasises Creativity, Flexibility and Productivity
Leads to a revised backlog, and the probable items for the next one
Cone of Uncertainty
How much is known about the product over time