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

Version 1 Next »

This How-To details how to engage with the Product Committee to define a new use case or change an existing one. For the purposes of this document, submitting a new use case and submitting a change to an existing use case are synonymous.

\uD83D\uDCD8 Instructions

  1. Submit - Contact the Product Committee on Slack or email (wbrown@dial.global) to submit the use case. Note the Use Case Template that defines the type of use case that the GovStack is looking for as well as the structure to follow, if possible. Note that the use case template is still being drafted and the current document is still under discussion

  1. Evaluate - Once received, a member of the Product Committee will be assigned to review the 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

  2. Track - If the use case will be incorporated, a Jira task will be created to track any related work

  3. Discuss - The product committee (and optionally any required SMEs from the technical committee) will review the use case and draft either a new use case or changes to an existing use case. The document status is initially set to Drafted and then Review once the changes are ready to review

  4. 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 use case document will be changed to Approved

  5. Handover - The technical committee will take use case and create or update the technical specifications for any affected building blocks

  • No labels