Link: Configuring your release pipelines for safe deployments

“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.”
Original source: Configuring your release pipelines for safe deployments

Link: Configuring your release pipelines for safe deployments

“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.”
Original source: Configuring your release pipelines for safe deployments

Link: Progressive Delivery, a History…. Condensed

“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. (e.g. Stage 1: Release owner = dev. Stage 2: Release owner = PM; Stage 3: Release owner = Marketing; Stage n: Release owner = Customer Success)

An important point about delegation: while the initial implementation likely involves both the assignment of responsibility as well as the need for manual approval or action, the goal should be to base all of the delegation changes or release progressions on criteria and use metrics and event data to automate the transitions.”
Original source: Progressive Delivery, a History…. Condensed

Link: Lessons from Elad Gil and High Growth Handbook

It’d be useful at some point to compare the “how to be a startup” advice to “how to modernize and suite of enterprise applications.” For example, an enterprise often knows its product/market fit (e.g., selling kidnapping insurance to executives). However, it may not know the best product/technology approach (it needs a mobile app that tracks when the executive leaves the country), or product/design fit (the executive’s assistant does most of the interaction with the software, so you need to add a secondary user).

For enterprises, there’s much to be learned from startup think, but there’s also much that’s different.
Original source: Lessons from Elad Gil and High Growth Handbook