Let me introduce you to Filtra. Filtra aims to extract information like lead and cycle times from Github repos for (but not limited to) projects that are doing Kanban.
The SUSE Hack Week 18 is coming to an end tomorrow and I have to say it was a lot of fun! During the Hack Week we are free to work on whatever we want:
Hack Week is the time SUSE engineers experiment, innovate & learn interruption-free for a whole week! Across teams or alone, but always without limits.A SUSE tradition since 2007, Hack Week has brought together hundreds of hackers around the globe to collaborate on open source. Learn more about Hack Week.
This year I took the oportunity to work with Go, GraphQL, Prometheus, Grafana and a deployment via Docker Compose. The project is named Filtra, which is latin for filters. Filtra, when it's finally done, will query all of the issues from a Github project efficiently via GraphQL and present the results as a Prometheus exporter. Metrics like open or closed issues, bugs or support tickets are then shown in Grafana. On top of that Filtra already calculates the average lead time and hopefully tomorrow also the average cycle time of all closed issues.
┌────────────────────── Lead Time ──────────────────────┐ │ │ ├░░░░░░░░░░░░░░░░░░░░░░░░░░░░░|▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓┤ Issue Start Issue Created Work Done └────── Cycle Time ───────┘
But why am I doing this? Since our team at SUSE is doing Kanban, we don't have estimations. But we still need to predict how long it takes to finish something. And this is where lead and cycle times are coming into play. We can now use historic data to do much better predictions. We are not estimating and tracking only estimations. We are actually using time spend to caculate how long it takes to get stuff done. But this is just the beginning and I need your help! If you are interested in this come to the project, fork it, open pull requests or issues and help me shape this into a useful project management tool for hackers!