Blog / Other resources

What is a delivery point in software development?

A delivery point is one unit of finished software work, scored by magnitude × complexity, the same for engineers and AI agents.

How is a delivery point scored?

  • After the work ships, not before. It measures finished work, not an estimate.
  • Magnitude × complexity. How much changed, and how hard the change was.
  • All work counts. Pull requests, reviews, tickets, docs and agent sessions.
  • The task, not the person. The same change earns the same points in any stack, and duplicates earn zero.

Delivery point, story point or hour?

Hour Story point Delivery point
Measures Time An estimate Finished work
Set by The timesheet The team, before the work Pensero, after the work ships
Same for people and agents No No Yes
Compares vendors No No Yes

What do teams use delivery points for?

  1. Quote: price a scope in delivery points instead of hours.
  2. Evidence: show the client the points behind each invoice.
  3. Cost: read AI spend per point by client, team and model.
  4. Compare: put engineers, agents and vendors on one scale.

What is a delivery point in Kanban?

In Kanban, the delivery point is the point where finished work leaves the system and reaches the customer. The commitment point is where the team agrees to start the work. This page is about the delivery point as a unit of finished work.

How Pensero helps

Sources

Frequently asked questions

What is a delivery point?

One unit of finished software work, scored by magnitude × complexity after it ships.

Who scores delivery points?

Pensero, automatically, from pull requests, tickets, reviews, docs and agent sessions.

Is a delivery point the same as a story point?

No. A story point is an estimate set by the team before the work. A delivery point measures finished work after it ships.

Can AI agents earn delivery points?

Yes. Agent work is scored the same way as human work.