Phase 03 · BuildFeatured
Estimation with risk drivers
How it works
Estimates with LOC, complexity, the dependency graph and historical velocity — and names the reason: required API/schema changes, missing tests, highly coupled code. Estimates land within ±30 % instead of ±100 %.
- 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 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?
Try Teklens now
The planning software that knows your business – and turns it into specs, epics and stories grounded in real code context.