This How-To details how to engage with the Product Committee to define a new product reference use case or change an existing one. For the purposes of this document, submitting a new product use case and submitting a change to an existing product use case are synonymous.
Submit - Contact the Product Committee on Slack or email (firstname.lastname@example.org) to submit the product reference use case. Note the Product Use Case Template that page defines the type of product reference use case that the GovStack is looking for as well as the structure to follow, if possible. Note that the product use case template is still being drafted and the current document is still under discussion
Evaluate - Once received, a member of the Product Committee will be assigned to review the product use case. The person will evaluate the use case and share a recommendation about whether it should be incorporated at the core level during a Product Committee meeting
Track - If the product use case will be incorporated, a Jira task will be created to track any related work and a new product use case draft created on Gitbook
Discuss / Work - The product committee (and optionally any required SMEs from the technical committee) will review the product use case and draft either a new product use case or changes to an existing product use case. The document status is initially set to Drafted and then Review once the changes are ready to review. Collaborative editing will be done on Gitbook in document drafts
Approve - Once the draft changes are complete, the product and technical committees will review the addition/changes and, once satisfied, approve them. The status of the product use case document will be changed to Approved
Handover - The technical committee will take product use case and create or update the technical specifications for any affected building blocks
Publication - Approved product use cases will be published once the building block work is completed as part of a GovStack release