One of the main problems community managers face when they want to measure project’s health, is related with the life-cycle of it. If community managers are able to identify whether the project is either in growth, maturity or decline, that can be used when making further decisions regarding the project and its developer community
Software development analytics plays an important role in decision making for many data-driven firms. Being able to provide support for a wide range of different data sources to measure any project (so you can aggregate more than just one type of data) and manage different identities and affiliations among several data sources, is something we believe that can lead to a better understanding of the project as a whole.
Bitergia keeps growing as a software development analytics firm and nowadays, we are helping a wide variety of clients (project & community managers, engineering & development teams, HR managers, business analysts, etc.). Obviously, they’re not looking for the same goals in their projects, neither for the same metrics. So, how can Bitergia Analytics dashboards be customized for their specific needs?
Nowadays, more and more companies such as PayPal, Bosch or Autodesk are internally implementing inner source programs. InnerSource differs from classic open source development process by remaining within the view and control of a single organization and offers many advantages in terms of efficiency and effectiveness.
In previous posts, we talked about InnerSource characteristics and advantages such as InnerSourcing: the development model of the future.
Inner Source (or Inner Sourcing) is a term coined by Tim O’Reilly in 2001 that referenced to the,
“use of open source techniques within the corporation”.
Although more that 25% of the deployee code in the most influential IT companies was Open Source in 2015, IT departments didn’t show much interest in collaboration or innovation process. (Gartner, 2015).
Bitergia gathers data from almost the entirety of the set of tools associated with collaborative software development, providing useful information, metrics and insights for different profiles.
It seems that the first person that needs this kind of information is the community manager. But, there are other profiles that can get advantage of tracking projects and understanding the details to answer specific questions.
Which are other profiles that could be interested in metrics, and the information they can get from that data?
In Bitergia we have a list of happy customers using the Metrics Grimoire toolset (fork them at GitHub!) to produce metrics about their communities. Tracking tech communities is not that simple and this needs of some infrastructure. And one of the main issues usually consists of aggregating all of the information.
While we’re developing and testing our new toolchain for producing Kibana-based software development dashboards, we’re producing a good collection of them, with real data from real projects.
Continue reading “Check our Kibana-based development dashboards!”