I'm not sure you can avoid conflict! The challenge is to decide what to do so that everyone can learn, and not many people get hurt.
A well-managed team should work on its own. That is, the leading role of the team should be to create a good structure so that the team can decide priorities, methods, methodologies and even process, communicating.
So good managers will ask the team members "Okay, so what would you do?" They will then receive appropriate support for this to happen.
I would suggest that as a group you
- Get together regularly (maybe weekly) to review progress and learn about mistakes made during implementation.
- Make sure that all tasks are assigned to the team as a whole, and not to individual developers. Everyone should know a high-level job summary.
- Get together daily to take stock very quickly. Keep this meeting limited to 10 minutes.
In these meetings it is better to avoid blaming people. Instead, blame the code or process, but don't get personal.
And if your company's culture allows this, try reading some of the literature around flexible project management: there are many parts of this process that are designed to avoid this kind of conflict. However, for some organizations, a shift can be quite complex in order to give developers enough power ...
source share