making clear the division of roles and responsibilities, the product team should be involved in key decisions to ensure effective decision-making, their role is to define what features need to be developed, The development teams decide how to develop it, and The operations teams focus on fitting the best way to deploy the new change/feature. The product team should provide the strategic direction, If this issue is too technical for the product team, operation and R&D managers should revisit our customer and organizational needs to determine the most suitable approach. To address ongoing internal disagreements, I suggest involving HR to facilitate improved collaboration within the team, not just for this specific case.

Passe todas as funções e responsabilidades do time de dev, as mudanças esperada do sistema devem ser mediadas de forma clara para todos. Devemos ouvir todos os lados envolvidos no processo e decidir de uma forma que não prejudique as operações e forneca os resultados esperados. Realizar uma análise de causa raiz para evitar mais conflitos entre as equipes.

I used to be in that situation many times; I did the following: 1. Try to search for the shared goal and establish a ground point. 2. Identify the root cause of the conflict and set priorities. 3. Implement RCSA to these changes. 4. Assess the residual risk from both points of view. 5. Set risk appetite, risk acceptance, and key risk indicators for monitoring.

One thing I've always found useful is to understand where both sides are coming from. The developers might want to push or change something that is deemed too risky or a big change that would change how the ops workflow operates, requiring possible training. In a situation such as this it is important for both sides to have an understanding of the concerns from the other side. The developers need to be aware of how the changes could possibly disrupt the ops workflow and ops need to be aware that the changes are necessary for the system. In the end it all comes down both sides making some compromises and not having one of the sides trying to "win" the argument and having it their way.

Tout d'abord, j’organise des discussions ouvertes pour permettre à chaque équipe d’exprimer clairement ses préoccupations. Ensuite, je mets en avant les objectifs communs, tel que la livraison d'un système stable et performant, tout en conservant l’agilité nécessaire. Les décisions doicent être guidées par des données objectives, comme le taux de réussite afin d’éviter les subjectivités. Enfin, je veille à clarifier les rôles et responsabilités de chaque équipe pour réduire les chevauchements et les malentendus. Ceci permettra, à mon avis, d’instaurer un climat de collaboration et de responsabilité partagée.