Sprint
A sprint is the basic unit of delivery in Scrum and many other agile approaches. At the start of each sprint the team agrees a goal and pulls a manageable slice of work from the backlog; over the sprint it builds that work into a done, potentially shippable increment; and at the end it reviews the outcome with stakeholders and holds a retrospective to improve how it works. Crucially, a sprint is time-boxed — its length is fixed, so if not everything is finished, the scope flexes rather than the deadline.
This fixed cadence is what makes agile predictable. Because a team ships something every sprint, stakeholders see real progress regularly, feedback arrives while it can still change the outcome, and estimates get more reliable over time as the team learns its own pace. The sprint length is chosen to balance responsiveness against overhead: shorter sprints mean tighter feedback loops but more ceremony; longer ones mean less overhead but slower course-correction.
For talent and HR audiences, the sprint is worth understanding because it defines the working rhythm of the teams a GCC staffs, and because People teams increasingly adopt it themselves. A recruitment team can run its own work in sprints — a two-week push on a hard-to-fill mandate, reviewed and re-planned — mirroring the delivery teams it supports. Understanding sprints also helps recruiters read technical CVs accurately, since candidates describe their experience in terms of sprint work, velocity, and iteration.
Frequently asked questions
How long is a sprint?
A sprint is usually one to four weeks long, with two weeks being the most common. The length is fixed for a given team so delivery has a steady, predictable rhythm.
What happens at the end of a sprint?
At the end of a sprint the team holds a sprint review to demonstrate the increment to stakeholders and gather feedback, followed by a retrospective to reflect on how the team worked and what to improve. The next sprint then begins with planning.
What is the difference between a sprint and a project?
A project is a whole effort with a defined goal and end, while a sprint is a short, repeating cycle within an agile way of working. A single initiative is delivered across many sprints, each producing a usable increment rather than waiting for one final delivery.
Can HR teams work in sprints?
Yes. People and talent-acquisition teams increasingly run their work in sprints — for example a fixed two-week push on a priority hire — to gain the same rhythm, focus, and regular review that delivery teams get from the format.