This message was deleted.

there are some links in this thread which may be what you are looking for https://platformengin-b0m7058.slack.com/archives/C037XDKEDNW/p1654795922396719

You may also find value in interviewing a sample of engineers to understand their flow of work and common jobs to be done. Depending on how you track work you can cross reference opinions with data points from e.g. jira, github, etc. It's important to understand the perception of what slows people down as well as the "reality" for individual teams. Sometimes adding features to build goodwill is better in the early days.

A method we used was to categorize "chores" in the backlog as 0 point stories. This gave us a signal in lost velocity to isolate areas the platform team could automate out of the backlog

We survey 2x year around • Goals • Knowledge & documentation • Implementation • Change approvals • Quality • Deployments • Observability So that's the full devops cycle

@Michael Wood : How do you motivate and distribute engineers to take up zero point stories?

Hey, I am happy to share the survey we use. There is a sample here. I like the idea of marking Jira stories as chores. If the teams do that, it could be a very helpful dataset.

It's actually pretty seemless. We essentially work with the team on what we aim to accomplish (reducing their toil) and drive a few examples. Partnering with the PM is also a great way to get organized on stories.