Story Point Estimator
Calculate complexity based on technical and procedural vectors.
Base Difficulty
Technical Difficulty
— Technical complexity.
?
Medium example: adding a new feature, modifying an existing feature.
Hard example: architectural changes, complex algorithms.
Easy
Medium
Hard
Procedural Difficulty
— Organizational complexity.
?
Medium example: changes in a process which is part of the large process, but in squads ownership.
Hard example: changes/implementations of a large process, whichs scope may exceed our squad.
Easy
Medium
Hard
Variables that Increase Difficulty
Deployment Complexity
— Adds to overall difficulty.
?
How difficult is it to get this code into production? Hard means manual interventions, database migrations, or coordinated multi-system deployments.
Easy
Medium
Hard
Testing Requirements
— Multiplies technical difficulty.
?
The effort required to verify constraints. Hard means extensive integration tests, end-to-end testing, or heavy manual QA coordination.
Easy
Medium
Hard
Module Dependencies
— Multiplies base difficulty.
?
How much does this task rely on or impact other parts of the system? Hard means changes cascade across multiple systems or teams.
Easy
Medium
Hard
Technical Domain Knowledge
— Multiplies technical difficulty.
?
The specialization required to execute the work. Hard means it requires deep expertise in a specific obscure technology or legacy system.
Easy
Medium
Hard
Business Domain Knowledge
— Multiplies procedural difficulty.
?
The understanding of business rules required. Hard implies navigating complex, undocumented business logic or specific regulatory frameworks.
Easy
Medium
Hard
Reset Defaults
Estimated Story Points
1