In a previous post, I talked about developing a criteria triangle, with the bottom being the systems/data layer, the middle the objectives/tactics layer, and the peak the strategic results layer. The objective is to make sure the criteria that you select hit in the middle and upper layers of the triangle, where folks work in the realm of business results day in and day out.
Transformation & Agility
Transformation & Agility concerns the utilization of the technical agility derived from the benefits delivered by virtualization and cloud computing, coupled with Agile Development practices that improve business agility, performance, and results. This includes the agility derived from: (Read More)
- The implementation of Agile and DevOps methodologies
- The application and system architectures
- The implementation of IaaS, PaaS, and SaaS clouds
- Monitoring of the environment, coupled with processes for resolving problems quickly
- Having continuous availability through the use of high-availability and disaster recovery products and procedures
Transformation covers the journey from A to Z and all points between: how you get there and the roads you will travel; how decisions made on day zero or one, or even day three, will affect later decisions; and what technical, operational, and organizational pitfalls can be associated with an implementation. We examine what tool sets are required for Agile Cloud Development, and it delves into other aspects of Agile Development that integrate with cloud computing, SaaS, and PaaS environments, including DevOps, Scrum, XP, and Kanban.
A key step in putting together a business case is to ask, “Who cares about what?” “Who” is your audience: the decision makers. “What” is their criteria. The purpose of this step is to accurately determine your audience for your business case and the factors they will use—their criteria—in making their investment decision.
Many parallels are drawn between containers and VMs. At the same time, container evangelists are often quick to position containers as a replacement for virtualization. As is always the case, the new is different from the old but can learn from the past. Containers and VMs address different part of IT/IS, so they are not directly competing. Containers do not always remove the need for VMs, nor are containers always deployed where VMs could be used. Container deployments are likely to suffer some of the same issues that VMs experience with enterprise customers.
A new generation of private cloud environments is being created now, ones where all the management is done via SaaS. This way, the heavy lifting is done by others, and you inherit an IT as a Service environment ready for you to add new workloads without worrying too much about upgrades, management constructs, or even, in some cases, security controls. It is all done for you. For many companies, this is one way to transform to an on-premises cloud and then to a hybrid cloud. There is a growing list of players; however, the first out the door are ZeroStack, Platform9, and SkySecure from Skyport Systems.
If you have been following IT infrastructure for a while, you will have seen the rise of the cloud hailed as the solution to all of our IT problems. You will also have heard that the public cloud is like Hotel California, where you can easily check in but can never leave. I wrote a little while ago about the risks of relying on a single cloud service and the need to use multiple clouds. In order to use multiple cloud providers, you must use them in such a way as to minimize the barrier to exit. And that means using cloud-portable applications.
When we talk about transforming to the cloud, we often talk about hybrid cloud and what it will take to transition to it, leaving discussions about 100% cloud usage purely to the new startup (greenfield) organizations. What is needed to move 100% off-premises to a public cloud? What is sufficient, what is necessary, and what is the required last mile of this effort? I recently spoke to @AndiMann about concepts of what is necessary and sufficient. Andi brought up some great points I would like to share over a series of articles.