BEGIN:VCALENDAR
VERSION:2.0
PRODID:IEEE vTools.Events//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:Pacific/Honolulu
BEGIN:STANDARD
DTSTART:19470608T023000
TZOFFSETFROM:-1130
TZOFFSETTO:-1000
TZNAME:HST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20230324T220846Z
UID:E7CEABAA-8CD5-4E22-BAC9-A7693EA83452
DTSTART;TZID=Pacific/Honolulu:20230323T173000
DTEND;TZID=Pacific/Honolulu:20230323T190000
DESCRIPTION:Technical debt in software is incurred when developers take sho
 rtcuts and make ill-advised technical decisions in the early phases of a p
 roject---typically in the rush to deliver something---only to be confronte
 d with the consequences of those shortcuts later: the need for costly and 
 labor-intensive workarounds\, high rates of bugs\, and low productivity. I
 n this talk I will introduce the general notion of technical debt\, and di
 scuss its many manifestations and why you should care about it. Then I wil
 l zero in on a specific kind of technical debt--design debt. I will outlin
 e the causes of design debt and briefly describe how this debt can actuall
 y be quantified. Finally I will present two brief industrial case studies 
 on how design debt was detected and remediated.\n\nSpeaker(s): Dr Rick Kaz
 man\, \n\nBldg: Entrepreneurs Sandbox \, 643 Ilalo Street\, Honolulu\, Haw
 aii\, United States\, 96813
LOCATION:Bldg: Entrepreneurs Sandbox \, 643 Ilalo Street\, Honolulu\, Hawai
 i\, United States\, 96813
ORGANIZER:angus.ferguson@ieee.org
SEQUENCE:9
SUMMARY:Technical Debt: How to Find it and Fix it
URL;VALUE=URI:https://events.vtools.ieee.org/m/350286
X-ALT-DESC:Description: <br /><p>Technical debt in software is incurred whe
 n developers take shortcuts and make ill-advised technical decisions in th
 e early phases of a project---typically in the rush to deliver something--
 -only to be confronted with the consequences of those shortcuts later:&nbs
 p\; the need for costly and labor-intensive workarounds\,&nbsp\;high rates
  of bugs\, and low productivity.&nbsp\; In this talk I will introduce the 
 general notion of technical debt\, and discuss its many manifestations and
  why you should care about it. Then I will zero in on a specific kind of t
 echnical debt--design debt.&nbsp\; I will outline the causes of design deb
 t and briefly describe how this debt can actually be quantified.&nbsp\; Fi
 nally I will present two brief industrial case studies on how design debt 
 was detected and remediated.</p>
END:VEVENT
END:VCALENDAR