Scrum, a lightweight framework for complex problems
Scrum is a lightweight framework that helps people, teams, and organizations generate value through adaptive solutions for complex problems. It is not an exhaustive methodology prescribing every step of the work, but a minimal framework made up of roles, events, artifacts, and the rules that bind them together.
Created in the early 1990s by Ken Schwaber and Jeff Sutherland, Scrum is grounded in empirical process control theory, or empiricism. Empiricism asserts that knowledge comes from experience and that decisions should be based on what is observed, rather than on detailed upfront planning.
In practice, a Scrum Team works in short iterations called Sprints, typically lasting one month or less, during which it builds a potentially releasable product Increment. At the end of every Sprint, the team inspects the outcome achieved and adapts its plan for the next Sprint.
The three pillars of empiricism: transparency, inspection, and adaptation
The empiricism underlying Scrum rests on three pillars. Transparency means the work and the process must be visible to those responsible for it, as well as to those receiving the work. Inspection means frequently examining Scrum artifacts and progress toward a goal to detect undesirable variances. Adaptation happens when one or more aspects of a process deviate outside acceptable limits, requiring an adjustment as soon as possible.
These three pillars only work if they are supported by the five Scrum values: commitment, focus, openness, respect, and courage. Without these values, Scrum's events and artifacts can become empty rituals, applied mechanically without real benefit.
The three roles of the Scrum Team
A Scrum Team consists of three distinct roles, with no hierarchy between them: the Product Owner, the Scrum Master, and the Developers. The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team, notably by managing the Product Backlog. Developers are the people in the Scrum Team committed to creating any aspect of a usable increment each Sprint. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping everyone understand Scrum theory and practice.
These three roles form a cohesive unit, now simply called the 'Scrum Team', self-managing and cross-functional. The Scrum Team decides who does what, when, and how, without depending on authority outside the team for these decisions.
Scrum events: the team's regular rhythm
Scrum defines five events: the Sprint itself, which is a container for all the others, Sprint Planning which kicks off the Sprint by defining what can be delivered, the Daily Scrum where Developers inspect their daily progress, the Sprint Review where the Increment is presented to stakeholders to gather feedback, and the Sprint Retrospective where the team reflects on its own effectiveness to improve in the next Sprint.
Each of these events is a formal opportunity to inspect and adapt Scrum artifacts: they are never optional and occur at a regular cadence, which reduces the need for meetings not defined within Scrum.
Scrum artifacts and their commitments
Scrum defines three artifacts: the Product Backlog, an emergent, ordered list of what is needed to improve the product, committed to via the Product Goal; the Sprint Backlog, composed of the Sprint Goal, the set of Product Backlog items selected for the Sprint, and a plan for delivering them, committed to via the Sprint Goal; and the Increment, the concrete, functional addition produced during the Sprint, committed to via the Definition of Done.
Each artifact contains a commitment that reinforces transparency and focus toward the measurable goals pursued by the Scrum Team. These commitments allow the team and stakeholders to track progress reliably, without ambiguity about what has actually been accomplished.
Why get PSM I certified after understanding Scrum?
Understanding Scrum theory is an essential first step, but applying it correctly day to day requires practice and a solid grasp of common pitfalls. The Professional Scrum Master™ I (PSM I) certification from Scrum.org validates this foundational understanding through a rigorous exam, recognized internationally by recruiters and companies.
Earning this first level of certification is often the first step in a professional journey into agility, whether you're aiming for a Scrum Master role, an agile coaching career, or simply better collaboration within a product team.