Bottom-Up Software Effort Estimation Technique
Last time, we explained that even though estimating software project timelines is tough, we should do it anyway. We also broadly discussed some of the common estimation techniques. With that background, we want to go into further detail about the bottom-up software effort estimation technique that works for us. A critical aspect any estimation technique should capture is time and uncertainty. An estimate that only has time implies a high degree of certainty. This generally is not true for most of the projects. Here it goes : For details, read on: It is tough to give an accurate estimate to a complex task. Therefore, it is recommended that you break into small chunks. That will remove the number of uncertain variables. We use the following Sizes: Complexity Time Small 1 day Medium 3 days Large 1 Week Extra-Large 2 Weeks Your estimation gets accurate only when you are very granular in mapping and recording the hours that go towards a project’s completion. The whole point is to use real wall clock hours and days and idealized “programmer hours.” We should not be overly optimistic here. So if something might take 3 days but you might get it done in 1 day because you got lucky should still be quoted as medium. On the other hand, don’t be pessimistic by quoting that same task as large to cover your butt. In an ideal condition, your estimation mostly comprises small and medium tasks as there are few large and might be none extra large. However, you need not to do this in one fell swoop. The bottom-up software effort estimation technique advocates that you can refine the estimate later. A good software effort estimation technique will capture the uncertainty as well. “20 to 30 days” is a very different estimate compared to “5 to 45 days” even though both have the same mid-point estimate as 25 days. It is expected to capture the expected-case vs. best-case scenario. Uncertainty Level Multiplier Low 1.1 Moderate 1.5 High 2.0 Extreme 5.0 You can have a different multiplier value. That is quite possible. But defining and sticking to a system helps you to come up with quite accurate quotes. However, you will like to have more low and moderate uncertainty levels and very few high or extreme uncertainty estimates. How to arrive at the worst-case scenario estimates? The groundwork you have accomplished in your software effort estimation technique in the earlier steps will simplify this. Let me explain with an example. Task Complexity Uncertainty Expected Worst-Case Creating the filer Medium Moderate 3 days 4.5 Applying the Automation rule Large High 1 week. 2 weeks Showing an error message Small Low 1 day 3.3 days Integration with Salesforce Extra- Large High 2Weeks 10 Weeks. Is such a wide range acceptable? If not, then this step steps in. The range is so high because you have a few extreme, large, uncertain-level projects. You should review those along with your colleagues. Try to brainstorm and find out ways to reduce. You should now be breaking down extra-large complexity tasks into small ones. I agree that you would have done that had it been easy. The trick here is to revise these tasks again with a group of capable people with you on the board. It requires deeper research. You can decide to assign two weeks to work hands on some part of this task chunk and understand the complexity more closely. That will help you break this task into small and medium chunks and keep one large complexity level. There is no correct strategy here. The key observation is that if you are dealing with too many uncertain components, you should take some time to break them down into small and easier blocks. Track your accuracy so that you can improve over time. This helps to form a feedback loop. You project. You observe how much it deviates. You use that knowledge to refine your project in the next time. We hope that you will find this software estimation technique useful. Please share your feedback if you use this software estimation technique in your next project. The credit for this technique goes to Jacob Kaplan Moss – Co-creator of Django.Bottom-Up Software Effort Estimation Technique
Break Down Work into less complex task chunks
How to Estimate Uncertainty?
Once you have quoted the expected time blocks as described in the above section, you will now apply the “if-things-go-wrong” multiplier described below:Revisit the Software Effort Estimation
Track
Browse by categories
- Agile
- Artificial Intelligence
- Automated testing
- Big Data
- Blockchain
- Business Intelligence
- Chatbots
- Cloud Computing
- Customer Experience
- Data Science
- Design Thinking
- DevOps
- Dialogflow
- Digital transformation
- EduTech
- ETL
- Healthcare
- HealthTech
- Machine Learning
- Mobile application
- Product Development
- Quality Ascent
- Quality Assurance
- Real Estate
- Software Testing
- StartUp
- Testing
You May Like This

Top 10 AI Development Companies You Must Know In 2025
Choosing the most appropriate AI partner is crucial for you if you are planning for the digital transformation of your business. Introduction It is the AI sector that should be listed among the fastest-growing ones because it is continuously coming up with new solutions to provide businesses of different sizes with newly found opportunities. AI […]

How Is Virtual Reality Making A Difference In Product Design?
The product design and development industry has gone through drastic changes over the past few years with constant evolution and advancement of technologies. The growing complexities and changing demands of customers makes it necessary for information technology experts to design high-quality products and deliver it to the market in a short span of time in […]

How Business Intelligence Channelize Multiple Departments In Industries?
The sales and marketing industry is evolving continuously and is moving towards a customer-oriented approach for carrying out their operations. The market is becoming more dynamic with each passing day and industries require a vast amount of sales data for carrying out analytics, reporting, price fixing, negotiations, etc. by studying the trends and customers’ behaviour. […]

The Significance of User Interface Design in Mobile Applications
In today’s digital age, almost everyone uses digital media on their computers or smartphones. Consequently, both platforms have a sizable user base. A laptop is recommended for access to web pages, whereas mobile phones are known to produce a great User Experience (UX). Mobile and its related technologies are becoming increasingly popular on a global […]

RPA-A Tool To Transform The Retail Industry
The emerging markets and technologies are making the retail sector one of the prominent growth sectors among industries. The evolution of diverse technologies is simplifying various basic processes of the sector and allowing them to integrate automation in their operations. Technologies such as robotic process automation (RPA), artificial intelligence (AI), etc. are highly contributing to […]

Benefits Of Integrating Blockchain Technology In Banking Industry
The banking industry is undergoing a sea of change by embracing advanced banking methodologies with each passing day to deliver greater transparency and accuracy in various operations of the industry. The financial services industry is moving beyond its legacy systems and embracing new technologies to improve their outdated systems and infuse innovative ways of carrying […]