Allow tracking the usage of selected features and present the data in hierarchical way
Typical Feature workflow includes
Aha!
Product workspaces
Releases
Features
Its development and then the usage.
Questions need to be answered
This Feature introduced in this Version and here is the usage information and here is the usage
how it is progressing after this release.
Match Feature usage with Expectations and KPI's
In the future it can be matched against to the predetermined usage expectations or KPI's
that would be in first place defined as part of hypothesis thriving the prioritization of that feature and inclusion in the product
How well are we doing with our expectations which were defined and used to decide which feature to implement or not?
This will be Useful in further iterations.
This needs to be resolved in various phases and steps.
Aha! Feature, Epic, Release in Snowflake (Done)
Aha! Feature needs fields to capture Feature GUID and ProductID (Done)
Documentation why, what, when and how
to introduce this type of reporting (planned 2023-Q3)
allow teams to include these fields in their Feature UI and processes
Build report (to do)
Introduce to the teams (to do)