This is our best effort to map the pipeworks for how work comes in, where it goes, and how it should come out.
Work that comes in as a DM or an email should be directed towards a public team channel. We should queue up work in a place where the whole team has visibility. Ideally this should be a request that comes in via our org channel in either Teams or Slack. Teams; Org-devops-engineering Slack; Org-Lakitu
org-channel ->
Jira backlog ->
team review ->
If the team reviews the work and decides it is appropriate we’ll move it to
From there we’ll decide whether a Jira issue should be opened for it.
Who is responsible for accountability don’t want technical requests to come through a single individual
Consider the scope Priority list; What is the work type? Support production? lower environment? Roadmap Where does it fit into our top 5? Maintenance and Migration Innovation
direction
is it forward facing?
if a quick fix, what technical debt will it incur?
time to complete
short -> do it
long -> jira backlog
complexity
simple -> do it
other -> jira backlog
new project
to our Jira backlog >
how does it feed into a decision record?
What’s the future review process to make sure it stays on the radar?
setting a sunset date for how long this will be in place?
Monday/Friday Jira sweeps