What is the challenge? |
My team runs an annual planning process of initiatives from Aha! Roadmaps. We use team capacity planning to estimate the expected headcount required for each team per quarter for our upcoming FY. We like to run 2 rounds of these estimates - an initial estimate round helps us start to narrow down what we can commit to, then a final estimate round locks in our plan. We do this by using 2 scenarios. Once the Initial estimates are done we copy the data to the Final scenario to give us a starting point. Scenario 1: FY27 estimates Initial Scenario 2: FY27 estimates Final The challenge is, our users struggle to make sure they are adding estimates to the proper scenario. Both have different names but the capacity plan record looks the same across them. This leads to users making edits in the wrong scenario. |
|---|---|
What is the impact? |
Hard to ensure a completed scenario is not being improperly edited. I do not want to archive the scenario since i want the first round of estimates to still be visible. |
Describe your idea |
Lock a scenario from editing. Can be an account level control just like how you can archive a scenario. Let me lock the Initial scenario from edits so my users only add estimates to the final scenario. |