When you're working in a software development team, you'll know that work can be very stressful at times. Too much stress is a bad sign and can wear people down or even cause burnouts. That's why it's important to keep track of metrics that address team well-being. In a previous post, I argued that the often-used team happiness metrics are unreliable. Happiness may be useful in certain instances, but it is highly subjective and tends to fluctuate by the day. That's why I proposed to measure an alternative metric; team morale. Team morale is based on scientifically validated scales (see previous post) intended to measure employee well-being and work. Because this is a more reliable instrument, any decisions you may take based on the results will also be more reliable. And that's a good thing :)
I decided to write a small web application that can measure team morale for a team and make the results interpretable by comparing them against benchmarks. As with most hobby projects, this quickly grew into something a bit bigger and more time-consuming to make. That's how TeamMetrics came about. Don't worry, it's still a small tool. But I intend to extend it with other metrics and more features in the near future. It's free to use and the surveys can be entered anonymously. I hope to use the (anonymous) data that I've collected to improve the metrics and the benchmarks.
You can check it out here: http://teammetrics.apphb.com. You can also participate in an ongoing survey of team morale here with this link. At the end of the 8 questions, you can compare your results to a benchmark and the entire sample.
A sample screenshot is below:
If you found a bug, if you have a question or if you have an idea on what I can add, just drop a line or post a comment.