Story point Estimation key in today’s software development

Estimation is a rough calculation of work that can be done.So traditionally in software industry there were many methods for estimating the work or a activity.The estimation techniques like COCOMO,Function point were mostly used during previous times for estimating tasks.These were all statistically techniques and formulas were used in order to come to a rough value. Then came the  era of Project Management and almost whole industry quickly moved towards WBS estimation. WBS commonly known as Work breakdown structure is a method of breaking down the larger activities to smaller sub-divided executable tasks .WBS estimation based on the smaller tasks a time boxed duration and effort is assigned and then estimates are arrived. Mostly WBS estimation is done in a Microsoft project plan and done by Project Manager. It is recommended that he/she  should discuss with team and come up with probable estimates but hardly there would be very less project managers who follow this. Ultimately project managers decide on the estimates himself and assigns duration ,effort to the tasks wherever applicable .Eventually when it comes to execution it would result in failures and slippages in project leading to customer dissatisfaction

So I feel that Agile based story point estimation is much fairer and justifiable and easy going on the team if executed properly.Currently almost all the industries irrespective of the mode of execution are moving towards Agile Development.In Agile Story point estimation is a process which is more of a abstract based rather than detailed approach .If we list down the points which story point estimation covers it is better and more focused approach for estimating tasks

1.Unit less estimation:-Story point is unit less relative estimation .So any team members or project mangers cannot covert into hours /days for estimating the task

2.Experience and Learning -Since story point estimation is a brainstorming technique where all team members sit together and estimate the tasks.So fresher in team would always quote more story  points to complete while a architect would always quote less points in team to complete a task .That’s obvious as experience and learning comes into picture.So it depends on scrum master to decide upon the task and who suits best for the profile.

3.Risk or Uncertainity:-Story point estimation for a user story developers also consider any risk or uncertainty associated with user story.These risks and uncertainties are discussed in the team and accordingly story points are assigned.

4.Amount of work:-Amount of work which needs to be completed for a particular user story also contributes in estimating a story point.Based on the quantum of work and sub tasks that needs to be completed also helps in zeroing down to a estimate.So I belive a definition of done also plays a important role in contributing towards and summing up amount of work

With above 4 points being considered for estimating tasks.I feel that story point estimation has all aces covered in project estimation.i also believe that this makes the story point estimation technique unique and accurate.Story point estimation is more accurate to reality and it is one of key factors for successful Agile development.It’s better that leaving not only even traditional waterfall and  V models use story point estimation techniques to make it more accurate and precise