
Backlog Refinement
Getting on top of your Product Backlog is a key element of improved agility
The Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts. These events are specifically designed to enable the transparency required.
Failure to run any of these events results in lost opportunities to inspect and adapt. Events are used in Scrum to create regularity and to minimise the need for meetings not defined in Scrum.
The state of the Sprint's goal and progress toward it less clear. Does it truly reflect where delivery is at?
If daily plans are not assessed, opportunities to adapt to change in the environment are lost.
Opportunities are lost to deliver smarter, faster, if not assessed on a daily basis.
Optimally, all events are held at the same time and place to reduce complexity.
The Facilitation Guides for Scrum’s 5 events, and Backlog Refinement, cover the essential working sessions to strengthen empiricism through regular and consistent inspection and adaptation.
Getting on top of your Product Backlog is a key element of improved agility
Understanding complexity helps attack problems with the best approach
Inspecting progress toward the Sprint Goal empowers a team to adapt its Sprint Backlog
Inspecting progress toward the Sprint Goal empowers a team to adapt its Sprint Backlog
Inspect the team – people, process and tools – and decide on improvement actions
How does a team decide on what items will become part of their Sprint?
How does a team decide on what items will become part of their Sprint?
How does a Product Owner facilitate discussion on the value needed from the upcoming Sprint?
What are the essential parts of Sprint Planning and how do you make it effective?
Go beyond a demo and inspect the increment to get feedback on the direction for the next Sprint
Sprints are the heartbeat of Scrum, where ideas are turned into value.
The principles of the Agile Manifesto provide a guide for behaviour and action.
A Retrospective activity to help improve people’s awareness of the Agile Manifesto
Assess capacity each Sprint to understand what the load is on the team versus how much it can typically deliver in a given Sprint
The Sprint Goal is an objective to be met by the Sprint through the implementation of part of the Product Backlog.
Curated practices on facilitation best practice by certified Professional Scrum Trainers
Teams’ agility improves when the Scrum Master supports self-organisation with these simple phrases and facilitation patterns
The “What Worked”, “What Didn’t” gets boring quickly. Learn how to mix things up in Retrospectives to keep them fresh.
The Definition of Done is a vital part of Sprint Planning, indicating the quality, standards, and compliance criteria for an Increment of Done
Liberating Structures are easy-to-learn microstructures that enhance relational coordination and trust.
Learn how to get the most out of inspecting and adapting using Scrum’s 5 key events.
When quality slips, defects and rework increases, it’s important to look at the Definition of Done in the Retrospective.
A pattern to support experimentation and research as part of Backlog Refinement
Optimise flow of work through upgrading the team’s visual board to Kanban
Get the most out of the latest version of the IT service management (ITSM) and agile frameworks