Adding and revising some milestones in milestone_short_descriptions (#39

)

* Renames 'compensation' as 'incentives' in accordance with guidance from @itsemilyianacone

* Updates the status of a couple milestones, including their finished or north star status

* Replaces 'opportunity protocol' with a more expansive 'grants as a platform' milestone that includes 'opportunity protocol' as a subset

* Adds a new milestone, 'HHS-Internal-Site'

documentation/milestones/milestone_dependency_diagram.mmd

@@ -13,7 +13,7 @@ flowchart LR
 
     subgraph NOFO
         NOFO-Milestone-Planning:::executing
-        NOFO-Prototypes:::executing
+        NOFO-Prototypes:::finished
         Start-PRA-Comment:::executing
         NOFO-Prototypes-Metrics:::executing
         NOFO-Prototypes-Metrics & NOFO-Prototypes -->
@@ -32,15 +32,15 @@ flowchart LR
         NOFO-Recommendations-API --> NOFO-Recommendations-UI:::northStar
     end
 
-    subgraph User-Research
+    subgraph User Research
         Research-Synthesis
         Generative-User-Research:::finished --> Research-Synthesis:::finished
         Research-Synthesis --> ev1[Research Synthesis informs *everything*\n related to UI/UX.\nLines not shown here for simplicity.]
         Research-Synthesis --> User-Research-TBD
         Research-Synthesis --> Unified-Brand
         Research-Synthesis --> User-Research-NOFO-Writing
         Document-GrantSolutions
-        User-Research-Compensation
+        User-Research-Incentives
         User-Research-Database
     end
 
@@ -110,7 +110,7 @@ flowchart LR
     subgraph Define goals
         Define-Goals:::northStar
         Define-Goals --> Measurement-Strategy
-        Measurement-Strategy --> Measurement-Dashboard
+        Measurement-Strategy --> Measurement-Dashboard:::northStar
     end
 
     subgraph Analytics
@@ -143,10 +143,10 @@ flowchart LR
         GET-Opportunities --> AuthN-API
         GET-Opportunities --> Analytics-API
         API-Docs-Plan & Beta-Domain --> API-Docs
-        API-Plan --> API-Versioning
-        API-Plan --> Performance-Testing
-        DB-Plan & API-Plan --> Opportunity-Protocol
-        API-Plan--> AB-Testing-Plan
+        DB-API-Plan --> API-Versioning
+        DB-API-Plan --> Performance-Testing
+        DB-API-Plan & API-Plan --> Plan-Grants-as-a-Platform
+        DB-API-Plan--> AB-Testing-Plan
         ATO
         CI-CD
         API-Plan --> CI-CD
@@ -161,13 +161,15 @@ flowchart LR
     subgraph Hackathon
         Participatory-Plan
         Participatory-Plan --> Hacakthon-Page
+        Participatory-Plan --> Participant-Advisory-Councils
+        Participatory-Plan --> Participatory-Tooling
         Hackathon-Data
         Hackathon-Listing:::northStar
         Participatory-Plan --> Recruit-Hackathon-Workgroups
         Participatory-Plan --> Recruit-Hackathon-Participants
         RFI
         RFI-Tools
-        Hacakthon-Page & NOFO-Prototypes --> Hackathon-Listing
+        Hacakthon-Page & NOFO-Prototypes & Participatory-Tooling --> Hackathon-Listing
         Recruit-Hackathon-Workgroups & Recruit-Hackathon-Participants --> Hackathon-Listing
         Hackathon-Listing --> Hackathon-Apply
         Hackathon-Listing --> Hackathon-Listing-Internal-Entry
@@ -179,8 +181,9 @@ flowchart LR
 
     subgraph Communications Tooling
         Setup-Meetings
-        Comms-Platforms:::planning --> Milestone-Template:::executing
+        Comms-Platforms:::executing --> Milestone-Template:::executing
         Comms-Platforms --> Open-Source-Tools
+        Comms-Platforms --> HHS-Internal-Site
         Open-Source-Tools & Comms-Platforms --> Open-Source-Group:::northStar
         Open-Source-Group --> Hackathon-Listing
         Bug-Bounty

documentation/milestones/milestone_short_descriptions.md

@@ -275,18 +275,26 @@ This milestone is to add to that tool support for backend packages such as Pytho
 
 Based on initial research, the level of effort should be assessed to determine whether the time it would take to implement this milestone is worth the result. If it's longer than 2 weeks time of one developer, it may not be worth it.
 
-## Develop opportunity protocol
-Diagram short name: `Opportunity-Protocol`
+## Plan grants-as-a-platform
+Diagram short name: `Plan-Grants-as-a-Platform`
 
 Dependencies: `DB-Plan`, `API-Plan`
 
-Investigate whether it is appropriate to develop a protocol that is system-agnostic that describes the core components of what's contained in an opportunity. This could be shared across both federal grantmaking as well as some private-sector grantmaking to facilitate standardization and simplification. This could help bring us closer to the goal of having, for grantmaking, a version of what US colleges and universities share in their [Common App](https://www.commonapp.org/).
+Many of the most successful modern web ecosystems are design as platforms or platforms-as-a-service.
 
-The protocol would be implemented by our particular API ecosystem, but other platforms could implement the same protocol as well.
+This milestone is to design a plan for (1) considering whether that model makes sense for grants.gov, and if the answer is yes, then (2) developing a well-documented but agile-oriented plan for implementing grants.gov modernization as a platform.
 
-Much more investigation is needed to define this milestone.
+If grants.gov is implemented as a platform, then the open source framework would be something any organization or individual could use for grantmaking and/or financial decisionmaking and allocation. This provides obvious benefits to the ecosystem of grantmaking outside of just grants.gov.
+
+But selfishly, for the sake of grants.gov's core mission, designing its system as a platform would very likely make the service a more effective product, with better API boundaries and cleaner "separation of concerns" between services and processes. This approach would also likely make it easier for agencies who use grants.gov to make grants for themselves to customize their software and processes for their own needs. (For instance, while all federal agencies list all of their opportunities on grants.gov, roughly half of federal agencies use grants.gov to host the applications for their grants, and half use their own software systems. A design of grants-as-a-platform could make it easier for those external systems to integrate with grants.gov.)
+
+As part of this design and planning to complete this milestone, we should investigate whether it is appropriate to develop a protocol that is system-agnostic that describes the core components of what's contained in an opportunity. This could be shared across both federal grantmaking as well as some state, local, and philanthropic grantmaking to facilitate standardization and simplification. This could help bring us closer to the goal of having, for grantmaking, a version of what US colleges and universities share in their [Common App](https://www.commonapp.org/).
 
-For some research on common form fields, please see [this analysis from Technology Association for Grantmakers](https://www.tagtech.org/news/586811/TAG-Publishes-List-of-Common-Grant-Fields-from-FixtheForm-Analysis-.htm).
+The protocol would be implemented by our particular platform, but other platforms could implement the same protocol as well.
+
+For some research on common form fields that could be relevant to the protocol, please see [this analysis from Technology Association for Grantmakers](https://www.tagtech.org/news/586811/TAG-Publishes-List-of-Common-Grant-Fields-from-FixtheForm-Analysis-.htm).
+
+Much more investigation is needed to define this milestone.
 
 ## Plan for A/B testing
 Diagram short name: `AB-Testing-Plan`
@@ -322,6 +330,15 @@ Diagram short name: `Milestone-Template`
 
 [Link](./individual_milestones/milestone_template_published.md)
 
+## HHS NOFO transformation internal site
+Diagram short name: `HHS-Internal-Site`
+
+Dependencies: `Comms-Platforms`
+
+Create a site where HHS staff can work privately on the NOFO transformation effort, sharing resources, training, Q&As, legal questions, etc.
+
+Ideally, this would use the same communication platforms as implemented in the milestone `Comms-Platforms`. For instance, it could be a wiki directory with access restricted to HHS employees.
+
 ## Open source tools
 Diagram short name: `Open-Source-Tools`
 
@@ -609,6 +626,25 @@ Make a plan for the overall approach to participatory processes for the grants.g
 * "Hackathon" with challenge budget
 * Ongoing sprint/quarterly planning for "budgeting" software delivery based on story points
 
+## Participant advisory councils
+Diagram short name: `Participant-Advisory-Councils`
+
+Dependencies: `Participatory-Plan`
+
+Setup multiple participant advisory councils representing key stakeholders for grants.gov modernization as well as NOFO simplification.
+
+Details of this plan to be developed during `Participatory-Plan`.
+
+
+## Participatory tooling
+Diagram short name: `Participatory-Tooling`
+
+Dependencies: `Participatory-Plan`
+
+Setup and configure tooling that supports participant engagement processes, such as participatory budgeting software and processes. These processes can be used in the hackathon processes as well as potentially for stakeholder input during ongoing sprint/quarterly planning.
+
+Details of this plan to be developed during `Participatory-Plan`.
+
 ## Hackathon informational page
 Diagram short name: `Hackathon-Page`
 
@@ -1054,12 +1090,12 @@ Document all tasks that need to be completed on GrantSolutions to enable functio
 
 Document which of these tasks can be completed using APIs vs which must go through the GrantSolutions.gov user interface.
 
-## User research compensation
-Diagram short name: `User-Research-Compensation`
+## User research incentives
+Diagram short name: `User-Research-Incentives`
 
 Dependencies: `Design-Tooling`
 
-Investigate potentially setting up a system for compensation user research participants, modeled after the compensation system developed by USDS at the White House.
+Investigate potentially setting up a system for incentives user research participants, modeled after the incentives system developed by USDS at the White House.
 
 This will promote fairness, as well as increasing the quality and diversity of our pool of user research participants, by compensating participants for sharing their lived experience and expertise.