Having a Glossary of Terms Is a Good Idea

2min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

Having a shared understanding of the terms is very important for ambusess analise and also development. I was working with a client once, and i found there were two terms that they were using that i thought might mean the same thing but i wasn't sure. In that case, let's just pick one term and stick to it so that people don't have to mentally translate it or wonder if they're different. That's why this term calle shif left, you try to reduce the error from the beginning. So i also notice this kind of research, when you find the erress closer to the right side in the value stream mapping way,. It costs, like, really exponentially expensive

“A way to boost productivity is to create high-quality software from the outset, so that teams can spend less time on rework, both during development and after the release."

Karl Wiegers is the author of “Software Development Pearls” and the Principal Consultant at Process Impact. In this episode, Karl shared some lessons he has learned over the past five decades of his career. We first discussed software requirement, its role for communication, and the importance of defining the right requirements. Karl then touched on the reasons we can’t optimize all desirable quality attributes and instead advised how we should define the quality attribute requirements. Next, Karl shared some project management pearls, related to work planning and dealing with estimates. Towards the end, Karl explained the relation between quality and productivity, using pain as a driver for improvement, and his ultimate pearl of wisdom.

Listen out for:

Career Journey - [00:05:46]
Requirements for Communication - [00:08:07]
Importance of the Right Requirements - [00:13:49]
Importance of Definitions - [00:16:23]
Optimizing Quality Attributes - [00:18:48]
Specifying Quality Attribute Requirements - [00:21:59]
Work Plans & Friction - [00:24:48]
Giving Estimates - [00:31:03]
Pressure to Making Commitment - [00:35:19]
High Quality & Productivity - [00:39:38]
Pain as Improvement Driver - [00:45:16]
Ultimate Pearl - [00:50:25]
3 Tech Lead Wisdom - [00:54:09]

_____

Karl Wiegers’s Bio
Karl Wiegers is Principal Consultant with Process Impact, a software development consulting and training company. He has a PhD in organic chemistry. Karl is the author of 13 books, including Software Development Pearls, Software Requirements, The Thoughtless Design of Everyday Things, Successful Business Analysis Consulting, and a forensic mystery novel titled The Reconstruction. You can reach him at ProcessImpact.com or KarlWiegers.com, where you can hear more than 50 songs he has recorded just for fun, including 18 originals that he wrote.

Follow Karl:

LinkedIn – https://www.linkedin.com/in/karlwiegers
Website – https://karlwiegers.com
Process Impact – https://www.processimpact.com
Medium – https://karlwiegers.medium.com

Our Sponsors

DevTernity 2022 (devternity.com) is the top international software development conference with an emphasis on coding, architecture, and tech leadership skills. The lineup is truly stellar and features many legends of software development like Robert "Uncle Bob" Martin, Kent Beck, Scott Hanselman, Venkat Subramaniam, Kevlin Henney, and many others! The conference takes place online, and we have the 10% discount code for you: AWSM_TLJ.

Skills Matter is the global community and events platform for software professionals. You get on-demand access to their latest content, thought leadership insights as well as the exciting schedule of tech events running across all time zones.
Head on over to skillsmatter.com to become part of the tech community that matters most to you - it’s free to join and easy to keep up with the latest tech trends.

Like this episode?
Subscribe on your favorite podcast app and submit your feedback.
Follow @techleadjournal on LinkedIn, Twitter, and Instagram.
Pledge your support by becoming a patron.
For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/103.