Cualquier empresa que tenga como base el software, para ser ágil necesita entregar de forma frecuente y sostenida mientras mantiene una estabilidad alta. Cualquier tipo de intento de agilidad que no persiga esta entrega continua no persigue la adaptabilidad y flexibilidad que asociamos con la agilidad.
6. “
Each technological revolution have resulted in the
disruption of existing businesses by those who have
mastered the new means of production
From projects to products
6
12. “
Continuous Delivery is the ability to get changes of
all types—including new features, configuration
changes, bug fixes and experiments—into
production, or into the hands of users, safely and
quickly in a sustainable way.
12
https://www.continuousdelivery.com Jez Humble (link)
13. “
Continuous Delivery is the ability to get changes of
all types—including new features, configuration
changes, bug fixes and experiments—into
production, or into the hands of users, safely and
quickly in a sustainable way.
13
https://www.continuousdelivery.com Jez Humble (link)
14. “
Continuous Delivery is the ability to get changes of
all types—including new features, configuration
changes, bug fixes and experiments—into
production, or into the hands of users, safely and
quickly in a sustainable way.
14
https://www.continuousdelivery.com Jez Humble (link)
15. “
Continuous Delivery is the ability to get changes of
all types—including new features, configuration
changes, bug fixes and experiments—into
production, or into the hands of users, safely and
quickly in a sustainable way.
15
https://www.continuousdelivery.com Jez Humble (link)
17. Entrega Continua
◉ Automatización de tests
◉ Automatización despliegues
◉ Integración continua
◉ Desarrollo en trunk
◉ Arquitecturas con bajo acoplamiento
◉ Control de versiones
◉ Monitorización / Notificaciones proactivas
17
Accelerate: The Science of Lean Software and Devops (link) / DORA Report 2018 (link)
18. Automatización de Tests
◉ Práctica técnica XP (TDD, Customer tests)
◉ Tests unitarios (rápidos), integración, aceptación
◉ Otros tipos
○ Testing end2end
○ Tests de carga
○ Testing en producción
18
20. Integración continua
◉ Práctica técnica XP
◉ Rama principal siempre preparada
◉ Cada día todos a la rama principal
◉ Seguridad alta (TDD, Tests aceptación)
◉ Construcción automatizada
◉ No es: usar jenkins en Feature Branches
20
21. Desarrollo en Trunk
◉ No feature branches o menores de un dia
◉ Incrementos muy pequeños (menos de día)
◉ Cada incremento a rama principal
◉ Requiere
○ Feature flags
○ Cambios en paralelo
○ Saber dividir en pequeños incrementos
21
https://trunkbaseddevelopment.com/ (link)
22. Arquitectura bajo
acoplamiento
◉ Orientada a servicios
◉ Bounded Context (DDD)
◉ Arquitectura Hexagonal / Clean Architecture
◉ Cada servicio
○ Despliegue individual
○ Cambios autonomos
22
30. “
According to Gartner 70% of the IT market is focusing
on DevOps and another study found that 88% of
organizations have adopted agile, but only 26% of
organizations have broadly adopted test automations.
Chris Richardson
30
31. “
According to Gartner 70% of the IT market is focusing
on DevOps and another study found that 88% of
organizations have adopted agile, but only 26% of
organizations have broadly adopted test automations.
Chris Richardson
31