What gets scored?
- Pull requests
- Reviews
- Tickets
- Docs
- Agent sessions
Pensero scores the work automatically, from the tools the team already uses.
What are the two factors?
| Factor | Question it answers |
|---|---|
| Magnitude | How much changed? |
| Complexity | How hard was the change? |
The delivery point is the product of the two: magnitude × complexity.
When is the score given?
After the work ships. A delivery point measures finished work, not an estimate. This is the main difference from story points, which a team estimates before the work starts.
Delivery points vs other units
| Unit | What it measures | When |
|---|---|---|
| Hours | Time spent | During the work |
| Story points | Estimated effort | Before the work |
| Lines of code | Volume of text | After the work |
| Pensero delivery point | Finished work, magnitude × complexity | After the work ships |
How do you check a score?
Each delivery point links to the pull request and the ticket behind it. A client, a vendor or a manager can open them and see the work that the score is for. Pensero reads delivery points next to cost and quality.
How Pensero helps
- Read what a delivery point is, what Pensero reads and never reads and how to quote a project without man-hours.
- Book a scoping session to see delivery points on your own work.
Frequently asked questions
Who scores delivery points?
Pensero, automatically, from pull requests, tickets, reviews, docs and agent sessions.
Are AI agents scored the same way as people?
Yes. Agent work is scored the same way as human work, so firms can compare both on one scale.
Is a delivery point the same as a story point?
No. A team estimates story points before the work. Pensero scores delivery points after the work ships.
Can I see why a change got its score?
Yes. Each delivery point links to its pull request and ticket.
