Software projects accumulate many kinds of debt. While some can be useful (if not necessary), teams should learn how they can prevent “velocity bankruptcy.”
About the Webinar
Software projects accumulate many kinds of debt. Each debt comes in the form of small qualitative shortcomings we (knowingly or unknowingly) choose to ignore in the name of shipping. They cause friction—and over time they can combine to easily grind momentum to a halt if left unchecked. While these kinds of debt can in fact be useful (if not necessary) to creating software, teams need to understand the nature of their shortcomings to prevent “velocity bankruptcy.”
In this one-hour webinar, we’ll discuss the nature of process debt: hitting on shortcomings in things like culture, empathy, collaboration, morale, experience, and requirements. We’ll discuss examples, tips on identifying the risks in your own projects, and how to decide when to avoid, mitigate, or accept and track these risks.
This is a part of our ongoing webinar series on tackling design and technology challenges.
Thanks for Watching!
Thanks for watching “Saving Projects From Process Debt” with Brian “Mac” McElaney. Below you’ll find some related content and resources Brian mentioned during his presentation.
Resources from the presentation
Summary post of Gunter Dueck’s talk
Socialtechnical Design Variables
Visualising Sociotechnical Architecture with DDD and Team Topologies
