I felt that yesterday there was a small amount of disagreement about the team's scope. Getting that ironed out should be the first step! If you fundamentally can't agree on that, that's okay, because you can split into smaller, more tightly scoped teams that work very closely together. You'In fact, if you do it right, other teams won't even know! For example, we've already done that splitting in Mobile Apps, as we have separate iOS and Android engineering sub teams, as part of the wider Mobile Apps team. This was done, in part, to combat the perception that engineers can easily hop between platforms, so that they have time to focus on a single platform and not get distracted. But you wouldn't know this from the outside!

Then it's about rejecting work that's outside the scope. In Mobile Apps that's a team-level decision, not a director-level one, but that's only possible because as a team we're all in total agreement on our team scope. So, first things first, get the scope agreement.

Just my opinion. Hopefully it was helpful.

Dan