The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules. Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage. The rules of Scrum bind together the roles, events, and artifacts, governing the relationships and interaction between them as shown in the Figure below:

Best Scrum Software Every Project Needs
A powerful scrum software that supports scrum project management. It features scrum tools like user story map, product backlog management, sprint backlog management, task management, daily scrum meeting, sprint planning tool, sprint review tool, sprint retrospective tool, burndown, impediment, stakeholder and team management.
Basic Scrum Rules
The main aim of Scrum rules is to optimize the development process and minimize time wasted. Here is a list of Basic Rules in Scrum:
- Every Sprint is Four Weeks or Less in Duration
- There are no Breaks Between Sprints
- Every Sprint is the Same Length
- The Intention of Every Sprint is “Potentially Shippable” Software
- Every Sprint includes Sprint Planning
- The Sprint Planning Meeting is Time boxed to 2 Hours / Week of Sprint Length
- The Daily Scrum occurs every day at the same time of day
- The Daily Scrum is time boxed to 15 minutes
- Every Sprint includes Sprint Review for stakeholder feedback on the product
- Every Sprint includes Sprint Retrospective for the team to inspect and adapt
- Review and Retrospective meetings are time boxed in total to 2 hours / week of Sprint length
- There is no break between Sprint Review and Retrospective meetings
The Scrum Master is responsible for ensuring that everyone follows the rules of Scrum related to a project. These rules hold the Scrum process together so that everyone knows how to play.
About Visual Paradigm |
![]() Manage the Entire Scrum Process in One Page
|