While Gitential can be used in countless, often very complex ways to improve various parts of the development process, let’s not forget the basics.
During the early days of Gitential, one of our early adopters faced a situation where it seemed like one of their projects had suddenly stalled. Since most of the work was outsourced, our client asked their vendor to give an explanation. The vendor told them not to worry, as they were working as much as promised, only the current phase was not very visible on the front-end.
Since our client trusted their vendor, they accepted this explanation. However, they knew that something was wrong. So they asked us to run an analysis on their code base to see whether their vendor is really providing the resources that were promised.
We are not including the full report here, just one diagram – probably the simplest one possible. After processing the repository, the first thing that popped up was the sum workhour diagram (note that this is from an earlier version of Gitential):