Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Overview

Background

Objective

Allow customers to confirm which industry their company is in and tell use which affiliations they belong to such as ISACA, ISC2, and HIGHTURST which will later be used in reporting.

Personas

Link to UC’s personas for the user, buyer, influencer.

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

Will quicken the pace for customers to determine which authority documents are of interest to them.

Subscription / Pricing / Billing Impacts

No subscription, pricing, or billing impacts.

Beta and Early Access

No need for full beta. Will be built into CCH as additional functionality and ideally should be tested with a few friendly customers to validate functionality.

Risks and Assumptions

HubSpot enriches data at both the company and contact level. Need to ensure the user’s choice of industry does NOT override the company ZoomInfo derived industry.

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

User is presented the Industry from HubSpot/ZoomInfo which matches their understanding and user selects a few of the affiliations they belong to.

Rainy Day Scenarios

User chooses Other for the industry which during the reporting won’t add much value.

Requirements

Requirement

User Story

Importance

Status

Comments

HubSpot data cleaned up to ensure all companies have Industry information populated from ZoomInfo.

P1

Not Started

It is a known issue that HubSpot industry data is imperfect.

Within CCH, provide a means for the user to approve the enriched industry information or choose “other”.

P1

Not Started

To buy time this will be done in CCH.

Within CCH, provide a means for the user to choose which affiliations they belong to such as ISACA, ISC2, HIGHTRUST or others.

P1

Not Started

As example, marketing already has one set up for ISC2 Form (hsforms.com)

Within CCH, provide a means for the user to confirm which State-agency they belong to. This is only provided if the user’s domain corresponds to supported state agencies.

?

Not Started

If not the domain, how else would we want the user to self-select or confirm which state-agency they belong to.

Provide a means of UCF super-administrators to identify which authority documents below to supported state-agencies.

?

Not Started

Option 1: create a “dummy” company per supported state-agency and create a list of supported ADs.

Choice of Industry will be stored on the contact information in HubSpot and optionally in CCH.

P1

Not Started

Choice of Affiliation(s) will be stored on the contact information in HubSpot and optionally in CCH.

P1

Not Started

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

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.

  • No labels