Wie können agile Methoden die Systemwartung und -aktualisierung optimieren?

Creo que mi principal contribución al equipo sería mi capacidad para combinar un enfoque técnico sólido con habilidades de comunicación efectiva. En proyectos anteriores, he trabajado en la optimización de procesos y en la resolución de problemas complejos, aportando soluciones creativas y prácticas. Mi experiencia en scrum aplicando metodologías específicas, como "desarrollo de software con metodologías ágiles" o "gestión de incidentes en entornos de alta disponibilidad" me ha permitido aprender a abordar los desafíos de manera eficiente, manteniendo siempre la calidad y el enfoque en los objetivos del negocio

I have to implement Agile in my company which has 703 employees. BUT the business is not software development from the beginning, its entire life cycle and implementation, it is about continuous services, corrective and evolutionary maintenance. In addition, each of these services is not currently working in an agile way. Each one is doing what the ticket priorities come in (incidents/problems/requests for a specific evolutionary or corrective development).But also the technological environment that is mainly worked on is a mainframe where most of the COBOL, DB2 etc. developers are of a certain age and therefore are more reluctant to adopt changes in their work methodology. I have one year to implement this. How can these be accomplished?

Los métodos ágiles optimizan el mantenimiento y las actualizaciones del sistema al fomentar prácticas que priorizan la adaptabilidad, la colaboración continua y la entrega incremental de valor.

Os métodos ágeis são grandes aliados no desenvolvimento de sistemas, por dividirem o risco, a cada sprint o risco é analisado e a rota corrigida se necessário, já no método cascata é muito comum perceber o erro quando o sistema já está pronto e o custo de alteração é quase o de um sistema novo.

Para mim, os métodos ágeis fazem toda a diferença no desenvolvimento de sistemas. Adoro como eles permitem entregas contínuas e incrementais, o que facilita a adaptação às mudanças e reduz os riscos ao longo do projeto. Com ciclos curtos de trabalho, consigo receber feedback constante dos stakeholders, garantindo que o produto final tenha mais qualidade. Além disso, trabalhar em colaboração com equipes multidisciplinares torna a comunicação mais fluida e as soluções mais inovadoras. O que mais me motiva é ver o valor sendo entregue de forma constante e alinhada às expectativas

Risk Mitigation Because Agile emphasizes working in short cycles, it reduces the risk of large, untested changes being introduced into the system. Each iteration allows for frequent testing, which helps identify issues early on and mitigate risks associated with updates and changes. This also allows for more frequent deployments, reducing the chances of unexpected downtime or problems.

Utilizar Agile para el mantenimiento y actualizaciones del sistema es ideal porque: 1. Responde rápido al cambio: Iteraciones cortas permiten adaptarse a nuevas necesidades. 2. Prioriza tareas críticas: Se enfoca en lo que genera mayor valor inmediato. 3. Fomenta retroalimentación continua: Soluciona problemas rápidamente con el feedback de usuarios. 4. Incorpora automatización: Reduce errores en actualizaciones con herramientas como CI/CD. 5. Gestiona deuda técnica: Mantiene la calidad del sistema a largo plazo. En resumen, Agile asegura actualizaciones más rápidas, eficientes y alineadas con las necesidades del negocio.

2 critical points are: A balanced backlog of bug and bottleneck fixes, enhancements and new features. Refinement between these types of tasks is fundamental to keeping track of goals. Monitor burndown charts. They provide predictability of work during projects and allow you to work ahead. A product owner can't negotiate without a margin of delivery.

System upgrades can be potentially dangerous due to the significant impact they have on stakeholders. The loss of trust in the organization is a factor beyond the project that needs to be considered. The Impact x Risk factors have probably already been calculated and implementation failures cannot compromise the estimates. A good idea is to introduce DevOps practices into the sprints. More automated deployments will be more like continuous delivery and the risk will be lower. This is due to the better quality of collaboration between teams in the DevOps methodology.

Es sumamente importante hacer un estudio inicia de la complejidad de cada una de las tareas, para establecer plazos acordes y se puedan llevar a cabo en el tiempo estimado.

Monitor and assess the impact of Agile system changes with a forward-thinking approach. Collect data on usage, satisfaction, and errors, as well as relevant metrics. Identify risks and adjust plans based on user feedback. The combination of lean and agile thinking allows personnel with different expertise to join teams, providing the resources necessary to complete projects quickly and effectively. While lean and agile methods share many similarities, they are most effective when used in conjunction for maintenance activities.

Integrating other methodologies or practices into Agile improves the methodology. It is more open in its principles, which allows proven practices with a higher success rate to be connected to more technical problems. Learning and development that is integrated into the Agile culture must include learning equivalent methodologies as part of its goals.