2023-03-01 - Product Committee

Presenter

Time

Notes

5 min

@Steve Conrad @Wes Brown @PSRAMKUMAR

35 min

TECH-206: Specifications Release v1.0In Review

Next Steps:

1. Define content format (Steve) - Proposed

   1. Currently gathering feedback on draft format, setting a deadline of Friday

2. Capabilities

   1. Need to decide where Capabilities/Workflows live. Are they connected to BBs or separate?

      1. Wes - This will not be included in the 1.0 specification

         1. Use cases, example implementations and specifications is what will be published.

   2. Taylor - Previous standard for the use cases was to first review capabilities outlined in a use case and identified functional requirements.

   3. Ramkumar & Sarah - we should find commonalities across use cases - create a linkage. These capabilities/workflows are reuseable and will be moving forward.

   4. Ramkumar: one could configure workflow inside a building block.

      1. Wes: different capabilities still required across use cases i.e. with registration the content required can be different by use case.

3. Align BB specs to format (Valeria) - TECH-426: Update specs to be consistent for Version 1.0 releaseDone

   1. Tagging responsible parties for questions/comments on Gitbook.

   2. Date to finalize this format by Friday (March 3rd).

4. Internal tech edits/reviews as needed - (Ramkumar)

   1. Can we make a distinction between “content” and “formatting” changes in Jira tasks?

      1. Tag or other easy way to be able to filter/prioritize the tasks

5. Small review team to approve (Wes) - Who?

   1. Once changes to format have been made at the technical level, then final approval needs to be done by diverse representatives working on GovStack

      1. Potential individuals: Wes, Steve, Ramkumar, Nico, Vikash (@Wes Brown to get confirmation from Yolanda for country engagement representative)

      2. Reach out to Jake, Margus, and Yolanda

@Wes Brown

5 min

Status Update

• Review EPR Use Case (PRD-112: ENV-1 (EPR): Stage 9.3 - Create Use Case document with logical stepsProposed )

  • Goal is to incorporate feedback received today from Yolanda.

• Setup Online Construction Permit Tasks (PRD-115: Create Epics and Tasks for Online Construction Permit Use CaseAccepted )

• Compile Online Construction Permit Documents (Epic Required)

• Identify/Invite Country Representatives (PRD-117: Identify Country Representatives for Use Case FeedbackDone )

@Wes Brown @Shukla, Ayush

10 min

Question

Is a “live” document really needed as opposed to a high-level document detailing where content is located? The upkeep for a live document is significant and the page(s) will quickly grow to be difficult to consume. Can we instead rely on search?

Current Doc: https://docs.google.com/document/d/1G4md2h6eiSjwWp2Qlb8o-a-5Gwzm64PinWeY0W1ZCAo/edit