Sounds like a good idea! I like the idea of taking what’s useful from all teams and seeing if you already have the tool from one for the job of another.
You may know all of this, but I’ll say it here in case you don’t or someone else with the same question is reading:
I find that enabling process improvement is mostly about taking away the hard jobs and letting them find the way that they want to improve things. The difficulty, in my experience, is moving from ideas (which are plentiful across the land) and towards actions that improve things (which float, lonely and unseen, beneath the ocean of opinion). For that you generally need someone to be responsible for that action. Otherwise you get one of those meetings where everyone agrees what is a good idea and it’s all written down and then everyone goes back to the status quo.
Getting people to come to a consensus of ideas and build a checklist has always been the easy part, for me. Getting them to actually change is a social contract best managed or assigned responsibility in some way. For my checklist I had to point out that stories had moved without stickers a few times before it became clear that the old ways weren’t okay any more.
I predict that the meeting will bring up some non-relevant concerns to which there may be another solution or be associated with other problems. Everyone wants to be listened to, so there should be an inclusive way to accept those ideas or issues without wasting time on them. They could go in a “to discuss” pile or a vote to discuss only the most important items could render them last to talk about - a method of exclusion controlled by the team, ideally, to prevent the illusion of autocracy.
You may find, obviously, that a checklist isn’t the improvement you need. For me the list was a way of introducing an idea small enough that my team would shift to, and it was the sticker system that helped our communication and cultural ideas about tester integration. Maybe code is suffering because testers aren’t in design discussions. It’ll be something about feedback loops.
A way to iterate on a list or other device is useful. It may need maintenance - adding more items, removing redundant items, making the enforcement transparent, and discussing the perceived improvements and unforeseen costs.
Best of luck with it!