agile

Networking and security management, based on firewall policy configuration operation, has historically been very difficult because of the high complexity of networks, and the diversity of the different firewall vendors. Thus, while DevOps are performing agile server configuration management, the firewall rules that define the application connectivity are still managed in the old-school way, introducing a bottleneck into the software and infrastructure delivery pipeline. In this talk, we'll show how to abstract, describe and attach the application connectivity description (policies) to the infrastructure specification as high-level intents into a multi-vendor and multi-technology network (in-premise, cloud-based, PaaS-based, etc.) ensuring continuous compliance and that all potential problems are detected before the policies are provisioned into the infrastructure.

These are some interesting talks and podcast episodes that I heard in may:Business agilityFearless Change: Patterns for Introducing New Ideas Linda RisingS1E08: Corporate Liberation with Isaac Getz LeadWise podcastBossLevel Podcast Stan McChrystal From Craft Conf 2017:Scaling Lean: Principles over Process Jeff GothelfThe Build Trap Melissa Perri Decisions Decisions Dan North Tech Lead Skills for Developers Patrick KuaUnsortedAchieving High Load in Adv...

These are some interesting talks and podcast episodes that I heard in may:Business agilityFearless Change: Patterns for Introducing New Ideas Linda RisingS1E08: Corporate Liberation with Isaac Getz LeadWise podcastBossLevel Podcast Stan McChrystal From Craft Conf 2017:Scaling Lean: Principles over Process Jeff GothelfThe Build Trap Melissa Perri Decisions Decisions Dan North Tech Lead Skills for Developers Patrick KuaUnsortedAchieving High Load in Adv...

After my talk El arte del patadon pa'lante / Libro de recetas (Spanish) at the Pamplona Software Craftmanship 2017, some colleagues ask me about references for evolutionary architectures. This post tries to give the best references I know about this concept...To have context for the other references, I find the following resources essential:Who needs an Architect? (Martin Fowler)Competing On The Basis Of Speed  (Mary Poppendieck)  Optimizing for speed, flow, and waste re...

After my talk El arte del patadon pa'lante / Libro de recetas (Spanish) at the Pamplona Software Craftmanship 2017, some colleagues ask me about references for evolutionary architectures. This post tries to give the best references I know about this concept...To have context for the other references, I find the following resources essential:Who needs an Architect? (Martin Fowler)Competing On The Basis Of Speed  (Mary Poppendieck)  Optimizing for speed, flow, and waste re...

In Agile, we value “working software over comprehensive documentation” - there is value in documentation, but we value working software more. This helps us get things done and avoid waste. However, extremes are very common: teams who avoid documentation altogether (“our code is self-documenting”), or teams who create way too much documentation. This talk will cover how to leverage documentation to improve team documentation, align everybody to a common vision, as well as underutilised forms of documentation that go beyond drawing the current system state.

"Agile. Una palabra del día a día. Todos somos Agile. En esta charla analizaremos lo que realmente significa eso hoy en día y veremos que es mucho más de lo que nos pensamos porque su verdadero significado se ha diluido con el tiempo. Volviendo a las raíces de la palabra, veremos que hemos puesto en práctica el concepto en Tuenti, no sólo enfocándonos a procesos sino también al código." Descarga gratis la versión digital del libro de Roberto Canales “Conversaciones con CEOs y CIOs sobre Transformación Digital y Metodologías Ágiles ” https://goo.gl/i2zZtJ Facebook; https://goo.gl/o8HrWX Twitter; https://goo.gl/MU5pUQ LinkedIn https://goo.gl/2On7Fj/

Presentación preparada entre Luis Artola y yo mismo para la para la Pamplona Software Craftmanship 2017Videovideo scpna2017-el-arte-del-patadon-palante-libro-de-recetas Muchisimas gracias a Autentia por el Video (AutentiaMedia youtube channel) (Post de Autentia con todas las charlas Pamplona-software-craftsmanship-2017)Slidesscpna2017-el-arte-del-patadon-palante-libro-de-recetas SCPNA2017 El arte del patadon pa'lante / libro de recetas de Eduardo Ferro Aldama Referencias:CAS201...

Presentación preparada entre Luis Artola y yo mismo para la para la Pamplona Software Craftmanship 2017Videovideo scpna2017-el-arte-del-patadon-palante-libro-de-recetas Muchisimas gracias a Autentia por el Video (AutentiaMedia youtube channel) (Post de Autentia con todas las charlas Pamplona-software-craftsmanship-2017)Slidesscpna2017-el-arte-del-patadon-palante-libro-de-recetas SCPNA2017 El arte del patadon pa'lante / libro de recetas de Eduardo Ferro Aldama Referencias:CAS201...

Metaphors are a great tool to explain other people complicated concepts. Often, they help us to drive interesting conversations and expand the boundaries of the knowledge we have by borrowing ideas from other fields.In the Software industry, it seems like one of these metaphors is particularly strong, the one that tries to explain software as building houses. We even use it at our universities to introduce the topic to newcomers.In my opinion, this metaphor is not only wrong but also very danger...