snippetMinor
How to communicate in a multi-organization spanning project
Viewed 0 times
multihowprojectcommunicatespanningorganization
Problem
In DevOps S-Pillar of "CALMS" says that it is also about sharing knowledge.
At a present project I am working on, I am sitting at the interface between two organizations together with another "DevOps"-guy.
A lot of our time is wasted because we have partly redundant meetings (with the organization on the left side) and we wait partially longer times until somebody from the right side can assist us in solving some issue.
Sometimes I also spend hours to find out who is reponsible for getting some information for me that I need.
What would you try to address to make more sharing possible although it is different organizations that are working on that project?
At a present project I am working on, I am sitting at the interface between two organizations together with another "DevOps"-guy.
A lot of our time is wasted because we have partly redundant meetings (with the organization on the left side) and we wait partially longer times until somebody from the right side can assist us in solving some issue.
Sometimes I also spend hours to find out who is reponsible for getting some information for me that I need.
What would you try to address to make more sharing possible although it is different organizations that are working on that project?
Solution
- Establish a wiki (such as Confluence, DokuWiki, etc).
- Establish a chat/communications channel (such as through Slack or Mattermost).
- Share some code repositories (such as through GitLab, Bitbucket, GitHub).
- Share some binary repositories (such as through Artifactory, Nexus, Pulp).
- Occasionally send out a "newsletter" email that showcases what your team are trying to accomplish.
Context
StackExchange DevOps Q#12545, answer score: 8
Revisions (0)
No revisions yet.