Coté

“On the business side, Progressive Delivery involves two core changes in the delivery model: Release progression – progressively increasing the number of users that are able to see (and are impacted by) new features (e.g. Stage 1: visible to developers only; Stage 2: visible to developers and beta users; Stage 3: visible to more users; Stage n: visible to everyone) Delegation – progressively delegating the control of the feature to the owner that is most closely responsible for the outcome.

“On the business side, Progressive Delivery involves two core changes in the delivery model: Release progression – progressively increasing the number of users that are able to see (and are impacted by) new features (e.g. Stage 1: visible to developers only; Stage 2: visible to developers and beta users; Stage 3: visible to more users; Stage n: visible to everyone) Delegation – progressively delegating the control of the feature to the owner that is most closely responsible for the outcome.

“Kubernetes was created to bring the idea of dynamic, container-centric, managed, scheduled-cluster thinking outside of Google… But what is a container and what does a containerized application mean in this context?” Original source: Kubernetes for the Kubernewbie - The Journey

“Kubernetes was created to bring the idea of dynamic, container-centric, managed, scheduled-cluster thinking outside of Google… But what is a container and what does a containerized application mean in this context?” Original source: Kubernetes for the Kubernewbie - The Journey

“Also, it is recommended to not deploy to all production environments in one go, exposing all the customers to the changes. A gradual rollout that exposes the changes to customers over a period, thereby implicitly validating the changes in production with a smaller set of customers at a time… As an example, for an application is deployed in 12 regions with US regions (4) having a high load, European regions (4) having a medium load and Asian regions (4) having a relatively lighter load, following would be the order of rollout.

“Also, it is recommended to not deploy to all production environments in one go, exposing all the customers to the changes. A gradual rollout that exposes the changes to customers over a period, thereby implicitly validating the changes in production with a smaller set of customers at a time… As an example, for an application is deployed in 12 regions with US regions (4) having a high load, European regions (4) having a medium load and Asian regions (4) having a relatively lighter load, following would be the order of rollout.

How do you implement IT Automation best practices at a large company? What’s the best approach to convince stakeholders that IT Automation is worth the effort? In this interview with Acxiom’s Chris Donaldson we talk all about the good, the bad and ugly of IT Automation. Also see full show notes.

“Getting feedback on the effectiveness of the initiatives, and acting on it quickly to refine the strategies and initiatives to ensure their alignment with the purpose is critical for sustaining the effectiveness of the organization towards fulfilling the purpose.” Original source: Q&A on the Book Enterprise Agility

“Getting feedback on the effectiveness of the initiatives, and acting on it quickly to refine the strategies and initiatives to ensure their alignment with the purpose is critical for sustaining the effectiveness of the organization towards fulfilling the purpose.” Original source: Q&A on the Book Enterprise Agility

“The tiny margin in CA’s enterprise software business, which contrasts with its richly profitable mainframe division, won’t help Broadcom hit its projected EBITDA targets, no matter how many ‘adjustments’ are made. In fact, the division stands in the way.” Original source: Broadcom can’t get there from here