The 20 most frequently mentioned rules and guidelines in Scrum

The primary goal of Scrum rules is to optimize the development process and reduce wasted time.

Here is a list of the basic rules of Scrum:

1. The Development Team is suggested to be 3–9 members
2. The Development Team is Cross-functional and self-organized
3. Every Sprint is Four Weeks or Less in Duration
4. There are no Breaks Between Sprints
5. Every Sprint have consistent duration
6. Time-box for all Scrum events
7. Product Owner is one person, not a committee.
8. Once a Sprint begins, its duration is fixed — don’t stretch sprint time or cut sprint time
9. The Intention of Every Sprint is “Potentially Shippable” Software
10. Every Sprint includes Sprint Planning
11. The Sprint Planning Meeting is Time boxed to 2 Hours / Week of Sprint Length
12. The Daily Scrum occurs every day at the same time of day
13. The Daily Scrum is time boxed to 15 minutes
14. Every Sprint includes Sprint Review for stakeholder feedback on the product
15. Every Sprint includes Sprint Retrospective for the team to inspect and adapt
16. Review and Retrospective meetings are time boxed in total to 2 hours / week of Sprint length
17. There is no break between Sprint Review and Retrospective meetings
18. The Product Backlog is the single source of requirements
19. The Intention of Every Sprint is potential shippable product
20. A new Sprint starts immediately after the conclusion of the previous Sprint.

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: