How do you estimate effort for Scrum tasks or stories?

Short answer: Effort is typically estimated using relative sizing methods: ✅ Story Points (most common) ✅ Planning Poker (a team-based game using consensus to estimate) ✅ T-shirt sizes (S, M, L, etc., for quick high-level sizing) Story Points consider: Complexity Amount of work Risks or unknowns

Example code

A login screen might be a 2-point story (simple, well understood). A feature with integrations and security considerations may be 8 points due to complexity and risk. Pro Tip: Avoid estimating in hours — it introduces false precision. Focus on relative effort, not duration.

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.