GitHub Team Name Standards

Background

This card originates from the user research with the GitHub Admins- there was confusion around some of the GitHub teams and who they were/what parents team they belonged to. We need to decide and document a standard approach to how we should be creating teams in GitHub.

Proposed user journey

First we'll need to identify a good structure for a team hierarchy within GitHub. Some independent research may help with this to see how other organisations have managed their teams.

HMPPS are currently taking using the parent/child team approach.

We will also need to decide on a naming convention.

This card should be treated as a SPIKE, with a focus on the process of changing team structure/naming conventions (both the effort needed and the value of these changes). The Operations Engineering team can be used as the guinea pig for a PoC.

Approach

Research existing team structures outside of MoJ
Analyse our current estate to understand what's being done already and what areas need work
Discuss with team to decide on standards.
Document the new approach/standards

Questions / Assumptions

Q: Are we going to be enforcing this as a new standard? If so, how would we do that? A: ?

Q: Is this our responsibility? A ?

Q: Will other teams want up tampering with/dictating the structure of teams? A: Probably not.

Assumption: This will not affect the repositories associated with a team, just the team'

Acceptance Criteria

[ ] Naming convention has been reviewed and documented.
[ ] Team hierarchy structure has been reviewed and documented.
[ ] SPIKE outcome created and fed back to the team.

Reference

How to write good user stories

ministryofjustice / operations-engineering