Ideas and Validation January 29, 2020

Feature release benchmarking tool

fANZY

Hey guys,

So after posting this https://bit.ly/36Agc1a 2 days ago I've started working on noticing the issues I face. I've noticed one that seems promising and wanted to see what you guys think.

The stem is, I'm currently working as a dev in a startup and they don't seem to see code quality having as much of a bad impact as I do and whilst i'm trying to push code review as a process to improve it they think it would decrease feature release throughput too much to be worth it.

Not going into to much implementation details, the Idea is to create a benchmarking tool that would integrate with Github and/or a Kanban boards like Jira and let you track the speed it takes for every feature to be released. Point is to allow comparison over the long term of before and after implementation of a new process such as code review or pair programming.

Would be keen to know what you guys think and if any of you are in the industry, would you have a use for it?

  1. 2

    that could be interesting.

    Definitely feel the pain of the problem. To solve for this in the past i've used release version as an event attribute and wrapped all analytics tracking calls. This allows most existing reports to be segment-able by release which is super helpful.

    the harder part for me has been knowing when the feature has seen enough usage that the difference in the reports is reliable. but it'd be worthwhile to me, if i could sign up for something that could do the statistical significance math and send alerts when it's time to look back and see what happened.

    1. 1

      Awesome, thanks for the feedback