What do you do if your large-scale System Development project is plagued with complex conflicts?

Importante sempre que problemas foram encontrados nos projetos se criar uma lista do que está acontecendo e quais os causadores, porque isso vai sendo atualizado e facilita a visualização para ser resolvido.

When faced with complex conflicts in a large-scale System Development project, it's crucial to address them promptly through open communication, stakeholder collaboration, and proactive conflict resolution strategies. Establishing a dedicated conflict resolution team, conducting regular status meetings, and implementing agile methodologies can help identify and mitigate conflicts early on, ensuring project success.

Conflicts depend on the type of issue. It's most important to determine if there are internal team conflicts (personalities, skill sets) vs. project related issues. Personal conflicts need to be dealt with quickly, especially if there are substantial disagreements and personal issues as they can plague a project and deliverables if allowed to fester. If needed, resources may need realignment. On the project side, it can be a supply and demand issue, such as lack of tools, other projects causing too much impact, etc. These need to be looked at as PM issues from the schedule down to resource assignments to prevent a ripple effect. The PM must re-eval deliverables, goals, schedule & costs and get help if needed.

If you have the entire scope of the project and even having that you always will confront issues, so prepare for what could come and this is after you analyze what it could give you any issues.

Identifique a natureza dos conflitos: Comece identificando os diferentes tipos de conflitos que estão afetando o projeto. Isso pode incluir conflitos de interesses, de personalidade, técnicos, de recursos, entre outros. Entender a natureza específica dos conflitos ajudará na elaboração de estratégias para resolvê-los. Reúna todas as partes envolvidas

There is no substitute for clear and concise communication from the stakeholders, PM and team members. Finding the best methods that work with the team while producing as expected requires everyone be 'on the same page'. One problem area I see often is a lack of direction between stakeholders and PM's - the end goal and deliverables need to be well defined. Without this, the team can become rudderless and goals not met.

Im going be sincere it’s very difficult sometimes to communicate but you need to if it’s will it’s a way. Talking with you team all the time is good although if you see things need to be just go with flow.

Importante sempre estar alinhado com seus pares e stakeholders sobre os impedimentos que estão acontecendo no projeto para manter a comunicação clara e todos cientes dos andamentos.

In any project, everyone has a stake. For success, it requires that goals and deliverables are understood and can be met. When it's not clear in the execution, a cascade effect can occur. Direct interaction with everyone involved should be often - sometimes by just walking around, sometimes having a coffee. Larger groups require a bit of finesse - it's never advisable to 'gather the crowd' since involvement varies. Small meeting groups work well. If there are issues in goals and direction, sometimes rolling up the sleeves and getting the right people together can help mitigate. This is particularly important when members have issues with goals.

A medida que vai avançando nas complexidade do projeto ou dos projetos é importante deixar documentado os passos que foram tomados e as soluções desenvolvidas, para com isso facilitar da próxima vez que o mesmo problema for encontrado.