Teklens logo
DEEN
Back to the Teklens use-case library
Phase 03 · BuildTeklens match: very high

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

Scrum MasterProduct OwnerProduct ManagerCPO / CTO

Teklens apps & integrations

Teklens.aiJira

Example prompts

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

More use cases from the same phase of the cycle.

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 companionJira stays the source of truth – Teklens sits on top as a companion and answers questions about status, complexity and impact with code context.View use case

From the PM Lab

Articles that explore this use case in depth.

Try Teklens now

Software product management × code intelligence: your context becomes reasoned priorities and build-ready specs.

Start the demo Talk to a founder