AgileCards Lite 1.7

This approach offers a straightforward mechanism for effort estimation: simply swipe to select the relevant Fibonacci number or double-tap to reset to 1. The sequence implemented here is a modified Fibonacci progression: 1, 2, 3, 5, 8, 13, 20, 40, 80.

While points do not directly equate to hours, they serve as an intuitive gauge of "effort level." Our team considers each point as a Gaussian distribution spanning from half to twice the point value in hours. For example, a task perceived as requiring about half a day might be rated as a 5, whereas an estimated two-hour task could be classified as a 2 or 3. Ultimately, the true time needed to complete an hour's worth of work—represented by 1 point—will usually surpass a single hour, emphasizing the conceptual value of points in planning.

By maintaining consistent planning practices, we can monitor our velocity based on total points completed per Sprint. This data enables more predictable forecasting of future work.

At present, the system relies solely on point values—future developments are anticipated to expand upon this foundation.

Regarding the use of a "modified" Fibonacci sequence: when estimating larger stories or tasks exceeding 13 points, the level of detail diminishes and the probability of accurate planning decreases. Therefore, scaling up to 20, 40, or 80 points allows us to represent effort estimates while recognizing that such assessments require ongoing refinement and elaboration.