| Excerpt |
|---|
Communication between team members is the glue that makes a process, project or team successful. Umano provides insights into your teams team's online communication flow, using behavioural patterns observed via group communication channels such as Slack, Bitbucket, Confluence and JIRA. Understanding the flow of information is a primary signal of the cultural health of a team. Observing the way a team communicates online is particularly relevant for teams working remotely or that are distributed. |
The communication flow insights provided by Umano include:
...
...
| maxLevel | 2 |
|---|---|
| minLevel | 2 |
| Info |
|---|
Umano's models use Slack, Jira, Confluence and Bitbucket to obtain information on communications. |
Balanced communication
Balanced communication ensures all project members are involved in communications.
Umano determines the balance of a project's communications by looking at:
Messages sent in communication tools such as Slack
Comments in project management tools like Confluence and JIRA as well as Source code management tools like Git and Bitbucket
Umano considers a project's communications to be balanced when all project members contribute to a project's communications equally on a given day, resulting in a 100%.
What’s included?
Each model looks and specific activities within the tools. Below a list of activities that contribute to Balance of Communication and activities that do not have an impact on this metric.
Included | Not included |
|---|---|
All messages in public channels in Slack Comments on Jira tickets, Confluence pages and Bitbucket PR's | Direct messages or private channels Creating or editing Jira descriptions, custom fields, labels etc. Creating or editing Confluence pages Creating or editing Bitbucket PR descriptions Any communication from people outside of the linked team members. |
Tips for achieving balanced communication
| Tip |
|---|
Follow up in writing after a face-to-face conversation. It will not only help to document decisions but it will help with tasks ownership too. |
| Tip |
|---|
Ask quieter team members for their input with specific questions rather than a generic "@here" or "to all". |
Responsiveness
Responsiveness of Communication measures the time in hours, taken for a team member to respond to a request of them.
Umano determines the speed of a project's communications by looking at:
The time between questions and answers sent in communication tools such as Slack
The time between questions and answers sent in project management tools like Confluence and Jira
What’s included?
Included | Not included |
|---|---|
All messages in public channels in Slack that have a questionmark '?' and mention a team member '@name', Comments on Jira tickets, Confluence pages and Bitbucket PR's | Direct messages or private channels Creating or editing Jira descriptions, custom fields, labels etc. Creating or editing Confluence pages Creating or editing Bitbucket PR descriptions Any communication from people outside of the linked team members. |
Tips for quicker responses
| Tip |
|---|
Include a check in your daily stand up if anyone is waiting on a response from one of the team members. Especially if there is a lower score (for the previous day) |
| Tip |
|---|
With the wide range of tools, most teams use it is not strange that notifications can get lost. Keep a personal record for pending answers. |