Scrum
Scrum is a specific way of practicing Agile.
It organises work into short, fixed-length cycles called sprints, usually two weeks long. A small team works together with defined roles — a Product Owner who decides what to build, a Scrum Master who helps the process run smoothly, and the Development Team who does the work. Regular meetings keep everyone aligned and help the team continuously improve.
Scrum, explained at three levels
At home
Scrum is a teamwork method where people work in short bursts, usually two weeks, called sprints. At the start of each sprint, the team picks tasks from a prioritised list. They meet briefly each day to check progress. At the end, they show what they built and discuss what went well and what to improve. Then the cycle repeats.
At work
In business, Scrum provides a structured framework for teams to deliver work incrementally. The Product Owner maintains a prioritised backlog of work items, the team selects what they can complete in the sprint, and the Scrum Master removes obstacles. Sprint reviews let stakeholders see progress, and retrospectives drive continuous improvement. This predictable cadence builds trust and transparency.
At home
Scrum has specific events built into each sprint. Sprint Planning sets the work for the sprint. Daily Scrum (or standup) is a fifteen-minute check-in where team members share progress and blockers. Sprint Review demonstrates completed work to stakeholders. Sprint Retrospective is where the team reflects on their process and agrees on improvements for the next sprint.
At work
Professional Scrum practice involves maintaining a well-refined product backlog with clearly estimated items, tracking sprint velocity to forecast delivery timelines, and using burndown charts to monitor progress within a sprint. The Product Owner role requires strong stakeholder management, while the Scrum Master coaches the team in Agile practices and shields them from outside disruptions.
At home
Effective Scrum implementation requires understanding its underlying principles, not just its mechanics. True self-organisation means the team decides how to do the work, not just what to do. Sprint goals provide focus beyond a list of tasks. Definition of Done establishes quality standards. Scaling Scrum across multiple teams introduces coordination challenges that frameworks like Nexus and LeSS address.
At work
Advanced Scrum practice involves sophisticated backlog management with user story mapping, evidence-based management metrics (current value, time-to-market, ability to innovate, unrealised value), and organisational impediment removal that addresses systemic issues beyond a single team. Technical practices like continuous integration, test-driven development, and pair programming are essential complements to Scrum's process framework. At scale, cross-team refinement, integration sprints, and shared Definition of Done ensure coherent multi-team delivery.
Real-world examples
At home
Mei and her housemates use a Scrum-like approach for their home renovation. Every two weeks, they pick the most important tasks from their project list, check in briefly each evening on progress, and at the end of the two weeks, they walk through what they have accomplished and decide what to tackle next.
At work
David's software team uses Scrum to build a mobile banking app. Every two weeks, they deliver a working update — one sprint might add the balance view, the next adds transfers. The product owner adjusts priorities based on customer feedback after each sprint review, ensuring the most valuable features are delivered first.
Common confusions
- Many people assume Scrum and Agile are the same thing. Scrum is one specific framework under the broader Agile umbrella.
- It's often assumed that the Scrum Master is the team's boss. The Scrum Master is a servant-leader who facilitates the process and removes obstacles, not a manager.
- It's a common myth that Scrum means you cannot plan beyond two weeks. Teams maintain a longer-term product backlog and roadmap; sprints just determine the immediate delivery cycle.
For analysts
If your Scrum retrospectives are always positive with no action items, something is wrong. No team is perfect, and retros are where the real improvement happens. Encourage honesty by making it safe to raise problems. And remember — the Product Owner role is critical. A disengaged Product Owner who does not prioritise the backlog or attend sprint reviews will undermine the entire framework, no matter how well the team executes.
History & origin
The term Scrum was borrowed from rugby by Hirotaka Takeuchi and Ikujiro Nonaka in a 1986 Harvard Business Review article about product development. Ken Schwaber and Jeff Sutherland formalised Scrum as a software development framework in the early 1990s, presenting it at the OOPSLA conference in 1995. It became the most widely adopted Agile framework worldwide, with the Scrum Guide serving as its definitive reference.