Please enable JavaScript.
Coggle requires JavaScript to display documents.
Scrum (Rituals (Retro (review how things went - what was good, bad,…
Scrum
Rituals
Daily Stand Up
Same time, every day, time boxed, 3 questions, a chance to speak
Small, Brief, Pointed - highlight priorities and obstacles
-
-
Retro
review how things went - what was good, bad, improvements
-
-
-
-
Review
An opp to demonstrate what was done in sprint, get feedback from stakeholders, and what to do next
-
-
Leads to a revised backlog, and the probable items for the next one
Grooming / Story Time!
Advance work, prepping stories for future sprints
Planning
What can realistically be achieved in sprint, what is the goal
-
-
Based on Empiricism
-
-
-
Emphasises Creativity, Flexibility and Productivity
The Sprint
Team, not individuals responsible for delivering the increment
-
-
-
Artifacts
Sprint Backlog
-
Can change, dependent on if workload is less/more
-
Stories list is fixed, tasks can change
-
Product Backlog
-
Managed by the PO, responsible for stories
-
Contains all the stories, tasks, bugs, issues
Items at the bottom are generally placeholders, unformulated, underscoped
-
-
-
'Teams'
Scrum Team
Product Owner
-
-
Defines the overarching goal for a release, who its for, why they need it.
Owns the backlog, prioritises it and fills it
Scrum Master
Team coach - peer position, not the boss
-
-
-
-
-