¿Cuáles son las mejores prácticas para la hoja de ruta de productos con plataformas tecnológicas heredadas o maduras? (2024)

It's important to focus on integration rather than just innovation. Take the time to understand the limitations and strengths of the platform. Prioritize incremental improvements that enhance reliability and improve the user experience. Involve stakeholders early in the process to align expectations and ensure that user needs are met. Regularly reassess and adapt your roadmap to strike a balance between maintaining stability in legacy systems and capitalizing on emerging technology opportunities.

Traducido

Incremental Upgrades:Plan for incremental upgrades rather than massive overhauls.Break down the roadmap into smaller, manageable releases to minimize the impact on the legacy system.Legacy System Documentation:Have comprehensive documentation for the legacy system, including architecture, APIs, and data structures.This documentation is crucial for the development team to understand the existing system and plan for changes.

Traducido

Cross-Functional Collaboration:Foster collaboration between development, operations, and business teams.Ensure that all stakeholders understand the roadmap and are aligned with the goals of improving the legacy system.Legacy System Retirement Plan:Develop a plan for the eventual retirement or replacement of the legacy system.Consider the long-term roadmap with a view to transitioning to more modern technologies.

Traducido

DevOps books like The Phoenix Project are good starting point for understanding how to reduce technical debt and use simple tools like Kanban boards for visual representation of tracking. Apart from DevOps, It’s also common to adopt new ways of working secure software supply chain (DevSecOps), site reliability engineering (SRE) and CI/CD, as part of application modernization initiatives. Modernized applications are often more agile and flexible, allowing development teams to respond quickly to changing market conditions and customer needs.Modernized modular applications enable collaboration, so development teams to work together & share code, leading to increased productivity.New tools & tech can be added during the cycle.

Traducido

Technical debt is like the clutter in your home - it might be out of sight, but it sure slows you down. Convincing stakeholders to clean up isn't just about tidiness; it's about making the house more livable and functional. Quantify how this 'clutter' impacts product quality and costs, then tie it to the big picture - customer satisfaction and strategic goals. It's about turning technical housekeeping into a compelling story of enhanced user experience, agility, and innovation. Involve stakeholders in the cleanup plan, showing tangible progress and results. After all, a clutter-free home is a happy one, in software and life!

Traducido

Technical debt, often overlooked, can significantly impact product quality and customer satisfaction. It's essential to articulate its effects on performance, reliability, and security. Stakeholders need to understand that reducing technical debt is not just about fixing issues; it's an investment in the product’s future. Quantifying its impact on quality, cost, and speed, and linking it to strategic goals and customer outcomes is crucial. Educating stakeholders on the long-term benefits, such as enhanced user experience and increased agility, helps prioritize technical debt reduction alongside new features. Involving stakeholders in planning and demonstrating progress is key to successful reduction efforts.

Traducido

Nothing beats genuine unpaid feedbacks. The users tell the truth. Also marketing can help pump up sales in short term but dedicated improvements basis feedback turn a product into legacy

Traducido

Best practice #1 Inform teams of any operational changes, upgrades, equipment, as far in advance as possible. Best practice #2 Get your team leaders on board first, explain why these changes are needed. Request leadership to embrace changes with a positive attitude because it will effect entire regions of your organization if you don’t. Best practice #3Ask the opinions of everyone within the organization that these changes will impact regardless of how small you think the position is or how little it will be impacted. Let these people assist you to flush out potential challenges the new programs, technologies, or may cause in workflow. People embrace what they help to create. Double win factor here.

Traducido

Be ruthless about sunsetting old products/features. Legacy tech debt drags you down. Don't be afraid to "break some eggs" and disrupt the status quo. Move fast and break things.Prioritize new products/markets over legacy maintenance. Focus innovation on the future not the past. Legacy products have diminishing returns on investment.Challenge every legacy feature - does it still create real value for customers? Be willing to remove things customers barely use or forget about.Don't assign your A-players to legacy products. That's a formula for boredom and talent loss. Put your best people on new initiatives.

Traducido

In my experience, platforms doesn't produce outputs.This is us to drive them to what to produce as output.Knowing the full potentials of our platforms in contrast with market needs and considering the product strategy of company are main factors to make the best decision.🎩

Traducido

(editado)