Agile
Agile Estimation: Story Point vs Ideal Hour — It is a generation gap issue
Jun
Story Point vs Ideal Hour — It is a generation gap issue
via Scrum.org Blog by Naveen Kumar Singh
How much have you scored this year? My parents asked this question twice a year throughout my schooling. When I scored 80%, they reminded my previous scores were better, and when I said 90%, they checked how much Sharma’s son scored. They also reassured themselves with follow up questions — are you in top 5, top 10, or topper this year?
I was well prepared to ask the same questions to my son, but school cheated me. They changed the percentile system and implemented a student grading system. I hope you must have understood my dilemma and challenges by now.
Have you had a similar past? If yes, then you will understand why I call it a generation gap issue.
I keep telling this story in my The Scrum Master training program and use it to teach senior management through coaching.
Let’s take a couple of minutes to understand these:
- What is software development effort estimation
- How we were estimating earlier
- What is story point estimation
- What are the challenges with story point
- Why it is a generation gap issue
What is an estimation in software development?
Straight from Wikipedia — In software development, effort estimation is the process of predicting the most realistic amount of effort (expressed in terms of person-hours or money) required to develop or maintain software based on incomplete, uncertain and noisy input. Effort estimates may be used as input to project plans, iteration plans, budgets, investment analyses, pricing processes, and bidding rounds.