Output

Definition

An output is a deliverable produced by a team, such as a feature, report, or release. Agile teams treat outputs to achieve outcomes, not as an end in themselves.

Context

Many teams are measured by how much they deliver. But being busy does not mean being effective. Agile teams avoid the trap of maximizing outputs without knowing whether those outputs create value. They start by clarifying the desired outcome, then decide which outputs will best support it.

The Agile Manifesto sums this up in one of its principles as:

“Simplicity - the art of maximizing the amount of work not done - is essential”

Description

Outputs are the tangible results of work, including code, designs, reports, or released features. Agile teams deliver outputs iteratively and incrementally, but always with a clear purpose.

A focus on outputs without outcomes leads to waste. When teams build things that do not solve real problems, even fast delivery is a poor use of time and resources.

Example

A Scrum Team delivers three new dashboard features in a Sprint. These are outputs. But if users do not engage with the new dashboards, the intended outcome e.g. better data driven decisions, has not been achieved.

Common Misunderstandings

Teams sometimes equate productivity with the number of outputs. But delivering a lot does not help if those things do not create value. Agile ways of working help teams focus on delivering the right outputs that support a meaningful outcome.

Want to Learn More?

Explore the Sprint Goal article to see how teams align their outputs to achieve clear, valuable outcomes.