[fatnoah]

I've been managing for a long time, and where I always seem to land are to ask stakeholders and the engineering team what a successful engineering org looks like to them, and I start from there. The almost universal answer from stakeholders is consistency and some measure of predictability. For Engineers, it's usually consistency and feeling like their making valuable contributions and shipping products.

People tend to gravitate towards Scrum because they know it, but it's usually implemented because a process is deemed to be required, not that specific goals are trying to be met. By starting with the goals, I can at least start from a position of agreement, and develop a Scrum or other process that can provide some measure of success for stakeholders while meeting the needs of the engineers. It's also a forcing function for me to say that if you want X from the Engineering team, we need Y from you.

I'm also very upfront that a hill I'll die on is that velocities and story points are great planning tools and signals around process health, but they're never goals nor are they tools for judgement and reviews.