The queue, the timebox, and the mindset
These terms are often bundled together, but they describe different things.
- A backlog is an ordered pool of potential work, usually tickets or user stories on a shared Jira board or similar tool. Its items are options, not promises.
- A sprint is a fixed working period, often one or two weeks, used by teams following Scrum. The team selects work for the sprint in advance. Other teams use a continuous flow instead.
- Agile is a family of principles that favours small steps, frequent feedback, and adapting as the team learns. Scrum and Kanban are two ways teams put those principles into practice.
Imagine a council planning repairs across a city. Crews can tackle only some of the jobs in their backlog. Residents’ reports and the crews’ discoveries may change what comes next. In software, a team’s review and retrospective provide similar feedback.
Agile still needs a plan
Software is easier to change than a factory production line, where replacing machinery can be costly. That flexibility makes it practical to adjust plans as the team learns.
Agile teams still set goals, manage risks, and coordinate launches. They revisit plans as evidence changes. A sprint gives them a short planning horizon, but selected work may remain unfinished or urgent work may interrupt it.