Worked walkthrough: do the capacity math out loud

Kim is asked to add a dashboard this sprint. Estimated effort: 6 hours data cleanup, 3 hours dashboard build, 2 hours QA, 1 hour stakeholder review. Only 4 unallocated sprint hours remain. Capacity math -> explicit tradeoff: estimate the ask, compare capacity, offer scope/time/resource choices. The common trap is to call a 12-hour request "small" because each part sounds reasonable in isolation. Estimate the full ask 6 + 3 + 2 + 1 = 12 hours. Include cleanup, build, QA, and review. A no based on partial effort will underprice the request. Compare capacity 12 hours needed - 4 hours…

Sign up free — one personalized lesson every day, matched to your role and goals.

Already have an account? Sign in