Skip to content
BENIBIX Learn

Agile Delivery

Sprints, backlogs and boards: shipping the work in short blocks · 52 terms

Sort
Compare

Agile

5

The idea of building in small, checked pieces, the statement it grew from, and the time blocks and team habits it rests on.

A way to build in small pieces. Each piece is shown, checked and used to plan the next.

A short list from 2001 with four values and twelve principles. Agile ways of working grow from it.

One short round of work, often one to four weeks. Build, check and learn, then go again.

A fixed amount of time for a task or a meeting. When the time is up, it stops.

A team that chooses for itself how to do the work. Nobody hands out each task.

Scrum

17

The most used agile framework: its small team, its fixed events, the lists it keeps and the goals each list serves.

An agile framework for small teams. The work happens in sprints of one month or less.

The small team that works in Scrum. One Product Owner, one Scrum Master and the Developers.

A meeting where each Scrum Team sends one person. They sort out work that crosses teams.

Roles

3

The jobs inside a Scrum Team, and what each one answers for.

The Scrum role that decides what gets built next. One person who owns the Product Backlog.

The Scrum role that helps the team work well. A coach who clears blocks, not a boss.

The Scrum role for all who build the product. Coders, testers and designers all count.

Events

5

The timeboxed meetings of Scrum, in the order a sprint runs them.

Scrum's fixed round of work, one month or less. Each one ends with a result people can use.

The meeting that starts each sprint. The team picks a goal and plans the work to reach it.

A 15-minute daily meeting for the team that builds. They check the goal and change the plan.

The meeting where a team shows a sprint's work. The people it is for say what should come next.

The meeting at the end of each sprint where the team improves the way it works.

Artifacts

3

The things Scrum keeps in view: the lists of work and the usable result.

The ordered list of all work that could improve a product. The top items come next.

The plan for one sprint. It holds the goal, the chosen items and the steps to finish them.

A finished, usable piece of the product. Each new one adds to the last and works with it.

Commitments

3

The goal or standard pinned to each Scrum artifact, saying what it is for.

The long-term aim of a product. Each item on the Product Backlog should help reach it.

The one aim of a single sprint. It says why the sprint's work matters.

The checklist all work must pass to count as finished. The whole team uses the same one.

Kanban

8

Managing work as a flow: the board that shows it, the caps that keep it moving and the pull that starts new work.

A method that shows work on a board and caps how much is in progress. No sprints.

A board with a column for each step of the work. Cards move across it as work gets done.

A cap on how many items can be in one step at once. Finish work before you start more.

A way of working where people take new work only when they have room. Nobody pushes it on them.

Flow Metrics

4

The clocks, counts and charts that show how fast work moves through a team.

The time from when work is asked for until it is delivered. It is the wait the customer feels.

The time from when work on an item starts until it is finished. Waiting before the start does not count.

How many items a team finishes in a set time. For example, five items a week.

Stacked bands, one per step of the work, drawn over time. A band that widens shows a jam.

Frameworks

4

Other named ways of working agile, from coding habits to waste cutting to running many teams at once.

An agile method made of strict coding habits. Pair up, test first, and ship small and often.

Building software with less waste. What adds no value for the user goes.

A way to run agile with many teams. Groups of teams plan as one, every few months.

A mix of Scrum and Kanban. Keep some Scrum meetings and run the work on a Kanban board.

User Stories

7

The short notes agile teams plan work in, the bigger and odder kinds of them, and how a big one is cut down.

A short note of one thing a user wants, and why. The details come from talking.

A big piece of work, too large for one sprint. It gets split into user stories.

A short bit of research with a time limit. It answers a question so a story can be sized.

Breaking a big story into small ones. Each one still gives users something that works.

Story Quality

3

The checks that say a story is clear enough to start and when it counts as accepted.

The checks one user story must pass to be accepted. Each one can pass or fail.

Six letters to check a user story. A story that passes all six is ready.

A checklist for when a story is ready to enter a sprint. Many teams keep one.

Planning

11

Getting the backlog ready and deciding what ships when: refining, ordering, mapping releases, sizing work and tracking it.

Ongoing work to split, detail and size backlog items. Then the top is ready to build.

Deciding what goes in a release and about when it ships. It is updated each sprint.

A map of stories along the steps a user takes. Lines across it mark each release.

A way to sort work into must, should, could and won't have this time.

Estimation

4

Ways to size work by comparing it with work already done, rather than by guessing hours.

Sizing work by comparing it with work you know. Not by guessing hours.

A unit for how big a story is. It mixes effort, risk and doubt, not hours.

A team sizing game. All show a number card at once, then they talk and vote again.

Rough sizing with shirt sizes, from XS to XL. Quick, and good for early plans.

Progress Tracking

3

The pace a team keeps and the charts that show work left, work done and scope over time.

How much work a team finishes per sprint, often in story points. Used to plan ahead.

A chart of work left over time. It should slope down to zero by the end.

A chart of work done climbing toward a scope line. It shows when scope changes.