Phase 03 · Build

Estimation with risk drivers

How it works

When the team has to commit in sprint planning: epics and stories are estimated with LOC, complexity, the dependency graph and historical velocity – and the reason behind every number is named: required API/schema changes, missing tests, highly coupled code. The difference to Code-grounded estimation in Discover: a rough triage of an idea is enough there; here the team needs a number solid enough for the sprint commitment.

Estimates grounded in code: LOC × complexity × risk
Names the risk drivers, not just a number
Re-estimates automatically when the epic's code changes

Roles

CPO / CTO · tech leadershipHead of product & engineering

Teklens apps & integrations

Teklens.aiJira

Example prompts & actions

Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.

Estimate epic [E] and name the risk drivers.

Why is this epic hard – API, schema, tests or coupling?

Related use cases

Three use cases closely connected to this one.

Cross-team dependency graphSurfaces dependencies from Jira and code at planning time instead of in week two.View use case Ticket organiserMoves tickets into sprints and assigns them to epics automatically – roadmap and Jira stay in sync.View use case Jira and code, continuously aligned.Continuously compares what is planned in Jira with what is actually happening in the code – and reports the difference.View use case

From the PM Lab

Articles that explore this use case in depth.

Give Teklens a real job.

Connect Jira and your code – and let Teklens work on something real.

Try Teklens Talk to a founder