When you grow from a small group to a larger tribe of professionals working towards a common goal, you have to start agreeing on procedures and protocols to hand over tasks between individuals and groups.
Whether you work in parallel, or in serial with other groups; whether information is exchanged frequently (agile), or handed over to another group (waterfall), you need to have clear communication standards established.
There exists a pertinent need for documented standards, which everyone involved understands and agrees to. And…it’s the agreement to standards where conflict often arises. Imagine working on standards, without the consent from all the stakeholders. Or worse, implementing standards without getting input from all parties involved or affected by the change.
One thing is clear, it is better to have some sort of standard than none. It is equally problematic to have more than one standard, with every group having one for themselves. In those situations, its a challenge for groups to adhere to a common standard, since they are already attached to the one that they created.
Yet, a common standard would eventually make it easier for all groups to work in sync, and reduce the transaction cost of information exchange. People will spend less time translating the data and/or reworking it. Consistency in information format, when coming from any group, will help make the final output look cohesive to an external agency consuming the output.
Eventually, everyone would embrace the common standard, and start to ‘love’ it…or will they!?