Every discipline has its jargon that’s hard to explain to those who aren’t “in the know” about tools, how work gets done, and common problems. As engineers, we do ourselves a favor by using names that are easy to explain and have reasonable agreement on the definition. For example, I don’t think it’s hard to explain the very basics of agile methodologies, data warehouses, or firewalls because their names convey some meaning, even though engineers debate the technical definitions.
At some point, you’ll face a situation where a business leader asks you to explain some technical jargon. Maybe they heard it from a technology vendor, saw it on an invoice, or heard about it at a conference.
