Ops/Delivery and Saas/Delivery name clashes
Problem
Delivery is being used at least in two, conflicting ways across the product org:
- The previous "Release+Configure" stages and groups got merged and are being rebranded as the Delivery stage and Delivery group. This team is responsible for the Delivery direction
- The SaaS platform stage has a Delivery group
We should come up with easy to distinguish names for these teams (and direction).
Decision
Stage Deploy / Group Environments.
Rationale: There was agreement that the best name would be "delivery". At the same time, the Delivery group has a lot of automation built on top of their label, and "deploy" and "environments" were considered as good enough alternatives. As we are in the process or redesigning our main navigation to better suit personas, "deployments", "environments" and "operations" often came up as descriptive menu names for the features the combined team delivers. Overall, we agreed that "deploy" and "environments" are descriptive names for our users.
Previous proposals
Proposal
- No change to the SaaS Platform (internal) stage and the Delivery group.
- Remove the Release and Configure stages
- Create the Deliver stage
- Create the Application Delivery group under the Deliver stage
- Create the
~group::app delivery
label for tracking - Create
#s_deliver
and (later if we grow to multiple groups)#g_app_delivery
Slack channels. Note that there is a#g_delivery
channel already.
came later)
Alternative (- No change to the SaaS Platform (internal) stage and the Delivery group.
- Remove the Release and Configure stages
- Create the Ship stage
- Create the Environments group under the Ship stage
- Create the
~group::environments
label for tracking - Create
#s_ship
and (later if we grow to multiple groups)#g_environments
Slack channels.
Alternatives considered for the new stage and group name
I mention the biggest counter-arguments together with the proposals
- Release - If we simplify the infinity-devops sign and leave out deployments, it would be hard to argue that we are a DevSecOps platform. We plan to focus mostly on the deployment aspect of delivery first.
- Configure - The word in itself has nothing to do with delivery and it would likely not help our customers to understand that it's about delivery.
- Environments - Would be perfect, but we need a verb.
- Deploy - This excludes release, the most important aspect of delivery, making the product available to users. It would result in a half-baked messaging to our users.
- Orchestrate - the Delivery group already has an Orchestrate/Sytem team-split internally