Agile and Scrum explained for non-software teams
What Agile and Scrum really mean, the three accountabilities, five events and three artifacts, and how marketing, HR and operations teams can borrow the useful parts.
"Agile" started in software, but its core idea works for any team with changing priorities: deliver in small pieces, get feedback early, and adjust. Scrum is the most popular framework for doing that.
Scrum in one minute
The official Scrum Guide (last revised in November 2020 by Ken Schwaber and Jeff Sutherland) describes a small team working in fixed time-boxes called Sprints, usually one to four weeks long.
| Accountabilities | Events | Artifacts |
|---|---|---|
| Product Owner: decides what is most valuable Scrum Master: helps the team work well Developers: the people doing the work |
The Sprint Sprint Planning Daily Scrum (15 minutes) Sprint Review Sprint Retrospective |
Product Backlog Sprint Backlog Increment (finished work) |
How non-software teams can use it
- Marketing: two-week sprints of campaign assets, with a review where stakeholders see real drafts, not slides about drafts.
- HR: a backlog of hiring and onboarding improvements, prioritised by impact.
- Operations: visual boards that make bottlenecks obvious, plus a short daily stand-up.
Start small: borrow three habits
- A visible backlog: one prioritised list of everything the team could do.
- A short planning session every one or two weeks: pick what fits, and commit to a goal.
- A retrospective: 30 minutes on what went well, what didn't, and one thing to change.
When not to use Scrum
Work that is fixed, regulated or highly predictable (a compliance filing with set steps, for example) is often better served by a traditional plan. Many teams mix the two: a fixed overall plan with agile delivery inside it. See our one-page project plan.
Join the discussion
Have a question or a tip to add? Comments are reviewed before they're published.