Cloud computing is the future of businesses. Adopting a cloud service provider is like building a house for specific end users. The needs behaviours, requirements and lifestyle is important in designing the product that will fit and excite that end user. The agile framework allows end users to be involved directly in product development, feedback loops and mechanisms are in place to guide quality product delivery that will meet the end users needs. This allows businesses to respond quickly and swiftly to end-user needs and market changing conditions so they can stay profitable and competitive in the business. There are several Cloud service providers and each provides unique services that can meet and user needs.
There are so many benefits to moving your business or infrastructure and applications to the cloud. Unfortunately, there are disbenefits too
These include agility of operations and product rollouts, response to changing markets and end-user behaviours. operational efficiency, adaptability, ease of operations, reduce infra costs, uptime optimisation, reduced FTEs, improved customer perceptions and more
Disbenefits include the possibility of a downtime, security and privacy issues (GDPR?), vulnerability to attack, perceived limited control and reduced flexibility, possible hidden costs
NOT HAVING A DEFINED RELEVANT BUSINESS CENTERED STRATEGY
Adopting cloud needs a rightly strategic objective, defined and agreed to success criteria, a full 360 degree view of the current business state and the future state compared and buy-in from relevant stakeholders. Beyond the hype of cloud popularity, it should always start with the rightly defined strategy. This should answer the question – ‘why are we moving to the cloud?’ This is usually answered through requirements workshops with all the stakeholders involved in the business.
NOT HAVING A PROJECT CHAMPION/CLOUD ADOPTION TEAM IN PLACE
Adopting a cloud strategy is a business centered (not IT) objective and should be owned and championed by a business representative. That is not to say that I T should not be involved in the decision and governance structure.
NOT DEFINING FUTURE AND PRESENT STATES TO IDENTIFY GAPS.
A roadmap usually provides guidance on expectations behaviours structure and more that will help the business get the best out of the cloud adoption
NOT HAVING A DEFINED SUCCESS/ACCEPTANCE CRITERIA
Once the strategy is defined and fleshed out the next step is to outline what a cloud adoption strategy success looks like. This is usually gathered through another or joint requirements workshop with the strategy definition.
Down the line, a benefits case is defined, gathered and listed for the business case. Usually, the benefits are qualitative and quantitative. Quantitative benefits can be measured while qualitative benefits are implied. These benefits are defined in conjunction with the present state of the business compared with a future state when a Cloud service is in place.
Usually the business case will contain one or more items defining in the rationale behind the cloud adoption project this include an executive summary, aims or objectives, the strategic objectives and reason for adopting the cloud, risks appetite, gap analysis, SWOT analysis, vendor analysis, vendor assessment, personnel resource requirements, a project plan, etc all starts with a define strategy. without the right strategy, there is no definite Direction on expectations and eventual delivery of the Cloud services.
No doubt AWS, Microsoft and Google lead the pack of cloud service providers, offering a public, private or hybrid cloud service. A lot of businesses are leveraging on the differences between this top three by combining services from multiple providers. For example, i can decide to put some applications i feel will work well with the infrastructure provided by google and a few others with Amazon.
It is pertinent to know that not all applications or assets can be put on the cloud. Legacy applications and those that are business critical are usually candidates for this.
Also, on the adoption of cloud, a robust governance and budget monitoring structure (Center of Excellence) should be in place. Regular value delivering monitoring should be carried out to identify savings, improvements and possible future direction in the cloud adoption journey.
THINKING ALL CLOUDS ARE THE SAME AND ANY CAN BE A GOOD FIT.
All cloud is not the same, they offer different fits for different requirements. It is in your best interest to keep an eye on the savings and benefits offered by these vendors. Measurement for fit is based on these seven conditions – storage, security, Compute, network, governance management, and provisioning. These criteria should be used to measure/assess the cloud capabilities and decisions made on answers received.
FOLLOWING THE CLOUD ADOPTION HYPE
Don’t put your assets in the cloud without a solid reason to. You must do your groundwork and be ready to face the consequences of moving to the cloud. Like every evolving tech, the cloud has its benefits and disbenefits. AWS had an outage in 2017 that set back publicly traded companies up to $150 million dollars. No organization is immune, especially when business critical processes cannot afford to be interrupted. It is up to you to decide.
I CAN HELP
As a business analyst consultant with some years of cloud implementation and discovery intitiatives, I help businesses adopt the right cloud service that is a good fit for them. Its not always about the hype of cloud adoption, but getting the reason for using the cloud. There are more benefits than disbenefits. Businesses need to know of the two. Decisions should be made based on a full 360 degree view of perceived cloud capabilities and helping businesses make this decision is what i do.
My other capabilities include web design, Robotics Process Automation implementation, Software and mobile applications delivery in an agile framework. I can help your teams and your business become better.
Let me know if i can help you in your cloud adoption journey today. Contact me today