Capacity Planning to pull from Work Remaining rather than original estimate

When Planning your capacity in the Aha Feature Board. The bar does not always represent the actual points that are remaining. We are currently using the Fibonacci Sequence. The screenshots are only for example purposes.

Issue: (see 1-Logged_Time.png)
A request that may span over multiple sprints causing the capacity to be over-the-limit for each sprint (release).

Complication: (see 2-UserStoryPointTotal.png and 3-FeatureBoard_Capacity.png)

Work completed is not captured in the sprint (release) to properly capacity plan

Does not allow for ranking correctly when integrating with JIRA

Resolution:

Have the capacity logic pull from Work Remaining rather than Original Estimate (see 4-Feature_LogTime.png)

4-Feature_LogTi...

3-FeatureBoard_...

2-UserStoryPoin...

1-Logged_Time.png

4-Feature_LogTime.png

Open full size

3-FeatureBoard_CapacityPlanning.png

Open full size

2-UserStoryPointTotal.png

Open full size

1-Logged_Time.png

Open full size

4-Feature_LogTime.png 3-FeatureBoard_CapacityPlanning.png 2-UserStoryPointTotal.png 1-Logged_Time.png

• ADMIN RESPONSE

  Sep 4, 2017

  Thank you for the idea. One suggestion would be to leverage master features to capture those larger items that span multiple releases. You could then break the master feature down into smaller increments that can be completed in a single release/sprint.

  At this time we do not have plans for updates in this specific area but hope that the suggestion above might help.

• Comments 0
• Votes 6