Initial SETUP - Document processes and procedures of the Names Development Team

[rstens]

The following was mentioned to stop doing in a Recent Retro:

CREATE A WIKI UNDER THE REPO

• Stop moving tickets in QA without any explanation, PR#, Steps to see/find/resolve, which system, what module etc.
• Moving tickets in ready for QA, right at the last minute of the sprint
• Duplicate requests for ops tickets./ Talk to front line 
• Pure code tickets that have no impact on the App: Code review should be enough (See the code owner tickets)
• Make sure git branches and PR commits/name include Zenhub ticket numbers

The following categories need to be addressed and documented:

• [ ] How to get started with Names (Code, repo membership, teams group membership)
• [ ] Technical procedures like: PR, Build Code (local, dev, test), COnnect to remote DB, OpenShift, Google Cloud Procedures
• [ ] Timing/Rhythm of the team - When does stuff need to happen, code freezes, impact analysis, meetings, daily notification etc
• [ ] Who id doing what and who is responsible?
• [ ] How do I escalate issues?
• [ ] etc.

Acceptance Criteria

Generated by Zenhub AI

• [ ] Scenario: Documenting processes and procedures of the Names Development Team
  • Given the team's recent retro discussions are documented
  • When the documentation is complete and organized into categories
  • Then the processes, responsibilities, and escalation paths should be clear for all members
  • [ ] Scenario: Properly addressing each category in the documentation
  • Given the documentation covers each of the mentioned categories
  • When the team has access to the complete and organized documentation
  • Then the team will have a clear understanding of how to work efficiently and effectively

[rstens]

Bare bones structure: https://github.com/bcgov/name-examination/wiki