Last time, I explained that, although estimating software project timelines is hard, you should do it anyway. With that background, I want to go into some detail and share the technique I use when I need to develop a project timeline. I don’t believe there’s a single “correct” technique; this is one system that works well for me. However, my system does have one critical characteristic that I believe any effective estimation technique should have: it captures both time and uncertainty.

Louis

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Learn a software estimation technique that captures both time and uncertainty. The technique involves breaking down work into smaller tasks based on complexity, estimating uncertainty, and refining the estimate as needed. By tracking accuracy over time, you can improve your estimation skills. Other estimation techniques like PERT, evidence-based scheduling, and fruit-salad scrum are also mentioned.

My Software Estimation Technique

The critical characteristic: capture time and uncertainty

I’m doing something similar by using the PERT, Standard Deviation, and Monte Carlo Simulation algorithms. I also created an Excel sheet for this too.

This is a good article with lots of details and tips. It can help if you’re having trouble estimating, which often happens 😅

Estimation is always a headache so thank you for sharing this post, with a lot of tips to estimate more accurately.

thanks! very useful! I will make some tests on this