Framework 202 Scrum (part of Agile)
Introduction
Scrum is a variation of the agile framework and is used to deliver complex products through iterative, incremental cycles.
It emphasises transparency, collaboration, quick feedback and the ability to adapt rapidly.
Scrum is built on three pillars:
- Transparency
- Inspection
- Adaptation
It operates in time-boxed cycles called Sprints, of usually 1–4 weeks.
1. Scrum Roles
Scrum defines 3 accountability-focused roles (not job titles):
1.1 Product Owner
- Represents the customer/stakeholders.
- Owns the Product Vision.
- Manages and prioritises the Product Backlog.
- Ensures the team works on the most valuable items.
- Makes decisions and accepts completed work.
In change management: this is similar to a change sponsor: setting direction, priorities, and ensuring alignment with strategic goals.
1.2 Scrum Master
- Facilitates scrum adoption and maturity.
- Removes impediments.
- Coaches the team in agile practices.
- Shields the team from distractions.
- Ensures Scrum events happen and add value.
In change management, this is similar to a change facilitator removing barriers, coaching behaviours, improving processes and communication.
1.3 Developers (Scrum Team Members)
- Cross-functional team delivering increments of value.
- Self-managing: decide how to do the work.
- Responsible for the Increment of each Sprint.
In change management, this is similar to change agents or implementation teams doing the actual work with end users.
2. Scrum Artefacts
2.1. Product Backlog
- A prioritised list of everything needed to build the product.
- Contains features, enhancements, fixes, technical work, knowledge items, etc.
- Continuously refined.
Change management equivalent: Change backlog (e.g., tasks, communication actions, process redesign items).
3. Sprint Backlog
- The set of Product Backlog items the team commits to deliver in the current Sprint.
- Includes a Sprint Goal and the plan for achieving it.
Change equivalent: Items required to achieve a short-term change milestone (e.g., training development, stakeholder meetings).
Increment
- The usable, potentially releasable piece of the product delivered during each Sprint.
- Must meet the Definition of Done.
Change equivalent: Tangible progress step (e.g., completed training module, process prototype, pilot test results).
(main source: Madel, Monika et al, 2021)