This message was deleted.
# developer-productivity-engineering
s
This message was deleted.
🎉 5
thank you 7
j
I am curious about the Developer Champions part of the DPH framework, because it sounds like the clearest description and most connected to day to day workflow issues for your identified stereotypes (mobile, server, ML, etc.). Is there a place where team coordination issues are discussed? Because that seems like it could me more a characteristic of a team (which might have a cross-functional membership) than of a persona.
Code reviewer response time (one of your chosen metrics) led me to do a motivational cartoon advocating for synchronous paired review to avoid long cycling. Smaller, more frequent code increments is another approach to avoid stalling and merge trouble.
m
What do you mean by team coordination issues?
I’ve heard a lot of people advocate for paired review. I’ve never seen it function in a large engineering org. It definitely stops working once you have major time zone barriers. I hear lots of people say positive things about it, though.
j
Stalling on other teams, rework because of changed integration terms, choke points in flow, demands from security or compliance showing up at awkward times. Or maybe you're part of a customer integration team waiting for a bug fix or schema change. In this case the persona might be similar on a happy workflow day but pain points differ.
m
Well, that’s just organizational coordination. The only thing special about that for any team is how many interdependencies they have. It’s not so much a persona as an aspect of a project. There’s no special process for it that we own as the Dev Prod team.
j
In some sense none of these are tooling issues, but bad tooling can make coordination more difficult.
m
I could imagine bad and good ways to do it, but I would basically just be sharing my opinion, not anything empirically validated. :)
👍 1
j
OK, so the DPH framework mostly addresses unblocked workflow.
m
I think if we discovered alignment was a major issue specifically for some persona, we would try to surface that too.
j
Thank you for the clarification. Good tooling and in-team workflow is important, but at some point developer productivity and happiness hits Conway's Law issues (Team Topologies), and knowledge transfer, and those have been most salient to me.
m
But it would surface by being a pain point we discovered in the survey. If we saw it for multiple personas, we might try to address it in a broader way, across the org. I personally go to all the persona reviews, so I can deal with issues that appear in multiple places.
👍 1
Sure, I think the most important productivity issues usually lie outside of tools and infrastructure.
The catch is how well your survey instrument is designed to catch those things.
j
DPH sounds like a good place to start with providing each team member what they need.
m
Yeah. I mean, conceptually everything you’re talking about should show up in our Happiness signals. I would like to improve our survey so that it does a better job there. I have seen some in-person interviews done internally that did raise issues like this.
👍 1
j
And the Champions are less about team coordination?
m
Yeah, they are more about being advocates for the personas.
👍 1
j
More the surveys as sources for themes there.
m
The Champions do do all the survey analysis.
j
Thank you, that's very helpful.
I hear a little echo of Netflix's "guilds" notion as dispersed roles with similar interests and issues.
m
Could be! I actually haven’t read about Netflix’s thing.
j
I think NF's are self-organizing knowledge transfer and solutions providing groups around particular technical interest areas. Narrower than personas, probably, but sharing the notion of common concerns across teams.
I'm happy that you get to share your work here. Thank you again.
m
Ah, I get it about Netflix’s. My suspicion is that that sounds better than it is in reality. 😆
j
Even Netflix admits that. :)
👍 1