Rather than having each team discussing the setup, we define areas of responsibility that can discuss the setup for each area. This way we can ensure that each area is represented in the setup and that we can have a conversation focused on that area's need rather than discussing entire processes and methodologies. We not only define the areas, but we also color mark the areas to make things like issue types visually recognizable in the setup. In our Build setup, we have the following AOR's: Management - Teal Requirements - Blue Design - Purple Development - red Test - Orange Operations - Yellow The main benefit of this is to ensure that the right groups only can discuss the setup of their assigned items, while at the same time have the opportunity to discuss improvements as a unified workforce rather than as individuals or teams. This ensures that improvements can be made quickly and be done for all teams. This prevents fragmentation of the setup and encourage collaboration for all teams and groups across the AOR.
