Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
This task affects the entire platform
User story
As a user, I want acronyms to be spelled out on each page, so that I don't have to look up what acronyms mean or navigate the platform without a full understanding of the pieces of information being requested or organizations involved.
Acceptance criteria
Given a user is navigating the platform, when they reach any page, then any acronyms that they encounter will be spelled out on first mention followed by the acronym letters in parenthesis.
Given a user is navigating the platform, when they reach a form, then any acronyms that they encounter on a form will always be spelled out.
Exceptions to the rule to explore:
Are there any acronyms that are less well known that should be spelled out always
Are there instances where we don't need to spell out the acronym on first mention if it is spelled out in a form context just below the intro text?
Once story refinement is complete and the story has been brought into the current sprint, team members should create task issues and add links to those tasks.
Epic
Epic issue includes overview, complete list of user stories, technical and content requirements, user testing task ideation, and current design mock-ups.
User story
Acceptance criteria
Exceptions to the rule to explore:
Existing platform acronyms include:
Story refinement
Technical tasks
Once story refinement is complete and the story has been brought into the current sprint, team members should create task issues and add links to those tasks.
UX
Front end
Back end
Data