I want to have one place to check existing and proposed error messages
So that I can QA our products more efficiently
Background Context
Right now, error messages are spread across various sources, from Github developer docs, to Github CSoT (and in within different areas of the CSoT documents), to multiple screens in FIGMA. There isn't one clear working source of truth for our error messages. Determining one best place to document errors will make it easier for the team to develop and QA our products.
Outcome, Success Measure, KPI(S), and Tracking Link
Add here
Acceptance Criteria
[ ] A single CSoT is created for each of our forms
[ ] All current error messages are captured within the CSoT
[ ] Teammates (developers), collaborators (CAIA), and stakeholders (enablement team) are able to access to the CSoT
Designs and Build Notes
Add here
Enablement team (if needed)
@jstrothman
Out of scope
Add here
Open questions
Add here
Tasks
[ ] Decide on the best way to document and display error messages
Definition of Ready
[ ] Clear value description
[ ] Testable acceptance criteria
[ ] Estimated to fit within the sprint
[ ] Dependencies and blockers linked
Definition of Done
[ ] CSoT is created and up-to-date with our error messages
[ ] Access to CSoT is available to relevant parties
Value Statement
As a team member
I want to have one place to check existing and proposed error messages
So that I can QA our products more efficiently
Background Context
Right now, error messages are spread across various sources, from Github developer docs, to Github CSoT (and in within different areas of the CSoT documents), to multiple screens in FIGMA. There isn't one clear working source of truth for our error messages. Determining one best place to document errors will make it easier for the team to develop and QA our products.
Outcome, Success Measure, KPI(S), and Tracking Link
Acceptance Criteria
Designs and Build Notes
Enablement team (if needed)
@jstrothman
Out of scope
Open questions
Tasks
Definition of Ready
Definition of Done