jpatil

At tenXer we are working on tools to help development managers and developers identify software development problems and improve skills. We have been focused on getting information from project management tools to date but are now ready to look at commit level data from git.

When I say commit level data, I am referring to things like identifying if someone is thrashing on a piece of code (writing a lot of lines and rewriting them right away), identifying commits that have touched really old code (probably want to check for regression defects), identifying huge pull requests (hard to review), etc. Here are a couple samples -> http://cl.ly/image/1e1d2b0a0f0m http://cl.ly/image/0F2X2u1A3R2w

I was wondering if people had other thoughts around what might be useful information to extract. What might you want to know about your team based on their git activity?

Thanks!

We are building tools to help developers gain insight on how productive they are, how they do against goals and continuously improve.

We aim to gather information from the various tools developers currently use and do some magic to extract relevant and present information that will be useful to helping the developer or team be better. Some of the things we are working around are code coverage, continuous integration, measuring and forecasting Sprints, retrospectives, feedback loops, etc.

If you use Pivotal Tracker, JIRA, GitHub, Phabricator or Jenkins (thats what we have integrated to so far), we would love to talk with you to show you some stuff we have done, get your feedback and maybe help you/ your team improve.

Thanks!