Scrum
Sprint-based iterative delivery
Scrum is an agile framework for delivering complex products in short, fixed-length iterations called sprints (typically 1–4 weeks). Work is pulled from a prioritised backlog, a cross-functional team self-organises to complete it, and four ceremonies — sprint planning, daily standup, sprint review, and retrospective — create a feedback loop every iteration.
Developed by Ken Schwaber and Jeff Sutherland, formalised in the Scrum Guide (1995, updated 2020).
Use Scrum when
- ✓You have a defined product backlog and a stable cross-functional team
- ✓Requirements evolve but delivery cadence needs to be predictable
- ✓Stakeholders want regular demos and feedback opportunities
- ✓Team size is 3–9 people (Scrum struggles to scale without SAFe or LeSS)
Avoid it when
- ✗Work arrives unpredictably and can't be batched into sprints (use Kanban instead)
- ✗The team is distributed across many time zones with no async culture
- ✗You're doing pure maintenance or support work without discrete features
Key Concepts
A fixed time-box (1–4 weeks) in which a usable increment is delivered.
An ordered list of everything that might be done in the product, maintained by the Product Owner.
The subset of backlog items selected for the current sprint, plus the plan for delivering them.
A single objective for the sprint that gives the team focus and flexibility.
A shared checklist of quality criteria that every increment must meet before it can be called done.
The amount of work a team completes per sprint, used for forecasting not target-setting.
How it works
Team selects backlog items, agrees on a sprint goal, and creates the sprint backlog. Typically 2–4 hours for a 2-week sprint.
15-minute daily sync for the development team. Focus: what did I do yesterday, what will I do today, are there any blockers.
Team demos the increment to stakeholders and collects feedback. Backlog may be updated as a result.
Team reflects on the process — what worked, what didn't, one improvement to try next sprint.
Tools that support Scrum
Industry standard for software development teams — most PMs will encounter Jira in their career
Exceptionally intuitive and visually clean interface — one of the lowest onboarding friction tools for non-technical teams
Highly visual and intuitive interface with color-coded boards — one of the easiest PM tools for non-technical teams to adopt
All-in-one platform replacing multiple tools — docs, whiteboards, goals, time tracking, chat, and project management in a single workspace
Unmatched flexibility as an all-in-one workspace — combines docs, wikis, databases, and project management in a single tool
Spreadsheet-familiar interface makes adoption easy for teams transitioning from Excel — minimal training needed for basic use
Extremely intuitive drag-and-drop Kanban interface — virtually zero learning curve, new users productive within minutes
Browser-based with no installation required — runs on any OS and enables instant sharing via URL, removing friction for cross-functional collaboration with PMs, engineers, and stakeholders
Frequently Asked Questions
Agile is a set of values and principles (from the 2001 Manifesto). Scrum is one framework for implementing those principles. You can be Agile without using Scrum, but Scrum teams are by definition Agile.
Scrum defines a Product Owner role, not a Product Manager. In most companies, the PM takes on PO responsibilities (backlog ownership, prioritisation, stakeholder communication) while the Scrum Master handles process facilitation.
Most teams run 2-week sprints. 1-week sprints work well for mature teams with fast feedback loops; 3–4 week sprints suit teams with longer test/review cycles. Shorter sprints surface problems faster but increase ceremony overhead.