Technical Debt vs. Not "Done" Work

In this Scrum Tapas video, Professional Scrum Trainer Steve Porter looks at the impact that undone work has on technical debt and discusses some techniques to use when dealing with such issues. Steve discusses value creation and what needs to be done to ensure value is a consideration in the process.

[@TheFootballNightmare]

I would love to see a follow-up of this video.

[@DIGGERfromAR]

A focus on output while de-prioritizing technical debt is traditional project management. Disguising that modus operandi as value-driven is dishonest. The exponentially rising cost of these choices is well documented. #BusinessAsUsual
Not "Done" work means the Definition of "Done" has not been met; therefore it is not a proper product Increment. This is one of the two best candidates for calling any Sprint a failed Sprint. #ScrumBut

[@StevevrPorter]

Alan, I'm curious, in your opinion, can an increment contain technical debt and still be "Done"?

[@nuurdaalacay3541]

Many thanks Steve for this enlightening video, to Mr larimer, its my understanding that sometimes you have to loosen your DOD consciously to deliver some value to your customer now so that your competitor does not eat your lunch and fix the technical debt later. Steve could you please kindly confirm or deny this statement validity.

[@peterillig3021]

quality of this video is bad