Matt ElandHey all, I'd love some feedback on audience expectations for a software talk I'll be giving at CodeMash in January. This is my first time speaking at a technology conference and I want to make sure I have a good chance at meeting a wide array of audience expectations.
Here is my accepted abstract:
Technical debt must die - Communicating code to business stakeholders
Our software sucks. We're up to our necks in bugs and technical debt, yet we often seem to hit roadblocks explaining things in ways that bring about meaningful change. In this session you'll learn to gather, analyze, and interpret data in order to create effective presentations to communicate quality, technical debt, and other technical matters in ways that tell a compelling story. You’ll master how to communicate effectively with key stakeholders by taking a data-driven approach and bridging common gaps between development and business stakeholders. You’ll explore the 7 tools of software quality, and how they can bring clarity and sanity to the decision-making process, justify paying down technical debt, and focusing on improving our quality in the areas that need it most.
If you were attending this talk:
- What would you most want me to focus on?
- What would you be disappointed about if I didn't cover?
- What work situations or other questions coming in would you want to find answers to?
- What other topics not explicitly listed here would you hope I covered?
Thanks for any help you can provide in the comments.
If you're curious about some of the things mentioned in the abstract, take a look at my post on the 7 basic tools of software quality.
