Phase out Aha!
The objective is to phase out the use of Aha! as a collaborative tool for writing functional specifications.
Depending on the status of the functional specifications and the status of the corresponding feature(s), Aha! contents will be migrated either into GitLab issues or in the documentation website.
Types of contents, location, status and targeted destination
A tag called Migrated_to_GitLab
is created into Aha! and is used to flag all features and other contents once it is fully migrated to the agreed location.
- Shipped features >>> Migrate to the documentation website
- WiP features >>> Migrate to existing GitLab issues
- Opened features >>> Migrate to new GitLab issues
List of Aha! features
-
DLM features https://oecd.aha.io/bookmarks/feature_grids/6817764187617495196?product_id=DLM -
DE features https://oecd.aha.io/bookmarks/feature_grids/6817765144576994702?product_id=ONEDATA -
CORE features https://oecd.aha.io/bookmarks/feature_grids/6817767162202419363?product_id=CORE
List of Aha! Ideas
Other types of contents
-
Product vision, personas, user journeys
Roadmaps and leftovers
-
Matrix of .Stat v7 features and availability in .Stat Suite (05/04/2018) Matrix_of_.Stat_v7_features_and_availability_in_.Stat_Suite_v8.xlsx > to migrate here
Internal (and community) strategy for decommissioning
-
Add in the documentation website a clear reference to the backlog of features (prioritized) and the release(s) (proposal to put it along with the flight-planner). -
Communication with SDD/PB and SIS-CC community once the migration is complete -
Remove Write access and keep Read access to Aha's products (by 'decommissioning' the 3 'Owner' roles (to communicate with DKI))
Edited by jean-baptiste nonin