Automatically estimate work timelines based on past performance

Quickly estimate work based on past performance.

September 10, 2025

Automatically estimate work timelines based on past performance

by Claire George

Estimating when features will be delivered is notoriously hard. And often, these estimates are just wrong. Why? Because solving technical challenges can be unpredictable. Yet dates still matter. Customers and colleagues want to know what is coming and when so they can coordinate their own activities. Today's update takes the guesswork out of this process.

Automatically generate initial estimates for new features in Aha! Roadmaps based on historical cycle time data in Aha! Teamwork and Aha! Develop.

First, a quick recap of how product managers can work closely with engineering and delivery teams to manage estimates at different stages of the planning process in Aha! software.

Start by setting an initial estimate in Aha! Roadmaps. This helps you gauge effort as you build out your roadmap. As implementation gets closer, teams add detailed estimates in Aha! Teamwork or Aha! Develop based on a deeper understanding of the requirements. Keep track of the actual effort so you can compare the difference between your estimates and how long it actually took to complete the work.

Today's update enables you to quickly set those initial estimates based on past performance. Our software automatically analyzes the team's cycle time for implementing similar features in Aha! Teamwork and Aha! Develop, suggesting a realistic estimate to inform your plans.

To get started, enable the new Suggested initial estimates option in the Capacity planning section of your Team settings. Then, define how to calculate suggested estimates:

  • Start status and End status: Determine when the clock starts and stops

  • Time period: How far back you want to analyze historical data

  • Confidence level: Adjusts the prediction based on your risk tolerance

  • Estimate filter: Refines your estimates further (for example, by feature type or T-shirt size)

Once enabled, when you assign a feature to a team in Aha! Teamwork or Aha! Develop, the new Suggest an estimate button appears right next to the Initial estimate field in Aha! Roadmaps. In the example below, we estimate a new feature for a fictitious cycling app. We assign it to the front-end engineering team and click the button. Based on historical data for similar features, the suggested estimate is four days.

Suggested development estimates are most accurate once you have data from at least 30 completed records.

That gives us a solid starting point. We can use the estimate as-is or refine it based on other context.

Estimating delivery dates will always be challenging. But now, you can make smarter predictions based on real performance data.

Suggested initial estimates are available for Aha! Roadmaps accounts connected to Aha! Teamwork or Aha! Develop — and for teams using Aha! Teamwork or Aha! Develop on their own. This is part of our ongoing effort to help you plan with greater clarity and confidence.

Start a free trial

Aha! Teamwork is the flexible project management tool. Complete all tasks, streamline workflows, and increase visibility. Aha! Develop helps agile development teams connect to the roadmap, optimize workload, and streamline delivery. Use Aha! Teamwork or Aha! Develop with Aha! Roadmaps to keep operations, IT, marketing, and engineering teams aligned with your overall strategy. Sign up for a free 30-day trial or join a live demo to see why more than 1 million product builders trust our software to build lovable products and be happy doing it.

Claire George

Claire George

Claire is passionate about helping product development teams learn how to bring their strategy to life. She is the vice president of marketing at Aha! — the world’s #1 product development software. Claire has 25 years of marketing and software experience. Previously, she led product marketing at an agile-based work management platform.

Follow Aha!

Follow Claire

Related articles

Strategic roadmaps: Vision vs. strategy vs. roadmap
January 14, 2020
Strategic roadmaps: Vision vs. strategy vs. roadmap

Roadmaps are beautiful. But a roadmap is still just a visualization. Learn why you need to have a vision and strategy behind the plan.

Your Roadmap Is a Promise (Do You Keep It?)
March 22, 2021
Your Roadmap Is a Promise (Do You Keep It?)

Your roadmap is a promise. Discover how treating your roadmap like a promise creates value for your company, team, and customers.

Roadmaps make strategy work
February 24, 2020
Roadmaps make strategy work

Putting strategy into action can be difficult. That is because too many teams jump straight to the “how” before they agree on the “why” and the “what.” Typically this…

Business Roadmaps vs. Product Roadmaps
June 11, 2020
Business Roadmaps vs. Product Roadmaps

Aha! CEO Brian de Haaff breaks down the differences between business roadmaps and product roadmaps — including where the two harmonize.