Software Engineering Should Run Like a Well Oiled Machine
Increase efficiency and effectiveness.
Reduce waste.
Move more quickly.
Adapt quickly.
To do these things, your people need to improve. To improve, they need the right metrics and the right training.
They need metrics on:
Waste.
Quality.
Speed.
Staffing bottlenecks.
Alignment.
Knowledge of Lean and Flow work patterns.
Behaviors that underlie all of the above.
Agile 2 Academy has partnered with EdenSoft Labs, a division of G3 Technologies, to provide groundbreaking AI-based metrics for numbers 1-5 above.
This is huge. These metrics are not your SonarQube code metrics. These look across your whole codebase. Some metric capabilities are:
How much of your code is being deleted because when someone leaves, others don’t understand the code? (The industry average is about 50% after five years)
What skill bottlenecks do you have among your developers?
How maintainable is your code? Specifically, does the code contain comments that actually explain what it does?
How well aligned are people’s coding efforts with management priorities? – that is, are people working on what they should be working on?
The ability to explain changes in plain language – so that business stakeholders can actually understand the work that has been done.
The last item, explaining what work has been done in plain English, is really powerful because it closes a critical gap between business and tech, helping them to communicate better. Over time, business managers learn more and more about what people are working on and get better at communicating with them about it.
These tools use proprietary AI developed by G3 Technologies. These are not your standard ChatGPT. These use the latest large language model and other algorithms, but were built specifically for understanding code.
Here is a snapshot of data from one of the tools. This tool shows how much code was deleted over a selected period of time. As you can see, it is immense. And analysis of the data, using the tool, shows that the vast majority of deletions are code written by a person who has left. That’s huge waste, pure and simple. And it is because people don’t understand the code that others write. It turns out that collective code ownership is a dream – it is not real – and it is because people are not doing design reviews or explaining what they are doing, and are not clearly documenting their code and their designs. Those are all behaviors that can be changed.
Get control of the work that is being done. Find out what is really happening, across the whole codebase.
These are powerful tools, and powerful tools can be misused. For example, the wrong way to use this is to criticize people’s work. If you do that, they will try to game the system. Instead, these must be used in a supportive way. That is why we do not sell these tools without providing training.
The training covers,
How to interpret the metrics.
How to determine root causes.
How to change behaviors that underlie the root causes – they need training in leadership.
How not to use the metrics.
Reach out to us to find out more. We are happy to provide a demo!
