Three (3) Pillars
The three pillars of the Scrum methodology are:
- Transparency – Visibility to all is what’s important, especially regarding the definition of done.
- Inspection – Frequent checks need to take place – not just testing at the end of any timeframe.
- Adaptation – Adapt based on what you’re learning instead of following a plan.
Five (5) Fundamental Values
The following are the fundamental values of scrum, with no explanation required.
The key component of scrum is that it employs a time boxed cadence – the sprint cycle – that sets the framework for all other activity.
Three (3) Scrum Team Roles
The three primary scrum team roles are:
- Development Team – The team builds the product increments each sprint, and is self-organizing – empowered to manage its own work. Team members are expected to be a cross-functional and interchangeable with each other as possible.
- Product Owner – Representing the business, the Product Owner manages the product backlog, or list of work to be done, sets development priorities, and ensures transparency across team and stakeholders.
Six (6) Scrum Activities/Events/Activities
- Backlog refinement – This meeting entails updating the backlog.
- Sprint planning meeting – This meeting is for reviewing the backlog, ensuring common understanding, and the development team setting sprint goals for developing backlog items.
- Daily scrum – This is a short morning standup meeting of the team where members only state what they have most recently accomplished, what they will do today, and what blockers they might have for accomplishing their agenda.
- Scrum of scrums – This is a meeting of representatives from each scrum team to coordinate dependencies across the teams. The same questions as in the daily scrum apply, plus mention of any cross-team blockers.
- Sprint review – This is where the team showcase its accomplishments at the end of the sprint, ideally as a demo. The Product Owner reviews, and adjustments are made to the backlog and plans for the next action.
- Sprint retrospective – This is a final review of the sprint by the development team to consider what worked well, what worked not so well, and what adjustments that can be made to improve in the next sprint.
Three (3) Scrum Artifacts
- Product Increment – This is the delivered working software, or demo of software to be included in the next increment.
- Product Backlog – This s the prioritized list of the work that needs to be done to produce the product at the end of the project.
- Sprint Backlog – This is the subset of the product backlog that will be developed in the current sprint.
Scrum is the most popular of agile methods, and is sometimes consumed with agile itself. However, it is its own method, but it often is customized in some way to accommodate needs of specific project situations. It can easily be combined with some other methods, such as Extreme Programming (XP), Lean, and Kanban. It is also the foundation of other more specific agile methods, such as the Scaled Agile Framework (SAFe).
This post is part of the series: A Look at Agile Methods
- Agile Method #1: Scrum
- Agile Method #2: Extreme Programming (XP)
- Agile Method #3: Lean Product Development
- Agile Method #4: Kanban