Scenario 1:
A start-up wants to develop and demo a product (software) to multiple customers. All employees (less than 25) are technology savvy. Average age less than 25. What should go to cloud?
- Everything
- Test & Development
- Production and demo
- Mail, collaboration & IT applications
Scenario 2:
A consulting company well established for last 10 years. All employees are using current applications and are happy. Average age more than 30 years. What should be cloud strategy?
- Everything
- Mail, collaboration & IT applications
- Nothing
- Look for Saas based IT applications to move first
Scenario 3:
Global IT Services company with more than 20 years in business. 50% of employees are below 25 years. Everyone not happy with what they get to use or not as per company policy. What options should CIO pursue?
- Create Privet cloud for company
- Move DR, Test & Development to AWS
- Move to Google Mail from exchange for majority or all employees
- All of the above
Scenario 4:
A High performance computing facility is required by a company to complete and deliver a project in a mature and not so fast growing market.
- Lease Servers
- Go for On demand Servers
- Use to AWS (Amazon Cloud) for delivering the project
- Create Privet cloud
Scenario 5:
A CIO who always wants to be using cutting edge technology for a fortune 500 company.
- Plan strategy to move to Public cloud in next 4 quarters
- Create Privet cloud within next two quarter
- Look at IaaS, PaaS and SaaS and target all SaaS implementations first
- Do nothing - it is too risky to take any side now!
Let's select only one option in all 5 scenarios
Comments?
-Cheers
Scenario 1: Everything should go to the cloud as it would be depending on growth/success of concept, huge investment in in-house infrastructure might be difficult to wind-up in terms of failure of concepts.
ReplyDeleteScenario 2: Look for SaaS based IT applications to move first as “Mail, collaboration” are backbone to consulting company, moving everything might be over kill, while employees are already happy.
Scenario 3: Move to Google Mail from exchange for majority or all employees, as new collaboration tools are expensive to build in-house, new generation loves to use new tools rather then send email and wait Approach. Google mail comes with other google tools e.g. gvoice, wave etc. this will make them happy and save cost on exchange cals.
Scenario 4: Use to AWS (Amazon Cloud)EC2 kanda.. Or Go for On demand Servers, detailed roadmap is needed to perfectly capture peak in processing required during all phases of project. Apple’s iphone4 delivery might be good example failure in private cloud.
Scenario 5: Look at IaaS, PaaS and SaaS and target all SaaS implementations first, this is the approach I am taking now as legacy applications can not take advantage of cloud and investment might be wasted with untrained staff.
/KP
Scenario 1:
ReplyDeleteConsidering younger population and size initially it makes sense for Start-up Company to put everything on cloud so that they can concentrate on their core function. Once established and on a growth path they may consider to bring back Production and Development environment to in-house from cloud, as running everything from cloud for more than couple of years may not be cost effective.
Scenario 2:
Initially look to move SaaS based IT application on cloud and a feel of experience. For a consulting company most of the time consultants will be out of office at client locations hence moving mail and collaboration application to cloud will be useful. Moving everything on cloud may be a option as consider amount of CAPEX has already gone into building in-house infrastructure.
Scenario 3:
Move to Google mail from exchange which will give better experience to employees with 50% younger population adopting to change won’t be a challenge. To give facilitate employees try to get Google collaboration tools such as Gtalk, Google voice and blogs with mail solution. This in turn will help to increase productivity and save software license cost. DR, Development and testing environment should remain in-house as it is the key for IT Services Company.
Scenario 4:
Assuming high computing power is periodic/seasonal requirement and not a permanent need, going for on-demand servers is a good option. Examples could high computing requirements for Wall Mart or other retail chains during “Thanks Giving Weekend”. AWS may be useful for complex product or application testing which needs to be carried out during quarter end month.
Scenario 5:
Definitely create Private cloud within next two quarter using Vblock0 components. Due to multi-tenant functionality, private cloud can be used to provide IaaS service offering to clients and hosting internal production service. Once public cloud concept is matured, moving development and testing environment to public cloud is an option available with CIO .
SG
Scenario 3: on reading this scenario again it makes sense to go with all these options as easy adoption by young generation. Hence I would “go for all”
ReplyDeleteCreate Privet cloud for company
- Move DR, Test & Development to AWS
- Move to Google Mail from exchange for majority or all employees
Scenario 5: if company’s main function is not IT I would try and avoid building anything in-house, as getting change acceptance and adoption in those fortune 500’s organizations is very tough.
Scenario 3:
ReplyDeleteEstablished IT Service Company should look at creating IaaS service offering by creating private cloud and also using it for internal use. Creating private cloud only for internal use may not be cost effective solution as initial CAPEX investment is huge to build “true” private cloud.
Scenario 5:
Ideally fortune 500 companies’ needs to adopt 1st three options; may be in a phase manner. These companies don’t have any problem with CAPEX spending. Even after having a internal private cloud it makes sense to go with SaaS model for their sales organization and for collaboration tools by using SalesForce and WebEx respectively. Eventually company will have to look at hybrid cloud by integrating private and public cloud.
In all the above scenarios, shifting to cloud will be looked at from different viewpoints.
ReplyDelete1). Risk
2). Service
3). Money, etc.
Typically it comes down to a number which will make sense to a CIO.
Fundamentally - Don't look at numbers, numbers will usually always be correct. Each company will need to look at the assumptions that go into calculating these numbers, I doubt that these assumptions will usually always be incorrect.