Tech debt is a shared responsibility across the team, not just one person. It usually involves quick fixes or vague solutions made under tight timelines. To manage it effectively: 1. Tech debt should never go unaddressed for more than 4-5 sprints (2 months max). Ensure it's included in sprint planning. 2. Review tech debt during every retrospective to track progress and prioritize. 3. If tech debt grows, block a sprint every 4-5 sprints to focus solely on fixing it. This approach keeps the process manageable, non-disruptive, and ensures the team stays on top of it without overwhelming anyone.

Having a conversation and getting to know what their perspective and understanding about technical debt is how we should start. Now the second important part is why it is being caused and what are its impacts in long run. Ones they understand this half of the problem is solved. Now they will tell you different solutions to minimise the impact themselves as a normal human tendency to solve problems. Implement some most useful ones which will also encourage them to not to do the same in the future. And at the same time plan the sprint in such a way that every now and then we are looking back and find/fix the debts to minimise its effects

I recommend a collaborative approach that incorporates technical debt into our sprint planning and retrospectives. By sharing relevant metrics and emphasizing the importance of managing technical debt, we can create a shared understanding of its impact. To begin, I'll engage with team members about technical debt and its potential effects on project timelines. Using real-world examples. Key Steps include: • Clarify the Impact • Collaborate on a Plan • Align Education and Processes • Monitor and Adjust After implementation, I'll monitor the outcomes and encourage open dialogue. If we see improvements in our timelines, it will validate our strategy. If not, we’ll work together to reassess and adjust our approach.

Ignoring technical debt today slows down development tomorrow. If a team member overlooks its impact, here’s how I address it: 🔹 Make It Visible – Track tech debt in the backlog. 🔹 Prioritize Fixes – Balance new features with refactoring. Sustainable development isn’t just about speed—it’s about building for the long run.

I’d address this by first educating my team member on how technical debt affects project timelines, using real examples where ignoring it led to delays. I'd highlight that short-term speed can lead to long-term slowdowns due to rework and maintenance issues. Then, I’d advocate for regular refactoring and debt tracking in sprint planning. If resistance persists, I’d demonstrate with data—showing how addressing debt early improves velocity over time. Lastly, I’d collaborate to find a balance between feature delivery and tech debt resolution, ensuring both business goals and code quality are met efficiently.