Kishore Bhatia talks with Travis Kimmel on software engineering measuring, communicating and improving engineering productivity, and challenging the widespread belief that engineering is an art. Their conversation covers: measuring engineering impact; key performance indicators (KPIs); development metrics; challenges in building a delivery pipeline with metrics; implementing feedback loops; the key metrics that most engineering teams should and how they evolve as the team grows. Travis uses his experience building data analytics tools in this space to present best practices for engineering teams and business stakeholders for measuring value and productivity.
Show Notes
Related Materials
Travis’ Developer Surveys and blog articles
- https://www.gitprime.com/2017-software-developer-productivity-survey/
- https://blog.gitprime.com/engineering-impact-news-2016-10-27
- https://blog.gitprime.com/author/ben-thompson
- Why KPIs matter for software engineering
- 6 causes of code churn and what to do about them Software Developer productivity survey in the US and Great Britain
Other sources
- What slows dev teams (guest post)
- Moneyball: measuring revenue per Engineer (external blog)
- LinkedIn: https://www.linkedin.com/in/traviskimmel/
- Guest Twitter: https://twitter.com/traviskimmel
- Guest Email: [email protected]
