Practice estimation by evaluating complexity, effort, and uncertainty. Get a suggested point range with reasoning.
How technically challenging is this story? Consider dependencies, new technology, and integration points.
How much work is involved, regardless of difficulty? Consider volume of code, testing, and documentation.
How clear are the requirements and approach? Consider unknowns, ambiguity, and need for discovery.
Story points measure relative effort, not hours. Compare this estimate to your team's reference story. When estimates vary widely in planning, that's a signal to discuss, not a problem to solve.