Story Point Estimation: Methods and Challenges

Abstract

Agile estimates are absolutely necessary for organizing and leading agile teams. Because there are insufficiently accurate estimates, most agile initiatives go over their budgets. Lack of accurate estimations causes inaccurate arrangement, design, improvement, and task management, which may result in the delivery of an unsatisfactory project or product to the client, leaving them—and the end user—unsatisfied. When the project's initial phase resulted in dishonest projections, the project's dangers were not identified. The main goal is to present different Agile Story Point judgment methods that are used in development settings along with their difficulties. Aids development teams in using accurate estimation techniques in their projects. Agile projects can be estimated using a variety of estimation methodologies. Planning Poker, T-Shirt Size, Dot Voting, Bucket System, Big/Uncertain/Tiny, Affinity Mapping, Ordering Method, Maximum Size or Less, Bottom-up estimation, Top-down projections, Expert Judgment, comparative or analogous estimation, Parametric Estimation, the Delphi Method, and the three-point method are a few examples of Agile estimating methodologies. The paper goes into detail about each Scrum estimate model and discusses the difficulties with each agile estimation method.