Unlock the potential
of your human capital
through Knowledge-Centric insights
What you get
Maximized Productivity
- Close the Talent Gap: Identify areas with a high information loss rate to measure and reduce rework. Arrange for targeted training to bridge the knowledge gap.
- Cultivate Engineering Talent:: Quantify human capital across teams, projects, and programs. Drive consistent performance and growth by leveraging these insights.
- Boost Overall Productivity: Measure and enhance the efficiency of knowledge acquisition and its application, ensuring faster value delivery to stakeholders.
Improved Developer Experience
- Foster a Positive Work Environment: Monitor and enhance developer happiness, contributing to a motivated and enthusiastic team.
- Manage Cognitive Load: Quantify the mental effort tasks demand and streamline them. Proper task allocation ensures developers are not overwhelmed, thereby improving overall efficiency.
- Enhance Collaboration: Understand how effectively information is acquired relative to the number of active developers, ensuring smooth communication and cohesive teamwork.
Aligned leadership team
- Demystify Data with Intuitive Metrics: Use metrics that resonate with and are easily understood by the entire leadership team, ensuring everyone, from the CEO to Engineering Managers, is on the same page. .
- Connect Developer Well-being to Business Outcomes: Correlate the well-being of developers with the economic outcomes, emphasizing the direct impact of a motivated team on productivity.
- Validate the Impact of their Management Practices: Equip managers with objective data to confidently justify their strategies to other leadership members, ensuring that practices are in line with organizational growth objectives.
When you get results
In just hours, you will transform the extensive history of your company projects into immediate, visual insights with comprehensive diagrams.
Company Collaboration Over Time
- The diagram showcases the relationship between an organization's capability and its size over distinct period
- The x-axis delineates time in terms of weeks,
- The blue line offers a visual trajectory of the organization's average capability variations over the period.
- The green line provides a representation of the company's growth or reduction in size, with each point signifying the total number of developers contributing during a specific week.
Company Happiness Over Time
- The diagram visually tracks Happiness level for the company over a selected period
- On the x-axis, the diagram displays the week dates, while on the y-axis, it shows the Happiness levels.
- Each colored dot represents an individual developer's Happiness level, and the dark blue line represents the average Happiness level for all developers.
Developer Cognitive Load Over Time
- The diagram presents a developer's Cognitive load for a selected period across all projects.
- The x-axis displays the week dates, while the y-axis shows the Codnitive Load values.
- Each week's Codnitive Load level is represented by a blue dot and the blue line represents the average.
- You can compare a developer's Cognitive Load to all developers who contributed during the selected period. Individual loads are marked by light gray dots, and the average is depicted by the black line.
How It Works
KEDEHub platform has three main functions: analyzing Git repositories, calculating Knowledge-centric metrics, and presenting results visually.
KEDEHub is available in both SaaS and On-Premise versions.
Analysis is conducted on local clones of Git repositories.
- Your source code and commit messages remain secure on your premises, ensuring the protection of your intellectual property.
- No Intellectual property (IP) is captured through the analysis of the source code and commit messages.
- The analysis is carried out by an open-source agent, which can be found here.
No Disruptions for Developers
- There is no need for software installations on developers' computers.
- Developers are not required to provide any additional input.
- Consent from developers is not necessary.
Case studies
Getting started
