Scrum Framework Basics
Where Scrum came from, what it actually is, and the principles underneath it that make it work.
A Short History
Scrum emerged in the early 1990s as software teams looked for an alternative to rigid, plan-driven processes. In 2001, the Agile Manifesto put a shared philosophy behind these approaches, and in 2010 the first version of the official Scrum Guide was published — a short, free document that defines the framework as it's used today.
Scrum is deliberately small. The entire ruleset fits on a few pages. Everything else — engineering practices, tools, org charts — is up to the team to figure out, guided by experience.
What Scrum Actually Says
"Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value."
Strip away the terminology, and Scrum boils down to four simple rules that repeat in a loop:
The Product Owner orders the Product Backlog by value.
The team turns a selection of that backlog into a usable Increment during the Sprint.
The team and stakeholders inspect the result and adapt the plan.
Repeat — every Sprint.
The Three Pillars of Empiricism
Scrum is built on empirical process control and lean thinking — decisions are based on observation and experience, not up-front prediction. That rests on three pillars:
Transparency
Significant aspects of the process must be visible to everyone responsible for the outcome — using a common language so everyone shares the same understanding.
Inspection
Scrum artefacts and progress toward the goal must be inspected frequently and diligently, to detect undesirable variances or problems early.
Adaptation
If something deviates outside acceptable limits, it must be adjusted as soon as possible — the process, the product, or the team itself.
The Five Scrum Values
When a team internalizes these, the pillars above come to life.
Commitment
Individuals personally commit to achieving the team's goals.
Focus
Everyone focuses on the work of the Sprint and the goals of the team.
Openness
The team and stakeholders agree to be open about all the work and challenges.
Respect
Team members respect each other to be capable, independent people.
Courage
The team has the courage to do the right thing and tackle tough problems.
The Agile Manifesto
Published in 2001, these four value statements sit behind Scrum and every other agile framework. They're about priorities, not absolutes — the items on the right still matter, just less than the items on the left.
The 12 Principles of Agile
The Manifesto's four values are backed by twelve more concrete principles.
Highest priority: satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development.
Deliver working software frequently — every few weeks rather than months.
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need.
The most efficient way to convey information is face-to-face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development — a pace the team can maintain indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity — the art of maximizing the amount of work not done — is essential.
The best architectures, requirements and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes its behavior.