The 6 Core Principles of Scrum Explained

Scrum's Fundamental Principles

Scrum is based on six core principles that make it the most common, successfully implemented framework.

These six principles describe how Scrum works day to day. The framework itself is defined by the Scrum Guide, last revised in November 2020, which sets out three accountabilities, five events, and three artifacts. That revision also updated the wording behind Principle 1: it calls Scrum Teams self-managing rather than self-organizing, rules out sub-teams and hierarchies inside a Scrum Team, and sizes the team at typically 10 or fewer people.

The six-principle framing is worth placing correctly, because the Scrum Guide itself never uses it. The six principles come from A Guide to the Scrum Body of Knowledge, the SBOK Guide published by SCRUMstudy, which names them as empirical process control, self-organization, collaboration, value-based prioritization, time-boxing, and iterative development. The Scrum Guide instead rests on the three pillars of transparency, inspection, and adaptation and the five values of commitment, courage, focus, openness, and respect. The two sets do not conflict. The pillars describe how Scrum learns, the values describe how the team behaves, and the six sections below describe the same practices in plainer wording.

Principle 1: Self-organized & Cross-functional teams

The Scrum Guide describes Scrum Teams as cross-functional, meaning the members hold every skill needed to create value in a Sprint, and self-managing, meaning they decide internally who does what, when, and how. The November 2020 revision replaced the older term self-organizing with self-managing. These two factors are crucial in an Agile setting because they serve as the foundation for a successful team that can:

• Work as a team without being directed by outside stakeholders.
• Have all the necessary knowledge, skills, and means to achieve their objectives.
• Handle difficult tasks with harmony, flexibility, and innovation.

Principle 2: Empirical process control

Scrum employs empirical process control, which is based on a project's real-world progress rather than estimates or long-term forecasts utilized in traditional techniques. Project decisions are decided based on observations and experiments rather than comprehensive advance planning when employing empirical process control. This principle is supported by three pillars:

Pillar 1: Adaptation

This is the final step in empirical process control. It occurs as a result of the organization's learning through continual improvement. Scrum does this through retrospectives, continuous risk assessments, and detailed change requests.

Pillar 2: Transparency

Allows stakeholders to see the project details without making any assumptions. This encourages the flow of information throughout the business and fosters an open culture in which all work activities are visible to anyone. Scrum enables this through many methodologies such as prioritized product backlogs, burndown charts, daily meetings, and so on.

Pillar 3: Inspection

Within the Scrum framework this is achieved by:

• Specific agile metrics that would provide crucial data about the project's overall progress (e.g., quality KPIs, team velocity).
• Ongoing feedback loops from customers and other stakeholders across development cycles.
• The Product Owner reviews and approves team outputs.

Principle 3: Constant feedback

The Scum Framework relies heavily on the continuous feedback process. Because there is less upfront planning to lead the team throughout the Agile SDLC, this is the case. Instead, the team relies on continuous input to comprehend and adapt to developments while keeping the project on schedule. The framework provides an excellent platform for enabling continuous feedback loops using events (review, retrospective, etc.) and artifacts (product and Sprint backlogs, burn-down charts, etc.).

• Sprint review: During this meeting, the team shares sprint outcomes and receives feedback on the quality of the work from the PO or client. This feedback is then converted into new product backlog items that will aid in the development of a quality product.
• Sprint burn-down chart: The release burn-down chart gives useful information about the remaining and completed work at any given time.

Principle 4: Iterative approach for delivering rapid releases

Teams should employ development sprints that run between a week and a month, according to the methodology. Each Sprint is divided into four phases by a Scrum team. These are as follows:

Phase 1: Sprint kick-off

Every Sprint starts with a planning meeting that includes the whole Scrum team (Developers, SM and PO). The following are the meeting's outcomes:

• A sprint backlog with a list of prioritized stories.
• Created a task list for each tale to guide development activities.
• A clear statement of the Sprint objective.

Phase 2: Sprint Execution

By researching, developing, and testing, the team works as a cohesive unit to fulfill the stories they committed to completing. These are required in practically every story. Using these activities, the team can guarantee that each story meets the Definition of Done (DoD) and that the sprint objective set at the start of the sprint is met.

Phase 3: Ongoing feedback based on sprint outcomes

The team shows the possibly shippable product increment to the key stakeholders at the end of each sprint (Product Owner, customer etc.). They will receive comments and approval for the excellence of their work. This feedback will be incorporated into the upcoming sprints.

Phase 4: Ongoing improvement

Finally, the team holds a retrospective meeting. They review how things went, adjustments needed in future sprints, and the primary constraints keeping them from flourishing at this discussion.

Principle 5: Consistent customer value through prioritization

Scrum, as an Agile model, places the client at the center of the process. As a result, throughout the project, Scrum teams should present deliverables to the customer at the end of each development sprint. The deliverables must be based on backlog prioritizing of customer requirements (directed by the Product Owner). This allows the team to provide the most value to the consumer.

The November 2020 Scrum Guide attached a commitment to each artifact, and the one that governs prioritization is the Product Goal. The Product Goal describes a future state of the product and gives the Product Backlog a single target to order against, while the Sprint Backlog carries the Sprint Goal and the Increment carries the Definition of Done. The Product Owner therefore orders the backlog by what moves the product toward the Product Goal, not by which request arrived last.

Principle 6: Timeboxing to increase predictability

Because Agile projects require little forward preparation, they are more adaptable to changes but less predictable. To attain high productivity, the project must follow a consistent schedule with short repeatable time-boxes.

A "time-box" is an agreed-upon and limited time period in which a person or team performs a specific function. They work to complete a goal within the time frame that has been agreed upon and defined. If the time limit expires without completing all the needed activities, the decision on how to proceed is based on the time-box approach (soft vs hard).

Consider an Agile project with 100 units of effort that the team must complete. Every two weeks, the team completes five units (The time-box of the sprint). Knowing these fundamental elements allows the organization to forecast project completion using a simple calculation of time boxing/velocity = twenty Sprints.

What is the distinction between "soft" and "hard" timeboxing?

There are two techniques to dealing with unfinished work at the end of a time limit.

• Soft time-boxing: When the time allotted expires, the SM decides whether to continue and allots the time for it.
• Hard time constraints: once the time limit is reached, there is no space for debate, and the team must stop working regardless of the danger to the remaining work.