From dbfe8995dff77f22e2f18cc12641782c37df5f2d Mon Sep 17 00:00:00 2001 From: Colin Murphy Date: Fri, 5 Aug 2022 14:44:47 -0400 Subject: [PATCH 1/9] Create a Project README --- docs/product/18FBuild_README.md | 39 +++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 docs/product/18FBuild_README.md diff --git a/docs/product/18FBuild_README.md b/docs/product/18FBuild_README.md new file mode 100644 index 000000000..5f6060ad7 --- /dev/null +++ b/docs/product/18FBuild_README.md @@ -0,0 +1,39 @@ +# Background +CISA and 18F are partnering to build a new .gov registrar. + +# Goals for 18F Build (as of 08/04/2022) +**Primary Goal:** Replicate the necessary core functionality in a new system +**Secondary Goal:** Reduce the CISA admin burden while maintaining high security standards + +Deprioritized for later: +* Make getting a .gov domain as easy as getting a .com or .us +* Help more government entities set up and maintain their .gov site and infrastructure +* Build awareness and credibility of .gov domains + +# Milestones +_To be prioritized and posted_ + +# Considerations and Tradeoffs +## Success for 18F is... +* A new system that + * Can respond to user needs for all long term goals + * Can reduce the number of actors or decisions in a successful flow + * Upholds a security review process for getting a .gov domain + * Meets code and accessibility standards + open source policy + * Lays the foundation for a “a simple and secure registration process that works to ensure that domains are registered and maintained only by authorized individuals (Dotgov Act)” +* Supporting 1-2 registrant and admin flows with limited improvement and automation, based on value and complexity +* Has or is ready for an ATO +* Coordinating and navigating with procurement processes (RFPs and current vendor agreement) + +## Risks +* App may be supported by a combination of manual work and automation, not fully automated +* Scope creep – we build a system that can’t be ATO’d prior to June or Nov 2023 +* We build out a narrow slice of the system, which may be insufficient for all registrant and administrative use cases +* We wouldn’t be intentionally and directly focused on or prioritizing improving the registrant / admin experience + +## Example User Stories (to be prioritized) +* As a potential registrant, I want to learn what I should know about .gov so I can build support inside my organization to get a .gov domain. +* As a registrant, I need the registrar to have strong user authentication so that sensitive domain- or account-impacting actions take place post-authentication. +* As a program lead, I need to ensure that issued domains are from authentic, eligible organizations and requested by someone with authority so that domains are only given to bona fide US-based government organizations. +* As a program lead, I need to run queries on .gov data to ensure alignment with program, agency, and Congressional reporting requirements. +* As a program lead, I want to be able to send messages to individuals, groups, or all registrants so they are aware of important information: status emails (system downtime, etc.) to updates to status of an application. (PENDING, APPROVED, etc.). From e9e901fe7e1e119122a16a442d6cfd08cbf854de Mon Sep 17 00:00:00 2001 From: Colin Murphy Date: Fri, 5 Aug 2022 15:02:07 -0400 Subject: [PATCH 2/9] .gov Product Strategy --- docs/product/.gov_productstrategy.md | 36 ++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 docs/product/.gov_productstrategy.md diff --git a/docs/product/.gov_productstrategy.md b/docs/product/.gov_productstrategy.md new file mode 100644 index 000000000..0579d0d27 --- /dev/null +++ b/docs/product/.gov_productstrategy.md @@ -0,0 +1,36 @@ +# .gov Product Strategy +Purpose: Clarify our focus for developing a new .gov TLD system and align it to the needs of its users, CISA's mission and standards, and the vision for the .gov program. + +## Product Vision +_TBD - once we synthesize initial research and align as a product team_ + +## Primary, Secondary, Tertiary Users +_TBD - once we segment and prioritize all users and stakeholders_ + +## Problem Statements +_TBD - once we synthesize initial research and prioritize areas of need_ + +## Short-term Success for .gov +### Primary: +* A production-ready, modern .gov registrar that can replace the current system with improved user experience and operational efficiency + * Built in the open + * Meeting accessibility and testing standards +* A plan for developing capacity within the CISA organization going forward + +### Secondary +* Having a clear understanding and definition of current state +* A plan for new product +* A product plan that coordinates with other RFP actions + +## Long-term Success for .gov +_To be prioritized and posted_ + +## Problems .gov registrar needs to solve (now) +_TBD - once we synthesize initial research and align as a product team_ + +## Problems NextGen doesn’t need to solve (next or later) +_TBD - once we synthesize initial research and align as a product team_ + +## Risks +_To be prioritized and posted_ + From 585c8d79a77b116432fea4a4a089d053ff0828d1 Mon Sep 17 00:00:00 2001 From: Colin Murphy Date: Fri, 5 Aug 2022 15:04:37 -0400 Subject: [PATCH 3/9] Add title and rename --- .../{18FBuild_README.md => Phase1_README.md} | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) rename docs/product/{18FBuild_README.md => Phase1_README.md} (88%) diff --git a/docs/product/18FBuild_README.md b/docs/product/Phase1_README.md similarity index 88% rename from docs/product/18FBuild_README.md rename to docs/product/Phase1_README.md index 5f6060ad7..63592ef41 100644 --- a/docs/product/18FBuild_README.md +++ b/docs/product/Phase1_README.md @@ -1,7 +1,7 @@ -# Background -CISA and 18F are partnering to build a new .gov registrar. +# A new .gov system: Phase 1 +Purpose: Summarize the priorities for 18F and CISA in pursuing an initial build of a new .gov registrar. -# Goals for 18F Build (as of 08/04/2022) +## Goals for 18F Build (as of 08/04/2022) **Primary Goal:** Replicate the necessary core functionality in a new system **Secondary Goal:** Reduce the CISA admin burden while maintaining high security standards @@ -10,11 +10,11 @@ Deprioritized for later: * Help more government entities set up and maintain their .gov site and infrastructure * Build awareness and credibility of .gov domains -# Milestones +## Milestones _To be prioritized and posted_ -# Considerations and Tradeoffs -## Success for 18F is... +## Considerations and Tradeoffs +### Success for 18F is... * A new system that * Can respond to user needs for all long term goals * Can reduce the number of actors or decisions in a successful flow @@ -25,13 +25,13 @@ _To be prioritized and posted_ * Has or is ready for an ATO * Coordinating and navigating with procurement processes (RFPs and current vendor agreement) -## Risks +### Risks * App may be supported by a combination of manual work and automation, not fully automated * Scope creep – we build a system that can’t be ATO’d prior to June or Nov 2023 * We build out a narrow slice of the system, which may be insufficient for all registrant and administrative use cases * We wouldn’t be intentionally and directly focused on or prioritizing improving the registrant / admin experience -## Example User Stories (to be prioritized) +### Example User Stories (to be prioritized) * As a potential registrant, I want to learn what I should know about .gov so I can build support inside my organization to get a .gov domain. * As a registrant, I need the registrar to have strong user authentication so that sensitive domain- or account-impacting actions take place post-authentication. * As a program lead, I need to ensure that issued domains are from authentic, eligible organizations and requested by someone with authority so that domains are only given to bona fide US-based government organizations. From 216bc597fa27fb865fbf7702585ad74b71791349 Mon Sep 17 00:00:00 2001 From: Colin Murphy Date: Fri, 5 Aug 2022 15:05:09 -0400 Subject: [PATCH 4/9] Update Phase1_README.md --- docs/product/Phase1_README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/product/Phase1_README.md b/docs/product/Phase1_README.md index 63592ef41..2f08a30df 100644 --- a/docs/product/Phase1_README.md +++ b/docs/product/Phase1_README.md @@ -1,7 +1,8 @@ # A new .gov system: Phase 1 Purpose: Summarize the priorities for 18F and CISA in pursuing an initial build of a new .gov registrar. +**The below was agreed upon on 08/04/2022** -## Goals for 18F Build (as of 08/04/2022) +## Goals for 18F Build **Primary Goal:** Replicate the necessary core functionality in a new system **Secondary Goal:** Reduce the CISA admin burden while maintaining high security standards From 996276be27d775d00c6fbb30ec8d0ce177475516 Mon Sep 17 00:00:00 2001 From: Colin Murphy Date: Fri, 5 Aug 2022 15:05:38 -0400 Subject: [PATCH 5/9] Update Phase1_README.md --- docs/product/Phase1_README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/product/Phase1_README.md b/docs/product/Phase1_README.md index 2f08a30df..01690da35 100644 --- a/docs/product/Phase1_README.md +++ b/docs/product/Phase1_README.md @@ -2,7 +2,7 @@ Purpose: Summarize the priorities for 18F and CISA in pursuing an initial build of a new .gov registrar. **The below was agreed upon on 08/04/2022** -## Goals for 18F Build +## Goals for Phase 1 **Primary Goal:** Replicate the necessary core functionality in a new system **Secondary Goal:** Reduce the CISA admin burden while maintaining high security standards @@ -15,7 +15,7 @@ Deprioritized for later: _To be prioritized and posted_ ## Considerations and Tradeoffs -### Success for 18F is... +### Success for Phase 1 is... * A new system that * Can respond to user needs for all long term goals * Can reduce the number of actors or decisions in a successful flow From c7e2f20fdfe35a8ab7eeb72cb7e4bb430b1a3023 Mon Sep 17 00:00:00 2001 From: Colin Murphy Date: Fri, 5 Aug 2022 15:50:27 -0400 Subject: [PATCH 6/9] rename file name --- docs/product/{Phase1_README.md => phase_one.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/product/{Phase1_README.md => phase_one.md} (100%) diff --git a/docs/product/Phase1_README.md b/docs/product/phase_one.md similarity index 100% rename from docs/product/Phase1_README.md rename to docs/product/phase_one.md From 656740576b1ab28073eee776a10ab1caa31e14b4 Mon Sep 17 00:00:00 2001 From: Colin Murphy Date: Fri, 5 Aug 2022 15:50:54 -0400 Subject: [PATCH 7/9] Rename file --- docs/product/{.gov_productstrategy.md => product_strategy.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename docs/product/{.gov_productstrategy.md => product_strategy.md} (100%) diff --git a/docs/product/.gov_productstrategy.md b/docs/product/product_strategy.md similarity index 100% rename from docs/product/.gov_productstrategy.md rename to docs/product/product_strategy.md From 4242590b732ffb331d3ce105d5e3b0abc4cacf5e Mon Sep 17 00:00:00 2001 From: Colin Murphy Date: Mon, 8 Aug 2022 12:11:17 -0400 Subject: [PATCH 8/9] Edited Primary Goal from replicate to recreate --- docs/product/phase_one.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/product/phase_one.md b/docs/product/phase_one.md index 01690da35..ff90bcd7b 100644 --- a/docs/product/phase_one.md +++ b/docs/product/phase_one.md @@ -3,7 +3,8 @@ Purpose: Summarize the priorities for 18F and CISA in pursuing an initial build **The below was agreed upon on 08/04/2022** ## Goals for Phase 1 -**Primary Goal:** Replicate the necessary core functionality in a new system +**Primary Goal:** Recreate the necessary core functionality in a new system + **Secondary Goal:** Reduce the CISA admin burden while maintaining high security standards Deprioritized for later: From b68edfb5dcb3288deb446c4dde53fe26954db450 Mon Sep 17 00:00:00 2001 From: Colin Murphy Date: Mon, 8 Aug 2022 12:16:01 -0400 Subject: [PATCH 9/9] Updated long-term success goals and primary users --- docs/product/product_strategy.md | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) diff --git a/docs/product/product_strategy.md b/docs/product/product_strategy.md index 0579d0d27..d3b3d0840 100644 --- a/docs/product/product_strategy.md +++ b/docs/product/product_strategy.md @@ -5,7 +5,11 @@ Purpose: Clarify our focus for developing a new .gov TLD system and align it to _TBD - once we synthesize initial research and align as a product team_ ## Primary, Secondary, Tertiary Users -_TBD - once we segment and prioritize all users and stakeholders_ +### Primary: +* US-based government organizations and publicly-controlled entities who use or should use the registrar + * _NOTE: Segmenting our audience is a separate conversation and so this intentionally broad as placeholder_ +* CISA .gov administrators + ## Problem Statements _TBD - once we synthesize initial research and prioritize areas of need_ @@ -23,7 +27,21 @@ _TBD - once we synthesize initial research and prioritize areas of need_ * A product plan that coordinates with other RFP actions ## Long-term Success for .gov -_To be prioritized and posted_ +### Primary: +* Increase the number of governments, currently on non-.gov TLDs, to .gov +* Develop services to support “the security, privacy, reliability, accessibility, and speed of registered .gov internet domains” (DOTGOV ACT) +* Sustainable long-term skills and capacity to scale up the program + +### Secondary +* Increase number of domain registrations +* Reduce time to get an application approved from 20 days to 1-2 business days +* Increase the percentage of domains which resolve to content +* Reduce time to ship changes to production +* Enable the discoverability of government services to the public and to domain registrants (DOTGOV ACT) +* A “simple and secure” registration process that works to “ensure that domains are registered and maintained only by authorized individuals” (DOTGOV ACT) +* Active .gov community of practice where members ask and answer questions, provide feedback, and where CISA can communicate with all .gov domain managers +* Demonstrated commitment to working in the open +* A clear role for humans or a call center to support registrant use cases ## Problems .gov registrar needs to solve (now) _TBD - once we synthesize initial research and align as a product team_