I was just brought on to a company to manage a Dev team and basically create an SDLC. It’s legacy code that’s difficult to maintain. Here’s how I’m handling things: 1. I used Monday.com to implement a new bug tracking, enhancements, and uplifts project tracking system. 2. At this point we spend 20% of our time working on bugs and 80% of our time goes to new features and critical customer issues. 3. I’m reviewing Microsoft’s plans for next year and how their security changes will affect our existing software. 4. Starting a plan to rearchitect the software to .Net Core so we’ll have an easier dev to production time. 5. Bringing on a former employee who can help with Dev handoffs to QA while we do the planning for the “2.0” version.

To balance updating old systems and working on new projects, first focus on keeping the old systems running smoothly, fixing only what’s necessary. Make small updates to avoid big disruptions. For new projects, choose ideas that support the future growth of the business. Use Agile methods to manage both tasks by assigning teams to update the old systems and other teams to work on new projects. Regularly check progress and adjust plans as needed. Keep everyone involved updated so the work stays on track without overloading resources.

Equilibrar sistemas heredados y nuevos proyectos requiere priorización y estrategia. Es clave mantener la estabilidad del sistema antiguo mientras se impulsa la innovación. Dividir el equipo en mantenimiento e innovación ayuda a evitar sobrecarga. La modernización progresiva, en lugar de reescribir todo de golpe, facilita la transición. Además, la automatización y documentación reducen esfuerzos y preservan el conocimiento.

Beyond the excellent points mentioned, I've found these strategies effective for balancing legacy maintenance with new development: 1. Establish transition roadmaps with clear "sunset dates" for legacy components 2. Implement API layers between old and new systems to enable gradual migration 3. Use "innovation sprints" within maintenance cycles to keep teams engaged 4. Adopt monitoring tools that provide unified visibility across both environments 5. Calculate technical debt carrying costs to make business cases for modernization Our team reduced legacy support overhead by 40% while increasing new feature velocity by implementing these approaches. #TechnicalDebt #SystemModernization #DevOpsBalance

Eliminate legacy systems as early as possible by defining your path and strategy with that goal in mind. The right solutions are often simpler and easier than you expect. Be aware of naysayers and those who resist change to protect their positions or territory. Focus on what is best for the business and take decisive action. Avoid creating overly complex interfaces just to support outdated platforms and inefficient processes that have developed due to legacy system limitations.