Just Launched! — Improved Capacity Planning and Time Tracking
I love my job. I love helping product managers get the most out of Aha! — and sharing these weekly updates with you is an important part of that work. I also have more on my to-do list than there are hours in the day. Sound familiar?
I know that you have a ton of to-dos too and that there is likely a long list of features in your backlog, but only so much time to build what matters most. This is where capacity planning can help you and your team know when to make tough trade-off decisions.
Capacity planning is both a science and an art. Estimating what work can be completed within a given period of time is never simple. However, comparing those initial estimates against actuals adds a bit more science to the process.
Aha! enables product and engineering managers to better plan releases by aligning development capacity with the effort required to complete features and requirements. Leveraging this information allows you to better prioritize your releases and features, as well as track the overall progress of the team.
Our latest enhancement gives you the flexibility to specify how you record work logged in Aha! against your initial estimates when work is shipped. Here’s how it works:
Estimate releases by time or points Capacity planning helps you estimate the amount of work that can fit in a release. Above each release, the capacity bar shows how much work has been completed against your estimates. Estimates can be measured in story points or by time. And since you can choose to record in minutes, hours, days, weeks, or months, time estimates in Aha! are flexible enough to match exactly how your team works.
When enabled, capacity planning in Aha! allows you to quickly visualize the progress of each release.
Capture estimates on features or requirements Sometimes a simple user story is all you need. However, a complex feature may require dozens of requirements. Either way, product and engineering teams need to predict the level of effort required. That is why you can either estimate and log time at the feature level or break down estimates for each of the requirements. When you estimate time for requirements, progress is tracked individually and also summarized in the feature card.
Work with the engineering team to estimate the level of effort required for each feature or requirement.
Prioritize features Of course, when you start estimating work, sooner or later you are going to have a release that is over capacity. And unless you have a development team that does not require sleep, that means you will need to make some difficult prioritization decisions. The Aha! scorecard gives you an objective way to measure which features are going to have the largest impact on the business and which ones can be pushed to a future release.
Quickly measure the impact of each feature against your strategy. Aha! scorecards can be weighted and customized to reflect your business objectives.
Track work done Once a release has been estimated and prioritized, it is time to track work to ensure that the team is on pace to meet those target launch dates you have been counting on. And whether the progress is recorded directly in Aha! (or updated via your JIRA integration if you have one), capturing the amount of time spent working is valuable data that allows product and engineering leaders to better estimate the effort required for similar work in the future.