20161024 CFC Keynote - Transformation enablement

Notas del editor

• #10: Why this Slide: You are trying to setup the struggle between IT and Business – you have to run a huge portfolio of apps, the business always wants more apps but you are struggling to just keep running what you have. In part this is also to cement that you are an expert and you understand their challenges. Key Points: Setup CHANGE is constant – you are being asked to do more with less Business Pressure to innovate IT Challenge of just operating IT takes most of the time/budget/resources Transition to NEXT Slide: How will you put yourself in a position to rapidly deploy new tech to drive bus innovation?
• #11: Why this Slide: You customer/audience is interested in Azure BUT they also have a data center to run today – you are trying to setup that you understand they have many challenges running their own data center and that they need help to do this that goes beyond virtualization – which was a good step. You also want to setup the Public Cloud and SaaS pillars because the combination of Private Cloud + Public Cloud + SaaS is THE Microsoft all up differentiator against ALL competitors. Key Points: You have a large DC investment – you have moved to a highly virtualized DC – but not getting all the benefits you expected You are looking at Public Cloud – this is the moment to cover the Cloud Business Model – (1) You pay for what you use (2) You can change your mind This business model changes OUR relationship – we have to make great stuff or you will stop using it AND we have to help you adopt and consume or our sales people don’t get paid – we are in this together…! SaaS is MASSIVE – lot’s of opportunity to STOP running app infrastructure – O365 and SalesForce – multi-billion $ businesses – proven..! Transition to NEXT Slide: So, how can Microsoft help..? What’s our strategy and how are we different to everyone else…?
• #12: Why this Slide: This is the Key Differentiator – no one else is going to help the customer in their own DC, has a world class public cloud which is also a SaaS platform and has killer SaaS apps as well – Customers want all this – we have it. Key Points: Start setting the stage for what is Azure – very high level – it’s IaaS AND PaaS on top of a global DC infra – but it’s just software We can/will bring this software stack on-prem to help the customer with their own DC challenges We have killer SaaS apps that help the customer stop doing things – like running email systems. Our Platform is a platform for SaaS – if the customer is an ISV – benefits are building higher value SaaS service and/or keeping the “old” model of selling into the Customer DC… Position the Competition – Old Guard on left (IBM, Oracle, HP), Cloud Platform Vendors (AWS, Google) on the right only, Salesforce in the middle (only) – MSFT does it all. Transition to NEXT Slide: Summary – our strategy is 100% aligned to your strategy – but don’t just take my word for it, let’s see what some key influencers have to say…
• #13: Why this Slide: Extra weight to tell the story of our unique strategy – IMPORTANT – you are not selling a product or even a platform – you are really selling a long term vision – and you have to sell this high up. Key Points: Don’t go into any detail here, don’t get drawn into any specific MQ MAIN POINT – MSFT continues to innovate – we are a true software and platform company and we have been doing this for 30 years (this is a dig at AWS mainly) We are persistent – we strive but don’t always succeed to be the leader (be humble, but land that we have long term horizons, we will be there, we don’t back away from hard problems) Transition to NEXT Slide: So let’s start understanding in more detail WHAT is Azure.
• #14: There are many different numbers you can pull in here from the all up “quotable statement list” maintained by PR which can be found here: https://microsoft.sharepoint.com/teams/WAG/PM/Shared Documents/roadmap (in the Quotable Statements document).
• #15: P2
• #16: Why this Slide: This is the same as the previous slide except that the names are not service names, they represent IT Capabilities… Use either OR BOTH…
• #17: Why this Slide: It shows we have a very broad platform. It about BOTH IaaS and PaaS, that these work together. It shows that we continue to lead in world class IT capabilities and that there’s really nothing missing. Key Points: We have already seen how the Azure Platform is IaaS + Pass – but I want you to understand that this is a huge number of capabilities – IT building blocks if you will. Every one of these blocks you provision anytime, self-service anywhere in the world 24x7. You pay for what you use, you can get more or less anytime and you can fully automate everything… DON’T spent too much time on this slide – you are going to DEMO (aren’t you!!!)… DON’T go through each block… Transition to NEXT Slide: Make the build go backwards to show JUST IaaS and then you will go to the demo to show it.
• #18: 112
• #19: DevOps is a relative new term, people refer to individual capabilities to automate the release pipeline as DevOps. However, DevOps is more than that is increasing the scope of agility and should be view as a team undertaking. It requires teams to look at their full lifecycle investments. At its core DevOps enables better software development and enables delivery, accelerating last mile of continuous delivery.
• #20: What is driving DevOps? The agile methodologies are accelerating the construction process and creating a significant pressure to Operations teams to update their existing practices to make enable faster cadence, in other words changing and adopting existing process to not only be reliable but also support and agile cadence. In our internal teams and with some of our enterprise customers we noticed that once a team is able to accelerate the construction phase consistently. The next evolution process is to ensure such applications remind available and performing as expected. And when they aren’t having access to information and tools that allow both Operations and development teams to diagnostic and fix issues quickly. Then these teams become more sophisticated and mature and then they want to have access to customer usage information to use quantitative and qualitative data to help them determine the next set of investments and enable continuous learning.
• #21: Companies looking at implementing DevOps practices are balancing two important performance indicators. Agility: their ability to increase deployment frequency and reduce change lead time to react to dynamic business needs. And Reliability: reducing change fail rate and reduce the time to take them to detect and repair production issues. These are very hard to balance metrics and create friction across teams.