Overview
Background
...
Goal | Metric |
|---|---|
Recommended AD list provided to CCH end-users based on account industry information. Restricted to ADs in shared lists and/or builds. | Percentage of users who view recommended ADs list. |
Recommended AD list provided to CCH end-users based on account affiliation information. Restricted to ADs in shared lists and/or builds. | Percentage of users who view recommended ADs list. |
Recommended AD list provided to CCH end-users based on account state-agency information. Restricted to ADs in shared lists and/or builds. | Percentage of users who view recommended ADs list. |
Provide report to membership organizations what ADs are being used in shared lists and/or builds. | Percentage of membership organizations who leverage report. |
Current Challenges / Limitations
...
As per the requirements below, the HubSpot data regarding Industry must be up to date for all customers in order to provide an accurate recommendation for a customer in the same industry.
Assumptions
Updates will be done in CCH in order to buy us time to get a more sophisticated solution UC 4.0
Milestones and Phases
List the project milestones along with how that milestone can be successfully measured.
...
Requirement | Importance | Status | Comments |
|---|---|---|---|
Provide a means for UCF super-administrators to specify which authority documents are recommended to supported state-agencies. | TBD | Not Started | Potential suggested solution, but engineering will consider other solutions: Option 1: create a “dummy” company per supported state-agency and create a list of supported ADs. Ensure state-agency identification is populated in HubSpot which will feed into the reporting engine. Option 2: create table/form … outside of CCH to allow supper admins to specify supported state-agencies and their related ADs. |
Within CCH, provide a means for the user to ask for AD recommendations (only if they have filled out Industry other than “Other” and/or specified some Associations). | P1 | Not Started | |
After the user chooses the option to receive AD recommendations, gather recommended authority documents based upon the self-identified: 1. industry, affiliation, or both OR
Send the user via email with a PDF attachment for the recommended ADs. | P1 | Not Started | The consolidated recommended ADs is based upon ADs in shared lists and ADs in builds. |
Once the email is sent, inform the user they should check their email inbox for recommended ADs. | P1 | Not Started | |
Provide key partners (ISC2, ISACA …) with report to list CCH Organizations who are members in their affiliation. | P1 | Not Started | Phase 1 will be a manually generated report out of HubSpot, Power BI, or other and sent to the partner. Phase 2 (called out in phase 2 PRD) will allow for API access. |
Provide key partners (ISC2, ISACA …) with report to list CCH users who are members in their affiliation. | P1 | Not Started | Phase 1 will be a manually generated report out of HubSpot, Power BI, or other and sent to the partner. Phase 2 (called out in phase 2 PRD) will allow for API access. |
Cost
Estimated effort to fulfill all P1 requirements:
...
Question | Answer | Date Answered |
|---|---|---|
Since we are currently not tracking which affiliations a user belongs to, how will the recommended ADs be derived? | We are tracking which affiliations users belong to. Please see HubSpot or ask Matt. | |
How do we handle new versions of ADs? | ||
Is this purely data driven or do we need maintenance aspects on the reports we send out? | ||
Frequency of reports? |
Out of Scope / Future Functionality
...