The Scrum Framework – A Method for Agile Work


Scrum is an agile framework that helps teams structure their work into short development cycles called sprints, emphasizing collaboration, flexibility, and continuous improvement. It provides a lightweight structure for complex product development, enabling teams to deliver high-quality products efficiently.


The approach is used in project-based work to increase productivity, improve quality, and respond quickly to changes. Scrum can be applied to various industries including software development, marketing, research, and product development.


The Scrum framework is built on empiricism and lean thinking, and is designed to help teams deliver value in complex, unpredictable environments. Scrum teams consist of self-organizing, cross-functional teams that practice continuous improvement through regular inspection and adaptation. Key elements include: Roles:
  1. Scrum Master: Facilitates the Scrum process, removes impediments, and coaches the team.
  2. Product Owner: Represents stakeholders, manages the product backlog, and maximizes product value.
  3. Development Team: Cross-functional group responsible for delivering potentially shippable increments.
  1. Product Backlog: Prioritized list of features, requirements, and improvements.
  2. Sprint Backlog: Set of items selected for the current sprint, plus a plan for delivering them.
  3. Increment: Sum of all completed Product Backlog items during a sprint, meeting the Definition of Done.
  1. Sprint Planning: Team plans the work to be performed in the sprint (up to 8 hours for a one-month sprint).
  2. Daily Scrum: 15-minute time-boxed event for the team to synchronize activities and create a plan for the next 24 hours.
  3. Sprint Review: Informal meeting at the end of the sprint to inspect the increment and adapt the Product Backlog (up to 4 hours for a one-month sprint).
  4. Sprint Retrospective: Opportunity for the team to inspect itself and create a plan for improvements (up to 3 hours for a one-month sprint).
Time-boxed iterations (Sprints): Usually 1-4 weeks long, consistent throughout a development effort. Scrum emphasizes transparency, inspection, and adaptation. It helps teams focus on delivering working products incrementally, allowing for frequent feedback and adjustments. The framework promotes self-organization, accountability, and iterative progress toward well-defined goals.

Sample Activity

A sample scrum process may unfold as follows: Conduct a Sprint Planning meeting
  • Review and refine the Product Backlog
  • Select items for the Sprint Backlog
  • Create a Sprint Goal
  • Estimate effort for selected items
Hold Daily Scrum meetings
  • Each team member answers: What did I do yesterday? What will I do today? Are there any impediments?
  • Update Sprint Burndown Chart
Perform Sprint Review
  • Demonstrate the completed work to stakeholders
  • Gather feedback and update Product Backlog accordingly
Conduct Sprint Retrospective
  • Discuss what went well, what could be improved, and create action items
  • Identify and agree on continuous improvement actions
Backlog Refinement (ongoing)
  • Product Owner and Development Team collaborate to refine and prioritize backlog items


Jeff Sutherland is one of the creators of Scrum together with Ken Schwaber. Sutherland contributed to the creation of the Agile Manifesto in 2001.

Target Audience:

  • Project Managers
  • Quality Assurance Teams
  • Operations Teams
  • Marketing Teams
  • Research and Development Teams
  • Any team working on complex projects with changing requirements

Got feedback or input? Please share!