“Ineffective communication is the primary contributor to project failure one third of the time and had a negative impact on project success more than half the time.” - PMI, Project Management Institute.
Communication in a projects happens in different ways (sync: phone calls, meetings or async: email, chat (I think chat is async but that's debatable (not technically, but hypothetically - wow, that's the 3rd nested bracket))). But I believe communication is more than just participating in a conversation over a medium. Imagine a continuous deployment flow where committed source codes are deployed to QA servers every 30 minutes. If a simple Slack integration generates a notification with commit messages every time a deployment is successfully completed, then a QA engineer knows exactly when and what to test at any given time. Now remove the QA engineer and imagine an automated test suite receiving a similar message and immediately starting test execution. This makes me think that a well-established communication framework creates an information network and bridges the gap between stakeholders. Note that the nodes (or endpoints) in such a communication network can be humans and/or machines.
Top comments (0)