Spike: Catalog to Catalog
User Story
As a stakeholder we want a high-level overview for how catalog to catalog data feeds would work so that we understand the process of how people would interact with the different catalogs.
Background Documents
(Insert links to any relevant documents)
Acceptance Criteria
- Considers family to family mapping
- Considers Locales
- Considers Roles and Groups
- ?
Definition of Ready
-
User Story can be broken down no further -
Acceptance Criteria and Story Points are agreed upon by development team and PO
Definition of Done
-
If required, UI Mockups are created and reviewed -
Code is written with automated unit tests, reviewed, merged to master branch, all tests pass -
All UI texts are multilingual -
Manual tests in test environment are successfully performed -
Test Plan is updated -
Documentation is updated