|
|
|
|
|
|
by sdesol
1833 days ago
|
|
|
> The way to get engineers to adopt it is to demonstrate how it can be useful for them Agreed. My goal is produce a connected efforts graph that can accurately connect code with effort and time spent (meetings, code reviews, waiting for builds, etc.) This is why I refer to this as business intelligence for the software development lifecycle. Insights come from data and you can't use traditional BI tools to analyze software development data. If you want to understand effort, you need to be able to slice and dice coding activity which GitHub and traditional BI tools can't do easily or at all. Take the following for example, if you want to quickly understand the significance of three commits, you can do something like this: https://public-001.gitsense.com/insights/github/repos?q=comm... which will stitch together the commits in real-time for analysis. And this is what I ultimately mean by being able to slice and dice software development activity. And how I see thing is, BI for software development activity is both useful for developers and leaders. |
|
|