This is the first time to realize this equation. I always know that Bad Communication is bad and can waste time and resources.
But, I never imagined it ca be that bad or it can cause this severe damage.
I’m leading an integration project where we are building components that consume a WCF Services hosted on a web server.
When we first receive the Integration Guide we couldn’t get in connection with services because the configuration mentioned in the documentation is totally different than the actual required configuration. That was the first communication problem that lasted for a while till we could receive a working configuration. The reason behind delay that web services owned for a company that outsourced a third-party to implement the services for it. So to reach the actual technical team you go through a tunnel of emails from us to the service owner then to the service implementor and back again through the same route.
After many trials to get things to work we agreed to make a 2-3 days workshop to solve issues face-to-face. That was after 2 months of project kick-off. It was the first time for the service implementor to hear from the real service user.
The outcome of the workshop was my recommendation of writing a proper documentation since that service implementor wasn’t ready to do any further modification and updates because for them the project is ready for sign off and we are the only impediment.
After that workshop we tried to reach the technical team again but we failed. Again, raising issues consume very long time.
After two months of the first workshop we decided to have another workshop in our location this time.
The first shocking surprise was… We are testing a different service!!! The endpoint url is different.
After this shock I realized that three companies wasted about four months of efforts and money while the major reason is `Bad Communication`. My company could not launch two products dependent on this integration project. Right there are other reason like lake of proper service interfaces although this also is part of communication in my opinion.
If they had a proper service interfaces, constructors and method signatures that would minimize the need for documentation.
Because, the service will be self-exploratory and here we can coin learned lessons for this experience.
“Bad communication = Great waste of time and resources”
“Integration is all about Interfaces”.
”Implementation Interfaces are part of project communication: developer-to-developer channel"