← Data Services

Creating a new services engineering team

This is a guide to creating a new data services engineering team.

Decide team name

Be creative, have fun, be respectful.

Create Github team

https://github.com/orgs/Banno/new-team

Create k8s namespace

Add vault for the new team

See example.

Create Slack channels

  • #team-[team name] (private)
  • #org-[team-name] (public)
  • #auto-[team-name] (public)
  • Create slack group for the new team
  • Add emoji for pinging the new team
    • Command is /reacji-channeler :emoji: #channel

Create Google Group

[team]@jackhenry.com (this is the team’s email distribution list). Ask Tech Ops to create the group. They will make someone the admin. This should be the EM. The admin can then manage the members of the group at groups.google.com.

Create a Team-{team-name} Github repository

Create Jira project

  • Create Jira team, Jira group, component on OPS ticket, and Jira firefighter team. Reach out to #org-jira for this if you cannot do it yourself. The Jira teams are used to ping out to the team members on the OPS tickets, while the Jira group is used for permissions, especially around our Automation actions on those OPS tickets.
  • Create your primary Kanban or Scrum board
  • Create at least 1 Roadmap to use for status emails.

Create PagerDuty schedule and policies

This is performed by initially opening up a Jira ticket in the TechOps project.

Create a Grafana dashboard for the new team

Update Permissions Matrix

Work with tech-ops to update https://docs.banno.com/permissions-matrix/

Update domain document on wiki

https://docs.banno.com/engineering/domain-ownership/

Create team intro meeting

https://docs.banno.com/guides/how-we-work/new-hire-team-intros/

Setup Postgres access to banno_all (if needed)