Scrum
Scrum is a lightweight framework in which a team delivers work incrementally through sprints — time-boxed cycles, usually one to four weeks long, that each produce a usable increment. It defines three accountabilities (a Product Owner who orders the work, a Scrum Master who enables the team, and Developers who build it), a small set of artefacts (the product backlog, sprint backlog, and increment), and recurring events (sprint planning, the daily stand-up, the sprint review, and the retrospective) that keep the team aligned and improving.
The value of Scrum is that it replaces one big, risky delivery with a rhythm of small, inspectable ones. Because the team ships something every sprint and reviews it with stakeholders, problems surface early and priorities can change without derailing the whole plan. Scrum is deliberately minimal — it prescribes the structure and leaves the engineering practices to the team — which is why it is so widely adopted across technology organisations.
For talent acquisition and GCCs, Scrum is more than a delivery method; it is a hiring specification. Roles such as Scrum Master and Product Owner appear constantly in GCC job descriptions, and engineers are routinely expected to have worked in a Scrum environment. Recruiters screening for these roles need to understand the difference between someone who has merely sat in stand-ups and someone who genuinely understands empirical delivery, backlog management, and facilitation. HR teams themselves increasingly borrow Scrum’s cadence to run their own work.
Frequently asked questions
What is Scrum used for?
Scrum is used to deliver complex work — most often software — in short, repeatable cycles called sprints. A small cross-functional team works from a prioritised backlog and uses regular events to inspect progress and adapt, so value is delivered incrementally rather than in one large release.
What are the three roles in Scrum?
Scrum defines three accountabilities: the Product Owner, who owns and prioritises the backlog; the Scrum Master, who helps the team work effectively and removes impediments; and the Developers, who build the increment each sprint.
Is Scrum the same as Agile?
No. Agile is a broad set of values and principles for adaptive delivery, while Scrum is one specific framework that implements them. A team can be agile using Scrum, Kanban, or other approaches — Scrum is a subset of agile, not a synonym for it.
Why do recruiters need to understand Scrum?
Because GCCs and technology teams hire heavily for Scrum roles such as Scrum Master and Product Owner, and expect engineers to have worked in Scrum. Understanding the framework lets recruiters tell genuine experience from surface familiarity when screening candidates.