O que uma enterprise deveria fazer nos primeiros 90 dias

Notas do Editor

• #3: Agora, antes de iniciarmos, eu gostaria de fazer algumas perguntas: - Quem aqui está começando na nuvem? Levantem suas mãos. - Quem tem alguns workloads na nuvem e está fazendo algum movimento para ter mais? - E quem já tem um número significativo de workloads na nuvem? Levante sua mão Great! So I know from the feedback we took when you registered that 15% of people attending don’t use the cloud, 24% are experimenting with the cloud and 42% are running multiple workloads in the cloud – and specifically with AWS. The smart ones in the room will have worked out that that doesn’t add up to 100% but if you recall back to Pauls opening you’ll know we’ve broken down the detail allot more and I’m just sumarising – but what does it all mean – well means that more than a third aren't really using the cloud at all and for those on that journey you are not alone and help is on hand. Last question, those of you who have workloads in the cloud, who failed somewhere along the way?  So, what I can tell you is that’s ok, and you will have mistakes along the way, but the great thing about the AWS cloud is that it allows you to significantly reduce your cost of failure as a business. Infact the cloud allows you to take situations that would have previously been seen as costly failures, learn, pivot and invent
• #4: Now, For those of you who saw Max’s presentation just before this one you will be familiar with the Seven Steps…...... for those who didn't I'll do a quick recap. Through years of work helping customers migrate and invent in the cloud we've defined seven key steps to follow to make sure the journey is successful Executive Sponsorship - make sure you secure you stakeholders and bring them on the journey with you, organisational change is tough and you need your executives onboard Education – be sure to train both your technical and *importantly your non technical staff on the cloud Experiment, Find a hero workload that you can migrate easily and will deliver a good return Hybrid operations – provide centralised expertease to support your decentralised innovations Program and planning – make sure you have a plan that suits your business Organisational change – define and manage your structural and cultural change Cloud first – create a vision for a cloud first strategy across the entire business
• #5: It’s an obvious statement but Cloud adoption is more than just technology, and every single organisations journey is unique…so these steps aren’t always linear Today I’m going to focus on a three of the seven steps, that will help guide you in the first 90 days and look at how to plan, experiment - find that hero workload and begin formulating your cloud centre of excellence
• #6: So, lets get started.
• #7: Now it’s no secret that IT projects are a challenge, and only 39% are delivered ontime and on budget and a stagering $250m of every billion spent is wasted. I spoke about reducing the cost of failure before but you can also significantly reduce the risk of failure by doing a few simple things – it’s seems obvious but you have to have a plan
• #8: There are many factors driving your move to the cloud, datacentre consolidation, real estate decisions, contract changes. Where before companies often saw cost reduction as a strong motivating factor for cloud adoption, in order to stay competitive and relevant for their customers, enterprises now have to look at agility and innovation as keys drivers
• #9: And your plan should address all of these areas because these questions will be on the minds of everyone in your organisation But the good news is that planning Cloud Transformation doesn’t have to be like the traditionally designed monolithic Programs, where months of planning are spent up-front before any migrations occur.  pilot migrations can be undertaken in parallel to the planning activities so the results and learnings can be incorporated into back into the planning.  The successful results of the pilot can be used to help secure stakeholder buy-in
• #10: Whilst you’re working on your plan and many things can run in parallel these are the critical enabling activities you must consider fist - Envolver time AWS: AM, SA, Proserve, Parner (independente do canal) Engage your account team – we have a lot of people and resources who can help you, solutions architects with areas of deep domain expertise, technical account managers and of course your account manager Engage a partner – specifically where you have skills gaps. Nearly all the successful cloud migrations we’ve seen have involved a partner Identify your AWS champion – it could be yourself or someone within your team who has a good understanding of our services or the curiosity to learn Set up your AWS account structure – doing this early will help no end and is fundamentally important especially in large organisations where you have multiple departments. Com apoio da Amazon. Set up a VPC – virtual private cloud, plan the design for this, it could be similar to your data centre or on premises design Organise your telco links and direct connects – this is often overlooked but can be one of the longest lead times Make use of tools in the AWS console. These can help with usage and security, giving you dashboard views of your environment. Now another useful tool that isn’t mentioned there is Cloudwatch this allows you to monitor your AWS resources and the applications you run on AWS in real time. Tagging – setting a structure for tagging your workloads will pay dividends in the future, especially when you are looking at cost centres and cross charging And finally compliance – security is really important and *can get left until late in the planning if you don’t have a clear owner – some of the console tools, particularly Cloud trail, and AWS config can help with this. So there’s a lot of detail there but my takeaway piece of advice would be to engage us – we are here to help and can navigate you through these steps  Atuacao em reguladores
• #11: Once you’ve run your cloud discovery workshop, consumed the results and started to deliver on this you need to structure your IT teams Now first if we look at the Traditional Shared Service Model it currently – and I emphasise currently Works well Well understood Standardised Existing processes Cast of Specialists Clear lanes But this won’t sustain an agile cloud environment So you might be tempted to move to an Ad Hoc structure where you insert cloud into one small group within a business unit, but in this scienario Everyone does their own thing Silos created Non-standardised Non-centralised governance Best practices not shared Security risks Duplication of work Inconsistent tools Cost tracking hard
• #12: So we would recommend this   Center of Excellence (COE) Provides leadership in defining and executing the cloud strategy, technical design, operational standards, best practices and training Acts as a liaison and enabler to the Business for standards, patterns and best practices; and, also transitions newly built cloud infrastructure to the Cloud Operations team to run and operate. May only exist in an “interim” basis, helping the enterprise draw and organize resources and domain experts from various teams such as network, information security, storage, and systems Initial involvement of the COE team members is typically high when the new cloud infrastructure is being built out and processes are being defined
• #13: Once you have your plan and you’ve checked off your critical enablers you can address the challenge of structuring your operations
• #14: As organisations consider their business drivers, organisational context and challenges in adopting cloud, naturally a lot of important questions are asked across the organisation. So I talked about these questions earlier in the planning phase but they need to be addressed in this next step Questions like: Why are we doing this? Where should we start? How fast can we go? How fast should we go? Who needs to be involved? How should we govern it? Which apps should we move 1st, 2nd, 3rd or not at all? How should I structure my organisation in a post-cloud world?, or How can I transform my culture and processes How can I plan and manage a multi-year data center exit?, or These are all really good and important questions right?  As you can see a lot of these questions are strategic in nature, and non-technical.  All of these questions need to be answered if you’re going to embark on an Enterprise-wide cloud adoption journey.  From our experiences, we’ve seen that when these questions are not answered, then organizations fail to get their cloud programs off the ground, or they stall at some point. So this brings me onto the AWS Cloud Adoption Framework. After working with hundreds of enterprises world-wide we took all of the questions we were getting from the field and compiled a cloud adoption framework (what we call the CAF).  The CAF is a framework that provides concepts, patterns, and best practices to deliver and operate cloud-enabled IT environments, and we use it to guide the development of cloud adoption roadmaps for our customers. And if you follow this method you will be successful So - When we looked at the questions we found they fell into 6 categories, or what we call Perspectives. The figure shows the six Perspectives of the CAF, Business, Platform, Governance, Security, Operating, and People Business Perspective – addresses the questions related to why am I doing this, what value & outcomes will I get from cloud, what is the TCO/ROI of my investment, how will I measure success. Platform Perspective – addresses the best practices around integrationing the AWS cloud platform with your organisation’s current environment, and covers networking, AWS account structure, SOEs etc Governance Perspective – addresses the questions around how the cloud program and initiatives will be executed and governed. How will you stick to timelines and budgets Security Perspective – addresses the questions around what your security architecture & posture will look like in the cloud, and define how you will design, build and operate securely. Operating Perspective – covers the operational processes used to run and operate workloads in the cloud, do you have manual high touch processes now and can these be re-designed People Perspective – looks at the skills, roles and organisational structures needed to effectively run and operate your cloud environment. The Business Perspective is typically the first perspective that organisations start with, but if say you’re kicking off a PoC to understand the value the cloud may bring to your organisation, you might start with the Platform perspective and focus on getting the foundational architecture components in place, such as your networking, AWS Account structure, etc. So what we would suggest you do is run a cloud discovery workshop with senior leaders across the business affected by each perspective and it’s really important to make sure each area is represented. This will then help you understand our current state and using the perspectives understand what needs to change in order to achieve your desired state. It also allows each area to voice concerns and raise ideas to ensure you have a water tight plan
• #15: All the activities and outcomes in Migration offerings are based on the new CAF 2.0 perspectives.
• #17: Right! you have a plan, and a team – now it’s time to start the process You don’t need to spend weeks or months up front doing theoretical business cases and modelling before getting started.  We see the successful companies performing POCs & experimenting to demonstrate the value of cloud with a few initial high-impacting applications and they use the learnings and results from these to accelerate their cloud journeys.
• #18: First things first, Create an MVP minimal viable product or a find a hero workload. It’s really important to find some quick and easy apps to move – ones that don’t necessarily have to be redesigned and if you can find one that gives you a quick financial return then all the better. Let me give you an example here, we started working with Qantas a number of years ago on their international route simulation, the original use case for the move to the cloud take advantage of the huge compute capacity available. previously they could only afford to anaylise high level data such as weather and traffic. But once they started and realised they could process so much more they were able to take a deeper look into their data and the results were phenomenal. Qantas were able to change their routes to not only save millions on fuel but also change their flight paths to become more competitive. So a small project to take advantage of compute power was able to change and excite the entire business.    
• #19: So as I said earlier, no one journey is the same and the process isn’t always linear but here’s an example of a simple process you can take and iterate on Start by Creating a scrum board – use a program like Jira to track the weekly work which allows you to set achievable goals, track progress, and estimate the completion date. Engage your AWS Account team and Technical account managers early on in the project.  Share your go live dates so we can help with any roadblocks you might encounter the next step is to learn and build a POC or staging environment on the cloud platform. this is so that you can load test the environment to ensure you can run existing workloads on a virtualized platform. Ensure the builds are automated and architected for High Availablilty Data Migration – build a process to move existing data into the cloud – choose the right method (if you have large volumes of data petabytes for example then could use snow mobile. Also consider if you do need to encrypt the data in transit.    Test and Optimization – perform a complete end to end test to ensure you can run critical workloads under peak operating conditions.  This is where you identify and optimize your application.   Build a monitoring environment – you can leverage something like cloud watch Now during this process it’s critical to do three things Foster an environment of continuous feedback. Be as agile as possible. Limit each foundational step to a sprint. Refactor early to mitigate risks. Then you can take the learnings from this process and feed this back into your cloud transformation strategy You can then move from a POC to migrating applications following the same steps
• #20: Now you’re up and running this is an important point, the cloud is highly cost efficient when you use it correctly. You can get a massive cost-reduction initially through cloud migration patterns like S3 storage, managed databases, right-sizing via auto-scaling.  However, these returns will be reduced on subsequent optimization cycles. So it’s important to engage your account team at this stage to help you review your architecture and environment. We have some great tools that can dive deep into useage and we can advise on solutions like reserved instances and SPOT Custo por transação fica o mesmo por conta da automação
• #21: Your first 90 days on a page. Plan and don’t forget your critical enablers - Set a goal to have 1, 2 or 3 important workloads in the cloud by date X. 90 days is perfect because it’s a realistic and an achievable time-frame to hit the target based on our experience. Hold a Cloud Discovery Workshop Start to form your Cloud Centre of Excellence team Build out your Cloud Platform MVP and do some POC migrations of 1-3 high impact hero workloads that will get your organisation excited. As you get more learnings from POC migrations, start to design your future cloud operating model, business case and transformation roadmap.
• #23: 1 – Objetivo e resultados do projeto. 2 – História Inter e analogia Nuvem vs. Banco Digital: Nuvem pessoal olha pro céu… excelente jogo de marketing, e representa muito bem milhões de servidores virtualizados… Banco Digital é a mesma coisa, o pessoal nao entende num primeiro momento. Temos tudo que um grande banco tem, entretanto digitalizamos todos os processos (ou quase todos) Passa pelo HUB e Democratização Bancária com nossos pilares E como Steve Jobs, e só mais uma coisa: Totalmente gratuita 3 – Visão do diretor Executivo Banco Inter
• #24: O desafio é esse… meu presidente quer chegar em 1MM de contas, nós queremos estar preparados para 10MM AWS não é pelo pico, e sim pela arquitetura.
• #25: Onda 1 site institucional e os serviços de abertura de conta Então, avançaremos para a parte transactional, App CD, IB, etc
• #26: Diagrama de solução, e explicar a solução, vantagens, etc Explicar teste de stress – Ver na prática esta arquitetura funcionando O valor que isso tem só sabe quem viveu uma campanha de e-commerce pesada, Black Friday Final – este é o básico de AWS, estamos mirando todos os outros serviços
• #27: And if you were to take away only three things from today, these are my top tips – do this and it will allow you to create a platform for success.