This page includes links and highlights to all the major artifacts required from the product team’s perspective as to what needs to built and the rationale behind it, but not “how” things should be built. The “how” is in the hands of engineering creativity.
User Story Map
The user story map shows the journey a user will take when performing tasks within the Unified Compliance web application.
Read the story map from top down and left to right. The major activities are listed on top, broken down into tasks, then sub-tasks. The intent is to capture all of the tasks a user might take which is then graphically pictured in mockups and verbally communicated in the product requirements document (PRD) and stories.
Each sub-task is categorized into one of three values:
Delighter = functionality a customer would be happily surprised to see. These can be thought of as differentiators.
Satisfier = the more of this type of functionality, the happier they will be.
Basics = the customer expects to see this type of functionality. If it is NOT included, the customer’s dissatisfaction with the solution increases.
Wireframes and Prototypes
Wireframes and prototypes are mostly completed in Figma.
The below prototype is a work in progress.
Product Requirements Document
The product requirements document details all the backstory as to why this project is important and lists the requirements in detail.
Once the PRD is in place it will be linked here.
Epics
Epics describe the high-level requirements that are slated to be completed for this project. Epics are further broken down into stories which can be completed within one sprint.
Stories
Stories describe the more granular level requirements which can be completed within one sprint.
Other Information
Third-party dictionaries in initial scope:
Oxford
Merriam Webster
Cambridge
Free Dictionary
Compliance Dictionary (Unified Compliance)