Scrum Good Practices Checklist

PracticeTask
Initial Backlog (Story Mapping) SessionHeld before sprint one
If Work being completed before the Sprint, then story mapping held earlier
Product VisionProduct Vision Workshop held
Unfolded to team before sprint one
Visible to all at all times
Team SetupTeam size max 9
Team members are 100% dedicated to team
All required disiplines are present and colocated
Team is motivated and trained on Scrum Fundamentals
Dedicated Product Owner and Scrum Master present
Team is formed for an extended period of time (3+ sprints)
FacilitiesRoom fits team (max 9) comfortably
Office suplies are plentiful (Markers, Post-Its, Tape, Whiteboard, Flip-Charts)
Workspaces are setup (PCs, desks, network, central collaboration table)
Daily Standup (Also known as the daily Scrum / huddle)Stand-Up Brownbag session held
Being held every day of sprint at set time and location
Starting on time and is completed within 15mins
Development team sticking to discussing the three questions
Team pointing to sprint backlog item when discussing.
Entire Dev Team partaking in every session when in the office
Progress and impediments are made visible on the Scrum Board
% of standups held without Scrum Master and Product Owner (showing independance)
Definition of Done (DOD)DOD Brownbag session held
Team and Product Owner create and agree on DOD at onset
DOD reviewed and revised during each Sprint Retrospective
DOD is known to each member and visible on wall in area
Done' items are indeed done and ready for sharing w/ stakeholders
Definition of Ready (DOR)DOR Brownbag session held
Team and PO create and agree on DOR at onset
DOR reviewed and revised during each Sprint Retrospective
DOR is known to each member and visible on wall in area
Ready' items are indeed ready to go into sprint w/o further discussion
Product Backlog (PB)Backlog is visible to all
PB maintained by Product Owner
Items on backlog are prioritised, most valuable first
Backlog refined continuously
Backlog reprioritised continuously
Implementation of items on backlog achieves product vision
MetricsBurndown Brown bag session held
Burndown Updated Daily
Burndown Visible at all time
Velocity discussed with team after each sprint
Historic velocity used for next sprint planning
Burnup metric updated after each sprint
Estimation (Poker)Estimation Brown Bag session held
User Story estimation complete prior to sprint planning
Product Owner explains story and answers questions from team
Backlog items meet Definition of Ready and are estimated using planning poker
The whole scrum team partakes and commits to the result
Estimation in place using Mandays
Estimation in place using Story Points
Sprint ReviewSprint Review Brown Bag session held
Held at the end of each sprint, after last stand-up, before retrospective
Inspect the increment - Demo Given to stakeholders in each review
Entire Scrum Team partakes in session
Individual team members demonstrate 'done' stories
Team commit to recommended Sprint Review times
Presentation is informal and direct feedback is encouraged
Group collaborate on what can be done next to maximize value
Changes to scope are welcomed and prioritized by Product Owner
Sprint RetrospectiveSprint Retrospective brown bag held
Retrospective held after each sprint
Each Scrum team member participants adding to Well, Badly, Improve
Previously agreed upon retro points are discussed, closed, and updated
Team commit to time as per recommended retrospective times
Improvement Items are formalised and added to the team backlog (<3 items)
DOR and DOD are updated/improved
Sprint PlanningEach item reviewed against DOR
Entire Dev Team partakes
Held before each Sprint, before first stand-up
Team agree Sprint Backlog
Sprint Vision in place and visible at all times
Each story is broken down into tasks (<4hrs each)
Scrumboard is setup ands reflects planning
Working AgreementAgreed before first Sprint
Visible to all at all times
Reviewed in Retrospective after each sprint
User Stories / Product Backlog Items (PBIs)USer Story brown bag held
Stories are created by Product Owner with help from stakeholders
Each Card shows Who, What, and Why
Each card shows the estimate
Stories follow INVEST (Independent, Negotiable, Valuable, Estimatable, Small, Testable)
Each story can be completed in <1 sprint
Story Splitting workshop regularly held
Acceptance criteria2-4 Acceptance Criteria on each user story
Visualisation - ScrumboardVisible to all
Scrumboard updated continuously by team members
Reflects current status at all times
ValueProduct Owner has defined Value
Measurement for Value in place
Product Owner (PO)Product Owner trained on Product Ownership Fundamentals
Single dedicated Product Owner per team
Product Owner prepares and continuously refines product backlog
Product Owner is mandated to make decisions regardless of existing reporting structures
The team is confident in the Product Owner's ability to identify Value Add opportunites
Scrum Master (SM)Scrum Master is trained in Scrum Master fundamentals
Scrum Master owns and maintains team ceremonies and artifacts
Dedicated to the team
Protects the team from outside influences and removes impediments
Focused on developing the team to become more effective
Scrum Master is focused on the process NOT content
MindsetTeam ceremonies continue in absense of the Scrum Master
Backlog items that are not 'Ready' are not added to sprint backlog
The team proposes improvements and solutions to impedements outside the team
Team members keep each other responsible for their work
The team determines 'how' they implement a story
Team outcomes are only validated against stories and DOD
The organization only judges the team by its outcomes
Management facilitates and supports the team, does not issue directives
Team CommitmentThe whole scrum team pledge to follow the rules
Team working agreement in place
Coaching working agreement in place
Team CelebratonTeam are celebrating Success
Brown Bag CommitmentTeam commit to 45 mins per day for brown bag sessions with coach

 

Contact Now For A Free Consultation