16 ms·

I thought this was a submarine article from Gitprime for a second as they use the exact same measures. I find the metrics useful for managing my devs, but only

by lovich 7y ago

I thought this was a submarine article from Gitprime for a second as they use the exact same measures. I find the metrics useful for managing my devs, but only as a secondary set of measures. If a team is hitting their goals for the project, I never need to look at these measures. If the team isn't hitting their goals I need to dive in deeper and these stats help me determine if the problem is the engineers just aren't working, or if its an issue outside of their control. Its also been a good piece of ammo to help train non technical upper management into accepting work from home more. I can show them directly how much the engineers are working and they lose that fear that people are just shirking their duties when they work from home

alesdonoso 7y ago
Hi there lovich and thanks you for your reply! You might be right since too many it managers work with OKRs so they don't need as a the first instance tool a git analytics one. In your case, it makes sense to have a tool like Scope "as a secondary set of measures" if everything is going well in your company! That's the point overall :) However, our tool involves engineers "gamifying" their processes so what we get is more motivated engineers, better team communication, company climate and culture. For managers, all data behind SCMs could be easily tracked so we make life easier! For non-tech profiles and remote teammates asking for metrics, it's worth also!