Skip to content
ScrumMastered logo
  • Corporate clients
    • Private Agile & Scrum Training
    • Agile Consulting
    • Case Studies
  • Courses
    • Upcoming live public classes
    • Jira for Scrum Masters
    • Scrum Master (PSM I™) Exam Prep Certification Course
    • Fundamentals of Agile Course
  • Resources
    • Wiki
    • Start here
    • Freebies
    • The Agile Audit Podcast
    • Premium Downloads & Courses
  • Blog
  • About
  • Corporate clients
    • Private Agile & Scrum Training
    • Agile Consulting
    • Case Studies
  • Courses
    • Upcoming live public classes
    • Jira for Scrum Masters
    • Scrum Master (PSM I™) Exam Prep Certification Course
    • Fundamentals of Agile Course
  • Resources
    • Wiki
    • Start here
    • Freebies
    • The Agile Audit Podcast
    • Premium Downloads & Courses
  • Blog
  • About
Shop

Scrum Framework Explained

  • Scrum Overview
  • Sprint Events
    • Sprint Retrospective
    • Sprint Review
    • Daily Scrum
    • Sprint Planning
  • Scrum Accountabilities / Roles
    • Scrum Master
    • Developers
    • Product Owner
  • Scrum Artifacts & Commitments
    • Sprint Goal
    • Sprint Backlog
    • Product Goal
    • Product Backlog
    • Definition of Done
    • Increment
  • Scrum Values
    • Value: Courage
    • Value: Respect
    • Value: Openness
    • Value: Focus
    • Value: Commitment
  • Pillars of Empiricism
    • Pillar: Adaptation
    • Pillar: Inspection
    • Pillar: Transparency

Useful Models

  • Use Kano Model to prioritize features
  • Psychological safety
  • Team Overestimating Their Knowledge – The Dunning-Kruger Effect
  • Cognitive Bias in Business
  • Shu-Ha-Ri Maturity Model
  • Tuckman’s Stages of Group Development
View Categories
  • Home
  • wiki
  • Scrum Framework Explained
  • Scrum Overview

Scrum Overview

3 min read

In this wiki space, you’ll find the key information about what it is and how it is used in engineering teams.

What is Scrum? #

Scrum is a product development framework that helps teams become more Agile.

Agile is defined in the Agile Manifesto. The Scrum framework is defined in the Scrum Guide.

In essence, Scrum defines a process of work the team should follow, the accountabilities to be fulfilled as well as working agreements between team members.

Key Scrum Elements #

Scrum defines several key elements that make the framework what it is. You can review each in more detail on a dedicated page in this wiki.

Sprint Events #

  • Sprint Planning
  • Daily Scrum
  • Sprint Review
  • Sprint Retrospective

Scrum Accountabilities #

  • Product Owner
  • Developers
  • Scrum Master

Scrum Artifacts #

  • Increment
  • Product Backlog
  • Sprint Backlog

Other #

  • Backlog Refinement

Overview of a Sprint #

Here’s a simple image showing how a regular Sprint would be run. Read the explanation of the process below as you review the image.

Scrum Framework Overview S - ScrumMastered 2025

In Scrum, the Scrum team works in Sprints that are shorter than 1 month. Very popular Sprint length is 2 weeks.

  1. It starts with a demand coming from stakeholders and customers to build a product. And so the team begins their work.
  2. The Product Owner collects information about customers’ needs and wants and decides on the next steps. This usually starts with defining a Product Goal. All the work to be done in the Product is documented in the Product Backlog.
  3. The team starts their Sprint.
  4. At the beginning of the Sprint, the team plans their work for the Sprint in a Sprint Planning. They follow the guidance given by the Product Owner on what they should work on. This is done with the help of a Sprint Goal that is initially defined by the Product Owner and then discussed and adjusted with the team if needed.
  5. The team pulls the work from the Product Backlog into their Sprint Backlog guided by the Sprint Goal. They discuss what exactly needs to be done and decide how much work is reasonable.
  6. The work starts. Every working day Developers meet for 15 minutes in a Daily Scrum to discuss their progress and plan their work for the day.
  7. The team continuously refines its Product Backlog as more is discovered about the Product and customers’ and stakeholders’ needs.
  8. At the end of the Sprint, the work that has been completed is added to the product Increment that can be presented to the stakeholders at the Sprint Review. Completed work must meet the Definition of Done – a checklist defining the minimum acceptable quality. The goal of Sprint Review is to get stakeholders’ feedback, discuss potential completion dates, and adjust the team’s plan for the next Sprint.
  9. The Sprint ends with a Sprint Retrospective where the whole team discusses how to make their work more productive, enjoyable, and organized while also upholding the standards of Product quality.
  10. This ends the Sprint and the next Sprint can start right away going over the same steps. The whole flow is facilitated by the Scrum Master who helps the Team to organize themselves and plan better.
Was this helpful?
Share This Article :
  • X
  • LinkedIn
Updated on April 4, 2024

Powered by BetterDocs

Table of Contents
  • What is Scrum?
  • Key Scrum Elements
    • Sprint Events
    • Scrum Accountabilities
    • Scrum Artifacts
    • Other
  • Overview of a Sprint

Join 5000+ Agile practitioners around the world on their journey to building awesome teams.

ScrumMastered logo
Quick Links
  • Shop
  • Agile Consulting
  • Private Training
  • Scrum.org Classes
  • Blog
  • About & Contact
  • Terms & Conditions
  • Privacy Policy
Follow for More

All Rights Reserved by ScrumMastered © 2025