Multiple Teams can have multiple processes and systems for what they do.
This isn’t a bad thing – build the process, methodology or system that fits the team for what they are doing.
The Agile methodology for software is built around tenets to accomplish goals and not implementation details itself.
If you are working with multiple teams with multiple ways of doing things and each team is performing well the question should be are you able to align the processes into one display of how everyone is doing – getting from comparing bananas and oranges to applying that are honey crisp, McIntosh, granny, etc (I hope this analogy makes sense).
What matters most when you have multiple teams with multiple processes is knowing what metrics you want to get out of each team. If they can’t get you the metrics, then there’s a problem, if they can, is there still a problem?
Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US). I’m also the co-host of the Remotely Prepared podcast.