-
Notifications
You must be signed in to change notification settings - Fork 25
Retrospective (and more) action items
Jerome Lee edited this page Sep 7, 2022
·
39 revisions
- Schedule discussion on how to transition tickets from Design -> Quality -> Dev (Jerome, maybe use Quality sync)
- Planning Discussion about tech needs for any implementation effort (Tif)
- Plan for Mini Kickoffs whenever dev begins work on a new functionality (Jerome)
- Revisit Brown Bag Schedule, Dio on tap for part two of his DevOps presentation
- Complete Comms Exercise with Team on 09/07/2022 (Team)
- Allow the team to cycle the environment variables/logins. Tif will let the team know when that is available. (Tif)
- Design: Document Validation Examples in Figma (Jenn to write issue)
- Design: Document in Wiki Page key design areas within Figma (Jenn to write issue)
- Team: Reflect on a memory from your time with the eAPD team to share during standup
- Schedule team building exercise (Jerome)
- Review Cypress 10 video on Component Testing / CodeCov (Darren)
- Review Chromatic license purchase pending meeting with Vidit (Tif)
- Review Bug Template to determine if we need to add a checklist item for writing a specific test for the bug being fixed (Darren)
- Rename existing test APDs to line up with naming convention from #4002 (Dio)
- Extract 4 APDs from #4002, the 0 activity APD from Ty, and merge with existing seed APD to make 6 different test APDs (Tif/Dev Team)
- Create issue for exploring Cypress component testing (Darren)
- Follow-up with Vidit on next steps for tooling/GH (Jerome)
- Figure out ownership of Figma + Akua (Jenn)
- Develop process for what documentation goes where (Wiki or Google Docs) (Leads)
- Clean up Dev Portion of Wiki Page (Dev team)
- Archive what is not need in Google Drive (Team)
- Update onboarding document for more general purpose (Jerome + Team)
- Next Design Sync: Discussing how to bring QA into the Design Process (Jenn)
- File Uploader preview to share with CMS Design System (Ty/Akua)
- Spin up bug related to spacing between fields in Personnel Field (Jerome/Tif)
- Update PR template to ensure tags are properly used for generating changelog (Tif)
- Reviewing cadence for implementing design system for review (Dev, Chromatic needs implementation first)
- Document decisions in GitHub; may require transferring summary from Slack (team)
- Ensure approved design is represented in final dev ticket (design/dev)
- Bring back Brownbag meetings (Jerome spin up issue)
- Review/Revise Templates (Design/Dev/DevOps)
- Conduct Comms preference exercise next week (team)
- Spin up next Mural board for 03/22 to allow team to async add content
- Wait till vulnerability scans are complete before releasing 4.0.0
- Plan for quarterly table top exercises (ticket to be spun up for Bill)
- Conduct after action report on latest downtime
- Try to address GitHub Org level issues with Cypress Dashboard (Nick)
- Try to obtain Mural licenses for team leads + design team (Nick)
- Switch office hours to once a month cadence / CMS takes over invite (Jerome)
- Reach out to additional MES team members to provide training / information sessions to eAPD team (Jerome)
- Determine when/how to hold a incident retro (Bill)
- Team discussion for next office hours (Jerome + team)
- Schedule time to discuss feature flags/feature branches
- Review retro template (Jerome)
- Design Debt: Work with Tif to align storybook to Figma
- Design Debt: Reorganize current implementation design with future MMIS work + Figure out how to organize features that span multple pages
- Design Debt: Archive "obsolete" designs
- Setup time to go over ZenHub Pipelines and how we use the board (Jerome)
- Document Coding Standards and Patterns, including testing + Cypress tags (Tif)
- Figure out how to do parallel cypress tests (Bill + Tif)
- Review release process + responsibilities (Team)
- Write ticket to update local build documentation (Tif)
- Setup time to go over scenarios that may come up during on call situations
- None
- Reschedule Retro (Jerome)
- Schedule time to discuss better documentation for design decisions
- Team lead discussion for documenting review process
- Using a sense of being overwhelmed as a discussion/catalyst for discussion.
- Parking Lot: ID team members who need to participate in parking lot discussions; Facilitator to assist
- Schedule Quarterly Check in on Roadmap (Jerome)
- Dev Sync will be used to review Design Issues ready for Dev + Create Dev Tickets as appropriate (Dev Team)
- Updating Change Log in the Wiki: https://github.com/CMSgov/eAPD/wiki/changelog (Team)
- Planning for the eAPD Review learning session (Jerome)
- Research Spreadsheets around MDBT
- Setup Dovetail for capturing general user feedback (Akua)
- Explore how to use Wiki to track releases (Dev Team)
- Review Vulnerabilities Wiki Page (https://github.com/CMSgov/eAPD/wiki/Development-vulnerabilities)
- Find time to discuss how Validation designs fit into future development (Team)
- Document External Dependencies (Bill)
- Evaluate/Remove legacy/old unused code (Tif)
- Find a new time for retro (Jerome/Tif)
- Team communication exercise to interns (Tif)
- Jerome to press button for releasing version 3.0 to production
- Keep/start pre-grooming tickets in dev and design sync. Leads will come together with Jerome for refinement ceremonies.
- Address warnings / errors in the react console
- Try auto-merging dependabot warnings
- Parking lot time should be used for unblocking > solutioning, with some exceptions as needed and time allows or doesn't allow, or if there is a whole team topic that needs discussion. ongoing
- If solutioning on a zenhub issue is needed, it should be done in a separate meeting with the folks who need to work together on an issue. That can be held in parking lot time if no other parking lot topics need to be discussed. It is not expected that the whole team remain on the call. ongoing
- Add a Ready for QA pipeline in zenhub completed
- Add a Blocked pipeline in zenhub completed
- Hear more on Risk Based Testing potentially during Cake Layer 2 kickoff
- Review open issues that have been long standing during backlog refinement/sprint planning. If appropriate, we may need to split up issues into more manageable chunks of work. It's also OK to keep as is -- if appropriate. - ongoing
- Product and design lead to write up agreement for team sharing. In PM's absence, temPM/Design Lead will write up and share out to the team for editing and comments. waiting for Jerome return to finalize
- Put a regular leads meet back on the calendar in progress
- Have a team working agreement workshop - completed 4/30
- Continue onboarding new team members - including sharing out the roadmap as part of Cake Layer 2 Kickoff
- Revisit the team working agreement exercise completed
- Solidify QA workflow completed
- Continue reviewing issue templates completed 3.5 Issue template for bugs/defects to include reproduce-ability completed
- If only one person can reproduce an issue, it might not be a priority (check with product, use "hard to reproduce" tag if appropriate) ongoing
- If there's question on impact, scale, priority of an issue, confirm with Product ongoing
- Can probably drop front-end label/tag completed
- Consider changing the time of team design sync waiting for Jerome return
- Find alternative ways to recruit for research sessions than the all states list serve completed
- Make sure issues that get auto-added to multiple sprints are addressed in some way - potentially in sprint planning ongoing
- Extend parking lot time 15 minutes to allow for more discussion completed
- Create issue for conducting Table Top Exercises for Go Live completed
- Be more mindful of scheduling in general, to help alleviate distractions
- Follow up with QA on the vision of implementing QA best practice for our team
- Consider breaking out bug template from dev template -completed Team opted not to do so for now, but rather use existing Dev template as suggested
- Write articles of our experience in the areas of Design, HCD, and Tech - In Progress
- Identify Tech Debt assessment criteria similar to bugs
- Limit use of yellow - completed on 12/15/2020
- Revisit working session/possibly conduct retro during working session - completed in January 2021 by moving Retro to Monday's working session
- Possibly reschedule retro - completed in January 2021 by moving Retro to Monday's working session
- Leverage existing processes such as backlog refinement and sprint planning to assess opportunities to split issues to epics ongoing
- Follow up on improving weak emoji game in CMS Slack- completed on 08/28/2020 via adding all of emojis that the team has identified in 18F Slack to CMS Slack
- Revisit Roadmap as a team - completed on 10/29/2020
- Add Testing as an upcoming working session topic- completed on 08/11/2020 via updating 08/17/2020 working session agenda
- Revisit template use now that ZenHub has been migrated to CMS - on hold
- Update team on next retro format as well as proposed cadence of retro format variation - completed on 07/27/2020 via working session
- Schedule 25 mins of working session time to discuss and experience a screen reader - completed on 07/13/2020
- Spin up issue to initiate Release Strategy discussion- completed on 07/01/2020
- Share path forward regarding conveying urgency or the lack thereof with entire team - completed on 06/16/2020 via Slack update
- Update future retro meetings' time - completed on 06/02/2020
- Track action items and status in a manner in which the team is full aware - completed on 06/02/2020 via creation and ongoing maintenance of this page in the centralized team Wiki
- Create Effective Issues - completed on 11/03/2020- Jerome to review Dev and Design templates proposed by Team Leads
- Communication exercise - completed on 06/01/2020 via Mural
- Mindful about breaks - ongoing - breaks are being offered during meetings which are scheduled longer than 1 hour as well a breaks in between meetings when schedules allow
- Resolve pr approval bottleneck - completed on 7/22/2020 - Team composite has been modified to support pr approval
- Balance design strategy with upcoming update experience layer - completed on 7/23/2020 - Jenn and team has completed foundational cake layer 2 user research and updated/presented the modified roadmap based on that feedback on 7/23
- Team Working Agreement
- Team composition
- Workflows and processes
- Testing and bug filing
- Accessing eAPD
- Active Documentation:
- Sandbox Environment
- Glossary of acronyms
- APDs 101
- Design iterations archive
- MMIS Budget calculations
- HITECH Budget calculations
- Beyond the APD: From Paper to Pixels
- UX principles
- User research process
- Visual styling
- Content guide
- User research findings
- eAPD pilot findings
- User needs
- Developer info
- Development environment
- Coding Standards
- Development deployment
- Infrastructure Architecture
- Code Architecture
- Tech 101
- Authentication
- APD Auto Saving Process
- Resetting an Environment
- Hardware Software List
- Deploying Staging Production Instances Using Scripts
- Terraform 101 for eAPD
- Provisioning Infrastructure with Terraform
- WebSocket basics
- Operations-and-Support-Index
- Single Branch Deployment Strategy
- Ops and Support Overview
- Service Level AOI
- Incident Response Plan
- On-Call Policy
- Infrastructure Contingency Plan
- Updating CloudFront Security Headers
- Requesting and Installing TLS Certificates