Technical debt is not, not “Done.”
What does this mean exactly? In some occasions it could be the right business decision to create technical debt—for example, being first to market, creating a quick prototype, or reacting to an unexpected event.
- Chapter 3 Value
- from The Professional Product Owner: Leveraging Scrum as a Competitive Advantage, First Edition
- Publisher: Addison-Wesley Professional
- Released: June 2018
Very important! Technical Debt is not, not Done! A good example of when to release a product despite its technical debt
Share this highlighthttp://www.safaribooksonline.com/a/the-professional-product/18758344/