NapAnt: Visualize the productivity of your engineering team at

NapAnt's mission is to help developers achieve their full potential by visualizing key development figures and automating the work reporting process. NapAnt creates an environment where you can focus on your creative work.

Since there was no tool on the market to measure productivity, we developed a slack bot in-house and implemented a system to obtain logs of commits, pull requests, and merges from the Github repository and notify slack by an organization and by the developer. As a result, the project manager's workload was reduced by 60%, allowing him to spend more time on other tasks. The sprint completion rate also increased to 90%. With the implementation and automation of the tool, the team's efficiency has increased significantly. NapAnt's mission is to help developers in the field achieve their full potential by visualizing key development figures and automating the work reporting process. NapAnt creates an environment where you can focus on your creative work.

@sunao_tateno Frequency, amount of commits and alike are bad indicators for developer productivity. I can develop in ways to optimize for this measurement. It won't produce better code (probably even worse with low quality) or add more value. I am sorry to say this but this doesn't add any value to software development.

@tobmaster Thank you for your comment!! Could you tell me the story behind this? What kind of measurement have you tried and why it didn’t work?