First of all, I wanted to apologize for not posting for few weeks in my blog. I was so into my work that I forgot to share my latest findings and opinions with you. Sorry, my reader, I will try not to repeat this again
.
If you remember I work for Programeter and I thought I should talk about it this time. Programeter is a monitoring and reporting tool for all kind of managers in software projects. It is both for technical leads and for managers without IT education. It helps them to keep an eye on software project in real-time. When we started to work on Programeter, our key goal was to make it autometed same way as Google Analytics is. We wanted to make sure that niether of project members should spend time on manually submiting data. Instead Programeter collects all the data from your development environment by connecting to code repository, bug tracking and task tracking systems which you already use.
There are four types of reports or so called angles: Effort, Scope, Quality Assurance and Knowledge. The reports in the Effort angle focus on how much effort and activities has been done by project team. For example, you can compare how active is team on different days of the week. You can see how completed tasks affect number of new bugs on daily basis. The information in Scope angle can help you to understand how your project moves towards its end. The reports in Quality Assurance angle focus on comparing the information about quality of code based on indicators received from different types of development tools. Knowledge angle reports focus exclusively on programming team’s knowledge. For example you can see when project knowledge is poorly shared and take proactive actions to lower team attrition risks.
Programeter is all about metrics and indicators. My favorite one is “know-how score” of developer. It illustrates the breadth of the individual developer’s knowledge in the project. For example, the know-how score of 6.5 in certain project, means that developer is capable of working alone with most project components. There are also software project indicators like: Team Activity, Team Friendliness, Contribution Size, Contribution Efficiency, Project Code Stability.
I hope it all didn’t sound as advertisement…actually, I know it did. But we truly addicted to what we do here, so you have to excuse me
And please, if you you or your company is working on tools for software development, please let me know. I would be glad to review it and comment about it on my blog.



I plan to try this on my current project.