Cloud is one of the core components during an Agile Development process. What are the enterprise viewpoints for going for a cloud? There are no two thoughts that the entry barrier for a new company to launch a platform on the cloud is low, but enterprises who have been running these systems for ages - is it viable to move to the cloud and be more agile. How do the economics work?
Cloud is seen as the means to competitive superiority, but if implemented wrong it can spiral out of control. The talk explains the various concerns the enterprises see when adopting the cloud.
- Capex vs Opex
- Tax benefits
- IAAS, PAAS, everything as a service! How the costs vary
- Adoption concerns
- Tools to monitor spends
- Tools to control spends
- Costs of these monitoring and control
- Costs of cloud neutral strategies
- Cost of migration
- Cost of training
- Cost of re-training the datacentre teams
- Cost of leadership effort
- Cost of adoption
With all the various costs, how to build the right mix of strategies to adopt cloud


Outline/Structure of the Talk

5 Minutes Introduction and context setting
10 Minutes on the basics of agile on the cloud
15 minutes of Cost benefit analysis including some case studies in large enterprises
5 Minutes of failure cases on agile adoption on the cloud and how thinking the waterfall/datacentre way in cloud can be disastrous
5 Minutes of Making the right choice on the cloud
5 Minutes of summary and QA

Learning Outcome

- Agile and waterfall ways of thinking on the cloud
- Economic benefits of Cloud
- Understanding of how agile ways of thinking helps in the cloud journey ( financial aspects )
- Real time Enterprise case studies

Target Audience

Any developer at any level of experience. Cloud know-how would be a benefit

Prerequisites for Attendees

Any software engineer (any level) would make good value of this presentation


schedule Submitted 2 years ago

Public Feedback

    • Abhinav Agarwal

      Abhinav Agarwal - Unbreakable Branches - Implement Continuous Integration with confidence

      20 Mins

      The concept of Pull Requests brought development and collaboration to the next level. Thus, developers can now work in isolation and submit their changes to approval through pull requests reviews and merge.

      However, merging a pull request does not guarantee that the resulting commit will build successfully on the target branch. In a context where tens of pull requests are created each day on a single repository, how to ensure that the merge operation will not break the target branch?

      Amadeus created the concept of Merge Request and Unbreakable Branches to setup a secured continuous integration. Come and discover how this feature can improve developer's efficiency and continuous integration in your company!