We are asked how HappySignals relates to DevOps and we see it very clearly. It could be the main input for development cycles.
DevOps needs input somewhere and many times this input comes from IT developers, IT managers or some loud business stakeholders. None of these inputs actually focuses on better Employee Experience or increased productivity. We made this picture to visualise, that before you plan, you should have continuous analytics of the real struggles from the actual users of the system. Monitoring systems is of course needed, but is way too easy way out, system could be functioning but employees might hate it. Let’s raise the bar.
If you wonder if Employee Experience is related to DevOps, it is very closely. Otherwise you might lose focus on why you are developing next cycle and start building numerous small development releases that bring no actual value to users, but just add features that techies like to build.
Measuring the lost productivity from employees, like we do with Lost Worktime, allows you to justify the development costs of each development cycle/sprint/iteration.
Please see our case study from Tieto, Largest Nordic IT Company, how they use our solution to input their development cycles.