Add a new idea Subscribe
Status Shipped
Categories Features
Created by Ankar S
Created on Aug 15, 2019

RELATED IDEAS

Ability to stack rank all features within a Product

Right now, drag and drop stack ranking features within a Product is limited to stank ranking features in each Release.

The only other way to prioritize across Releases is via a scorecard, but this is tedious for Product Managers who do not want to utilize the scorecard for every feature in order to do this.

This idea is to enable stack ranking features across Releases in a Product so that a Product has a prioritized backlog that is easy to change via drag and drop stack ranking.

Release time frame 1 month
  • ADMIN RESPONSE
    Sep 14, 2022

    New prioritization pages for scoring and ranking work

    You can now estimate the value of multiple ideas, features, or epics in one view. Quickly update scorecard metrics inline and rank items in priority order — so you can move ahead with confidence.

    See how

    Features priori...
    Features prioritization.png
    Open full size
    Features prioritization.png
  • Attach files
  • Marcie Gardner
    Reply
    |     May 9, 2022

    Hi team, in Aha, we'd like the ability to create a stack-ranked view (a backlog) of Features and/or Program Epics. This would allow our team to continuously prioritize items throughout the year and quarter.

    I’m envisioning something similar to the functionality provided in JIRA (backlog). This is an essential component to planning, focus, and the ability to easily radiate prioritization. I know that a custom “ordinal list” field exists, but this is extremely cumbersome, not intuitive, and requires re-work to avoid duplicates.

    I’ve observed a significant number of teams using Excel to do this and then moving into Aha, but it’d simplify our planning and development workflow if we are able to do this in Aha.

  • Nicolai R.
    Reply
    |     Apr 3, 2020

    Without stacked ranking between releases and parking lot you cannot synch a one prioritized backlog from Aha! to Azure Devops.

    The lack of this capability can definitely be a deal breaker.

  • Guest
    Reply
    |     Aug 22, 2019

    Total agree.  As team perform the commitment per release, we need a stack rank of feature for the product across the releases.  As the commitment is made, they should move off the product ranked backlog into the release. 

  • Ankar S
    Reply
    |     Aug 15, 2019

    I would imagine that this feature would also be able to apply to Master Features as well (via the MF toggle)

  • +1