Slack Notifications

A Team Trend Summary is a type of slack notification that shows a development team's metrics, and the value changes in comparison to the previous time period. Targets are based on academic research, domain knowledge, and industry benchmarks, such as Google’s DORA metrics or the SPACE framework for developer productivity.

‍

Flow of Work‍

These insights are all about how the work gets done – Multitudes shows how quickly the team finishes work and what’s blocking or interrupting people along the way.

We show medians here as it is less likely to be skewed by outlier values, such as a specific PR with a very long wait time. We measure things like:‍

• Time to Merge: This metric is an indicator of how long it takes to deliver value to customers; it shows the time from PR creation to merge. Target: <= 24 hours

• Feedback Wait Time (e.g., Review Wait Time): This shows how long people wait to get feedback on their PRs. Target: <= 8 hours

‍

Value Delivery

‍This section focuses on the value created for customers.

• Merge Frequency: This is an indicator of how much work is reaching customers; it shows the number of PRs that teams merged. Note that we only show this data at a team level, not an individual one – that's because PRs are a team sport. Target: >= 5 PRs merged per person, per week.

‍

Wellbeing

‍These insights provide an indicator of how people are doing – are they working long hours? Does the team communicate in ways that promote psychological safety? We measure things like:

• Out-of-Hours Work: This measure shows how often people are doing work late at night or on weekends. This is individually configurable, so it can account for people in different time zones and people who do part-time work or work different hours.You can edit your working hours under Settings > Team Members > Edit profile. Target: <= 5 out-of-hours commits per person, per week.

Collaboration

‍These insights are all about how the team collaborates to get work done – who’s getting support and who’s not? Who’s doing a lot of work to support others? We measure things like:

• PR Comments Written: This shows how much feedback each person on the team gave. This helps to highlight people doing “glue” work – the people who support others. 

For more on why we’ve chosen these measures and how we calculate them, check out this blog post: What We Measure and Why.

A Team PR Alert is a type of slack notification that shows a development team's PRs that need to be reviewed.

3 day summary

You'll see: In the past 3 days: [X] PRs opened · [X] PRs merged · [X] commits done out of hours

• PRs opened: The number of PRs that were opened. This includes PRs that were opened in a in a “draft” state.
• PRs merged: The number of PRs that were merged.

• Commits done out of hours: The number of commits that were created outside of the commit author’s usual working hours as specified on the Team Settings page.

• All values are filtered for just the people on the given team, for the given date range (past 3 days).

‍

Who's most blocked

[NAME] has the most PRs awaiting review ([X] PRs)

• This person has the most open PRs that don’t yet have any “approve” or “changes requested” reviews.

‍

PRs that need to be reviewed

The following metrics only look at non-draft PRs that have been updated (edited, commented, reviewed) in the past week, to avoid surfacing stale PRs.

⚠️[X] blocked PRs

These have been reviewed and waiting to be resolved/merged for more than 8 hours.

• These are open PRs that have been updated within the last 7 days, have had an “approve” or “changes requested” review, and it’s been more than 8 hours since it was last updated. Maybe worth checking to see if it can be merged!
• The “time since last update” shows the time since the PR was last updated.
• This excludes PRs with the string “[do not merge]” in the title (case insensitive).

‍

🧐 [X] PRs are reviewed and waiting to be resolved or merged

These have been reviewed and waiting to be resolved/merged for less than 8 hours.

• These are open PRs that have been updated within the last 7 days, have had an “approve” or “changes requested” review, and it’s been less than 8 hours since it was last updated. Perhaps the reviewer is waiting on a reply?
• This excludes PRs with the string “[do not merge]” in the title (case insensitive).

‍

🔨 [X] PRs are open and awaiting review

• These open PRs were updated within the last 7 days, but are yet to receive an approving or changes requested review. A good opportunity to nudge someone to review this work!

A 1:1 prompt is a type of slack notification that shows the top 3 reflection ideas to discuss, based on a team member's data.

‍

Who is included in a 1:1 prompt? 
Anyone that is assigned to your Profile > 'Who you have 1:1s with'

When does this get sent? 
You can pick a day to receive this, at a weekly or fortnightly cadence.

How can I share this with my team member?
Once your team member has configured their Slack connection to the Multitudes app, they will receive a copy of the conversation starters. To do this, the team member must have access to the app.

Good enough depends on a team’s working patterns and human context, so we recommend comparing to your previous summaries.

If you’d like to discuss your summaries with other engineers that care about supporting healthy team cultures, you can join #share-slack-summaries in our Multitudes Community Slack.