An overview of the Agile Scrum framework
Agile Scrum is a lightweight framework designed specifically for keeping complex product development and project management on track. Primarily used for Agile product development, but applicable to any activity requiring teamwork, the Scrum framework guides cross-functional teams to communicate, hold each other accountable, and iterate quickly and consistently to deliver results.
Like a rugby team (where Scrum gets its name) trying to take possession of the ball, Scrum encourages teams to work together and learn from their experiences to improve. It's not a prescriptive method, but rather a set of principles and well-defined roles that help teams manage their work.
The Agile Scrum framework is structured around roles, ceremonies, and artifacts.
Use this template to introduce Scrum to your team with a collaborative group activity.
The Scrum leader, also called the Scrum master, is the glue that holds the team together. A Scrum leader's main job is to facilitate Scrum ceremonies and nurture an environment where the team embodies Agile principles and collaborates efficiently.
The product owner looks over the product backlog, defines user stories, and orders the work to be done. They act as an advocate for the customer,
The Scrum Development team then turns part of that work into an increment of value (or goal) during a sprint planning session (e.g., in two weeks, we will complete the build out of the onboarding application). The Scrum team and its stakeholders then analyze the results and make any adjustments for the next sprint — and then repeat.
While the term might sound a bit intimidating, Scrum ceremonies are relatively straightforward. Think of them as meetings designed to align the Scrum team and empower them to be more effective with each increment.
The daily scrum, also called the daily standup, is a 15-minute meeting that keeps the Development team aligned. Facilitated by the Scrum leader, this ceremony asks team members to succinctly answer three questions:
Sprint planning happens at the beginning of each sprint — typically, every two weeks.
The sprint review happens at the end of each sprint with the purpose of aligning key stakeholders outside of the Scrum team and getting their feedback on the deliverables from the sprint.
While the sprint review focuses on the increment itself, retrospectives are a time for the Development team to reflect on the sprint process. Retros allow teams to identify what went well, what didn't, and what actions they can take to improve over the course of the next sprint.
Use these templates to plan, facilitate, and follow up after your Scrum ceremonies and meetings. More templates coming soon.
These three artifacts are the foundation of a successful sprint. They allow Scrum teams to align on their shared priorities and work quickly toward achieving the product goal.
A product backlog is an always-evolving list of the requirements, features, enhancements, and fixes for a given product. Each item is represented by a user story and prioritized in order of importance. The product backlog is managed by the product owner.
A sprint backlog is a subset of the product backlog that outlines the stories that a Scrum team is prioritizing during a sprint.
In Scrum, the increment is the output of a sprint. By definition, Agile is an incremental approach to product development — so it makes sense that each increment builds upon the previous ones.
Scrum teams use Mural to map out sprints, plan individualized goals, and help team members visualize the big picture. Learn more.