How do we know we have a lot of technical debt in our environment? how to deal with it and get to sustainable pace

1. Dealing with Technical debt Getting to a Sustainable pace

2. Unsustainable pace / Technical Debt vicious cycle

3. What are the typical symptoms of Technical Debt / unsustainable pace? The Product Dev Factory feels like it cannot succeed lower professionalism in engineering Mountains of defects High reopen rate Mastery of shortcuts and regression impact avoidance Many branches and versions that are supported No slack for errors Murphy happens Problems are magnified

4. How to get to sustainable pace Measure actual capability and start to work according to it predictability - regain trust In the short term – hard commit on less content for each delivery Soft Commit to deliver as much high quality features as possible Restrain Sales – manage overcommitment Elevate capacity to align with business needs After factory is stable and scalable

5. Sustainable Pace vs Make it Happen Delivering fast requires good technical infrastructure, robust system Technical debt slows us down significantly Scaling requires simplification of the system, less reliance on heroes B Maintain and improve ability to deliver fast - Ability to scale the business D Sustainable Pace with No Technical Debt A Meet challenging business requirementsnow and in the future C Deliver value now – To meet current business challenges D’ Make it Happen approach: Always be able to deliver Regardless the price With current capabilities, must have make it happen approach otherwise R&D don’t deliver enough R&D need to be pushed in order to deliver what the business requires

6. The solution – differentiated services