- Chat conversation should default to the most inclusive channel to which the topic is relevant so various team members may chime in and stay up-to-date. Direct 1:1 messaging between individuals is okay if you’re confident the conversation would not be helpful to others.
- OFA TDP General
- OFA TDP Dev
- OFA TDP UX
- OFA TDP Product
- OFA TDP Watercooler
- OFA TDP GitNotify
- OFA TDP Merge Notify
Using Github plugin for Mattermost
- Assuming you are logged into Mattermost, run the following command in any channel or private message (it will only be visible to you):
/github connect
-
This will prompt the Github bot to send you a link to click on to authorize Github.
-
After authorizing, you will have a private channel as well as this icon summary view like seen here:
-
You can expect a daily message at 9am (configurable) to detail your work:
- Text documents, spreadsheets, and presentations should be stored on OFA TDP SharePoint (also accessible via MS Teams Channels>Files tabs). This includes ATO documentation and user research interview notes.
- Raw user research interview notes should have restricted access and only be available to the core research team. Participants should have code names and notes should be anonymized of PII after each session.
- TANF Data Portal OFA OneNote Notebook - General Team Notes
- Design> UX Syncs notes
- Dev Notes> Dev Sync Log
- Compliance> Integrated Project Team (meetings with OCIO)
- Admin Notes> System admin sync log (Alex + Thomas)
- Product> Product Sync
- Murals retained for documentation purposes are hosted in OFA's Mural Workspace. Only Lauren has member access; others can edit Murals as visitors after entering the password. Ask Lauren for the password.
- Team murals in the Raft Workspace can can be found here🔒
- The UX team creates user workflows and designs for our application in Figma. The corresponding Figma board links are included in the the tickets for the developers to use as they build.
- Used primarily by the dev team as a place to quickly meet at any time about various issues in lieu of setting up a more formal Zoom meeting. Click here to set up an account or ask Andrew Jameson for an invite.
- Sprint Summary Reports are created at the end of each sprint and added to Code<>Docs. View them here.
- Goal: To document the vendor’s work and satisfy OCIO’s requirements and share during sprint demos.
- Raft creates markdown file covering all the sprint’s work.
- Contains sprint goals, accomplishments, and issues by status (with #s and URLs)
- Closed/merged (Done/Demo, Closed)
- Submitted (QASP Review or OCIO Review)
- Moving to next sprint (Raft Review, In progress, Current Sprint Backlog)