Overview
Background
Objective
Make the Authority Document search and selection process faster by allowing users to tell us a little bit about themselves and their company in order to propose a set of authority document which may be of interest to them.
Personas
Self identification will typically happen at the sign-up phase. The user signing up mostly is any of these roles:
If a user is already signed up, the selected industry can be changed by the owners/admins of the workspace. These typically will be any of the first two roles above.
Success Metrics
List project goals and the metrics we’ll use to judge success.
Goal | Metric |
|---|---|
Current Challenges / Limitations
The current Common Controls Hub (CCH) search functionality is confusing for customers to locate authority documents which are important to them.
Customers typically use three tools (CCH, Research, and the internet) to search for and confirm the ADs that are of interest to them.
Benefits
Vastly increase the time-to-value and user experience, by providing a proposed list of ADs based upon an 80/20 rule (i.e., propose the top 80% of ADS that others use in that industry).
Subscription / Pricing / Billing Impacts
Describe any financial impact this product will introduce (if any)
Beta and Early Access
Describe if beta customers and/or early access is essential for success. If betas are required, there could be a substantial recruitment process required which needs to be anticipated and planned for.
Risks and Assumptions
List any risk or assumptions you have about the users, technical constraints, business goals …
Milestones and Phases
List the project milestones along with how that milestone can be successfully measured.
Number | Description | Success Measurement |
|---|---|---|
Product Requirements
Describe the product requirements that will fulfill the underserved need(s) starting off with the use cases, then specific functionality
Use Cases
Happy Day Scenarios
This is the “happy path” that includes the beginning to end steps the customer/user takes to be successful.
Rainy Day Scenarios
Here is where you describe what to do when things go wrong (e.g., user closes the browser, API doesn’t return results …)
Requirements
Requirement | Importance | Jira Issue | Comments |
|---|---|---|---|
During the sign-up process allow the customer to specify which Industry their company most closely aligns with | HIGH | ||
During the sign-up process allow the customer to specify which memberships they belong to (e.g., ISACA) | |||
During the sign-up process allow the customer to specify which State-agency they work for (e.g., Alabama Department of Education) | |||
Propose a list of ADs based upon the industry self-identification. | |||
Propose a list of ADs based upon memberships self-identification. | |||
Propose a list of ADS based upon State-agency self-identification. | |||
Open Questions
List any open questions that come to mind throughout the lifecycle of this project
Question | Answer | Date Answered |
|---|---|---|
Out of Scope / Future Functionality
List the known features that are out of scope for this project or might be revisited at a later time.
As is case with the assumptions, it is important to list these out so that architects and engineers can plan accordingly for these later updates.
Impacted Product Components
If this project is a component to other areas or an update to an existing product, specifically call out where this product will interact with other areas.
User Interaction and Design
As soon as user registers, they go through a simple self-identification page with minimal friction.
The user chooses which industry best fits their organization or chooses other.
Once user is signed up and self-identifies which industry they are in, the call to action (CTA) is to setup their compliance portfolio.
Based upon their industry self-identification a list of regulations / frameworks are proposed which they can add to their compliance portfolio (AKA List).
Process Flow Diagrams
Links to user journeys, process flow, or other diagrams related to the requirements.
Guides
If there are UI components to this requirement, list the main areas where interactive user guides would be needed.
Additional References
List and link to any other reference sites, documents … that might be important to the reader.