That burnout warning because of too many meetings is a nice idea. Sort of cool to have a manager see that without needing to see an actual calendar. That said lots of meetings may be desired depending on what they are.
However, developers do need deep work time to write code. Of course, what action needs to be taken is subjective and Middleware can only provide probable signals affecting developer's joy of building :)
Self generated reports seems like a great idea to facilitate more meaningful 1:1s. Less time spent on manually analysing team/dev manually before every meeting.
I see the Git and Jira integrations but is there something to track how certain devs reacted in times of distress and resolved a critical issue ?
Of course @greycharles! We offer tracking Mean time to resolution (MTTR) leveraging integration with your incident management tools like PagerDuty, OpsGenie, Zenduty.
Many people track DORA metrics for their teams using Middleware which consists of Change Failure Rate and MTTR calculated using your incident mgmt tool and deployment tool.
4 comments
[ 10.3 ms ] story [ 17.5 ms ] threadHowever, developers do need deep work time to write code. Of course, what action needs to be taken is subjective and Middleware can only provide probable signals affecting developer's joy of building :)
Many people track DORA metrics for their teams using Middleware which consists of Change Failure Rate and MTTR calculated using your incident mgmt tool and deployment tool.
Did I answer what you were looking for?