Release and Feature Management Change Log Reports

Product teams are commonly measured on providing a predictable delivery of features for a planned release and need to report on change metrics such as the number of Features added to a release after the release has been approved for development and the number of features dropped/moved to another release. These types of changes are being recorded in the Aha! Activity log but there is no way of being able to create change log reports at the Release level [i.e. Number of features added and number of features dropped/moved] as well as at the Feature level [i.e. this feature changed releases 3x from v6.1 to v6.2 to v6.5].

The requirement is for Aha! to provide release and feature change log reports to help report on these key metrics to the business and to also keep track of any major changes to plans. 

Watch notifications of changes are helpful but are for individual events and do not provide the required aggregate view on the scope of changes. 

  • Matt Case
  • Jun 29 2017
  • Future consideration
Release time frame
  • Attach files
  • Paolo Espanola commented
    October 10, 2017 19:36

    Additionally, this will provide us with a layer of governance as currently, there's no wholesale way to catch Features that have inappropriately slipped into a Release that was already scoped and locked.  Likewise, should items "slip" to future Releases that shouldn't have (ex: urgent client commits, previously slipped items, etc.), we don't have a quick way to view these in bulk.

    Instead, the workaround would be to export the full Feature List for a specific Release on a periodic basis and run a VLOOKUP externally do identify the adds/drops.  This is extremely manual and has a higher risk for error due to the time lag.