Lightning Talks Tulio Paschoalin Leao – Software Engineering Manager October 28th, 2021 Tackling Technical Debt: Hello Junior Developers!© 2021 Cadence Design Systems, Inc. All rights reserved. 2 Photo by Cadence Design Systems, Inc. All rights reserved. 6 Senior Devs Junior Devs Key Concepts • Technical Debt • Resource Allocation “Free time” Knowledge© 2021 Cadence Design Systems, Inc. All rights

that it may not be in a consistent state, but it is a bug for a client to contradict itself.Technical debt is quantifiable as financial debtMeir M Lehman Programs, life cycles, and laws of software .html Technical Debt is a wonderful metaphor developed by Ward Cunningham to help us think about this problem.Martin Fowler martinfowler.com/bliki/TechnicalDebt.html Like a financial debt, the technical technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice.Martin Fowler martinfowler.

users and stakeholders monthly. These frequent iterations effectively measure progress, reduce technical and programmatic risk, and respond to feedback and changes more quickly than traditional methods operational and technical stakeholders. A product owner or a scrum master manages the backlogs, updating them based on the results of releases and sprints, changing operational priorities, or technical considerations software, to include software developers, database administrators and architects, testers, and other technical experts. End Users Conveys operational concepts and requirements/needs, participate in continuous

Krull Technical Humility 1 Jason Wohlgemuth Agile Front-end Automation 4 Nik Kalantjakos "Coaching Agile Teams" - Book Club 0 Ray Page CA Clarity PPM software for Agile 1 Scott Grimes Technical Debt for Defense 2 Jonathan Mowers The Testing Pyramid with a focus on Unit Testing 2 Scott Grimes Technical Debt 2 Nick Wenner My Experience in Effective Retrospectives 2 Sean Lomax Scrum: The Art of Doing in Half the Time 1 Barry Gastrock Scrumban! 1 Mike Ballou Notes from Velocity 1 Chris Krull Technical Humility 1 Ray Page CA Clarity PPM software for Agile 1 Eric Ewing LeanUX - Book Club 1 Tek Agile

Analysis 11 © 2018 Stericycle, Inc.Regulatory Standards & Documents 12100+ Standards, Documents and Technical reports Software Development in Medical Devices 13 www.medicaldevicehq.com www.jhc-technology vulnerabilities are introduced ❖ All new security hotspots are reviewed ❖ New code has limited technical debt ❖ New code has limited duplication ❖ New code is properly covered by testsContinuous Testing certified (3rd party vendors), ... ❖ What can help: ➢ Modular and decoupled architecture, Frequent tech debt reviews, Security/Compliance tracking, Established testing framework for upgrades, Proper dependency

actually degrade over time. 2. We improve daily work by explicitly reserving time to pay down technical debt, fix defects, and refactor and improve problematic areas of our code and environments—we do actionable data within weeks f. RESERVE 20% OF CYCLES FOR NON-FUNCTIONAL REQUIREMENTS AND REDUCING TECHNICAL DEBT i. Don’t just make the interest payments, pay down the principle ii. If not managed, services

Refactoring Upgrading Migrating Debugging Adding tests Writing documentation Resolving technical debt “The only constant in life is change.” - Heraclitus5 Aurora Innovation Types of Change Fixing accountability for software quality. reward continuous improvements and actively share about technical debt. Commitment Teams need to commit to continued investment in maintaining software quality and

Remind about Evolution Identify Technical DebtWhat-If? Did you consider? Suggest Better ways Ask about Simplicity Remind about Evolution Identify Technical DebtDoesn’t really happen Reviewer Ineffective Reviewer unaware of functionality Transactional involvement only Focus on technical aspects aloneToo Late for idea exchanges At least, no bouncing ideas off each otherModernisation/gradual mistakesHow about… Discuss & implement Better ways Ensure Simplicity Enable Evolution Address Technical Debt Evaluate more options!High- Ownership Functional Knowledge Code Awareness Code Familiarity

Unit Testing Barry Gastrock Scrumbanl Jun 2015 Mike Ballou Notes from Velocity Chris Krull Technical Humility Jul 2015 Jason Wohlgemuth Agile Front-end Automation Nik Kalantjakos "Coaching Agile Agile Teams'" - Book Club Ray Page CA Clarity PPM software for Agile Aug 2015 Scott Grimes Technical Debt Michelle Bauer "Rapid Problem Solving with Post-lt Notes - Book Club Nick Wenner

The DevOps Handbook – Parts 5 & 6 – Part 5: The Third Way – The Technical Practices of Continual Learning and Experimentation; 1. Introduction a. Goal – practices to enable learning as quickly, frequently in days that previously would have taken 3-6 months c. INSTITUTIONALIZE RITUALS TO PAY DOWN TECHNICAL DEBT i. Regularly schedule day- or week- long improvement blitzes with Dev & Ops teams. Focus on Provide Test Certified Mentors and Test Mercenaries to kick start testing efforts – Part 6: The Technical Practices of Integrating Information Security, Change Management, and Compliance 1. Introduction