BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage Podcasts Colin Breck from Tesla on Quality Views to Expose Technical Debt

Colin Breck from Tesla on Quality Views to Expose Technical Debt

Bookmarks

This is the Engineering Culture Podcast, from the people behind InfoQ.com and the QCon conferences.

In this podcast recorded in London Shane Hastie, InfoQ Lead Editor for Culture & Methods, spoke to Colin Breck, an Engineer from Tesla, about using quality views to expose and prioritize technical debt.

Key Takeaways

  • When systems are not customer facing, quality is not directly obvious and is frequently overlooked
  • Quality views provide a visual way of exposing quality in a system block diagram
  • Quality is a subjective – the value is in the conversations rather than the numbers
  • Quality views can help plan and prioritise development of features in the product and paying down technical debt

Show Notes

  • 0:30 Introductions
  • 1:10 Background in industrial control and monitoring systems
  • 1:40 Where the idea of quality views came from
  • 1:55 The challenges of exposing the quality of systems that are not customer facing
  • 2:05 Finding a way to show quality when there is no UI, and
  • 2:15 A mechanism to show changes in a system over time
  • 2:50 A tool to have continual conversations about the overall quality of a system
  • 3:30 An experiment using multiple quality factors
  • 3:50 Simple scoring mechanism and mapping to a colour gradient drawn on a block diagram of a system
  • 4:20 Quality is a subjective – the value is in the conversations rather than the numbers
  • 5:15 Adoption is most effective when adopted bottom-up rather than top-down enforcement
  • 5:50 Using quality views to help plan and prioritise development of features in the product and paying down technical debt
  • 6:45 Positive reactions to using quality views
  • 1:05 Story of a product manager using a quality view to identify significant risk in an overall system
  • 8:30 Ways this can be misused
  • 9:10 Quality and features are not either/or – quality views
  • 9:45 Starting conversations around systems that have technical debt that was not well recognised
  • 10:15 Striking the balance between new features and improving quality
  • 11:20 Adoption by other teams and groups – asking for feedback
  • 11:50 There could be multiple quality views – identify the quality measures that matter
  • 12:30 The challenges of subjective evaluations across teams

Mentioned:

  • Tesla
  • Michael Feathers

Learn how to solve complex software engineering and leadership challenges. Attend in-person at QCon London, (April 4-6) or attend online at QCon Plus (May 10-20).

QCon brings together the world's most innovative senior software engineers across multiple domains to share their real-world implementation of emerging trends and practices. Find practical inspiration (not product pitches) from software leaders deep in the trenches creating software, scaling architectures and fine-tuning their technical leadership to help you make the right decisions. Save your spot now!

More about our podcasts

You can keep up-to-date with the podcasts via our RSS Feed, and they are available via SoundCloud, Apple Podcasts, Spotify, Overcast and the Google Podcast. From this page you also have access to our recorded show notes. They all have clickable links that will take you directly to that part of the audio.

Previous podcasts

Rate this Article

Adoption
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT