wise-estimationlisted

# Story-Point Estimation Canonical story-point (SP) scale for sizing Jira tickets. Applies to every team (frontend, backend, mobile, platform) — using the same units so cross-team planning works. This is a **reference doc**, not a procedure. When the user is planning a ticket or breaking work into tasks, consult this scale to pick a value; when the user asks "is this a 3 or a 5?", walk the complexity/scope/time axes below to decide. ## The scale Fibonacci, with a 0.5 minimum for truly trivial work. | SP | Complexity | Typical scope | Calendar time | |----|------------|---------------|---------------| | **0.5** | Trivial, mechanical | Single file, one obvious change (copy tweak, constant rename, one-line config) | ~half day | | **1** | Simple, well-understood | 1–2 files, clear requirements, pattern already exists | ~1 day | | **2** | Moderate | 3–5 files, some decisions to make, one or two unknowns | ~2 days | | **3** | Complex | Multiple components, non-trivial logic, meaningful test surface | ~3 days | | **5** | Large feature | Architecture decisions, several components, full test coverage | ~1 week | | **8** | Epic-level | Multiple sub-tasks, crosses file/module boundaries, touches API + UI | ~2 weeks | | **13** | Major feature with unknowns | Research needed, spec not fully baked, architecture open | ~3 weeks+ | ## How to pick a number Size against **three axes**. The estimate is the HIGHEST of the three, not the average — an unfamiliar-tech ticket with one file is