I've been brought into an organization to improve their Release Management. A couple years ago they went through a transition to Agile development. I have two work streams: Run & Improve.
Boots on the ground (Run) my release management team is ensuring sprints run on time, that user stories are in Azure DevOps, sprint & increment planning is generally done, etc. We're keeping things moving the same way it was when we arrived.
Higher level (Improve), my manager would appreciate a roadmap for improving things. I'm collecting data on each team and how they run their sprints (writing features/user stories, grooming (or lack thereof), sprint planning (or lack thereof), etc.)
So, I need to assess the health of the engineering process as it currently is and make recommendations for how to get it to a better state moving forward.
For context, one team does grooming weekly. Their stories are well written, with all criteria included. They are prioritized but do not include work effort needed, so I've observed many stories carry over to future sprints.
Another team (who adds upwards of 10 stories a day) does zero grooming, has poor story development (often with missing criteria) and does all of their sprint planning in one large meeting. They also include detailed work effort at the task level, so their estimates for workload have been generally accurate.
Other teams are similar to the above.
My question is, what assessment/analysis methodology would be best for this need? I.E. It's not a "5 Whys", but perhaps "SWOT"? Something else?