Microsoft DevOps Solution - DevOps

Editor's Notes

• #2 Introduction : Introduce myself , background (maybe) Agenda 1. Presentation 2. Video – Demo Demo 1 – End to End DEV Ops 3. VM – to showcase any specific topics if needed.
• #3 Disruption affects every industry and no company is safe. Half of the companies that were on the Fortune 500 in 2000 are now gone, replaced by organizations that deliver value faster, better, and cheaper – and the current Fortune 500 faces very much the same fate. Technology plays a central role in the disruptors‘ ability to execute better.
• #4 But it’s no longer just the unicorns that disrupt – increasingly, companies you might not associate with the cutting edge of IT have recognized they need to invest in new technology. ‘Traditional’ companies are using cloud technology and investing in custom application development to stand out from the competition.
• #5 In the real world, there are real consequences if companies are unable to deliver high-quality software quickly or build the wrong thing to begin with:(CLICK) 40% of implementations end up getting reworked because they don’t meet the users’ original requirements.(CLICK) The average cost of one hour downtime of a customer-facing app is calculated at 100.000 dollars per hour – and this does not take into account the damage to reputation, which can be even greater.Fixing such production issues takes on average 200 minutes per incident.(CLICK) Three quarters of development teams have adopted Agile methodologies today, enabling them to develop faster.While this is a great number, it does not help if a development team is Agile but deployment still takes weeks or months.(CLICK) These are just 3 examples but all the data we have today points toward one conclusion – this is about more than just frustration or minor delays. Lack of collaboration between dev and ops can have substantial impact on a company’s bottom line and success.
• #6 I want to spend a few minutes on this slide: Development team have adopted Agile Methodologies delays in deploying the features into production – change management processes is prolonged. Business putting pressure on IT to provide the Features for the business to be agile. Time to market is key to the success of a business A bug caught in production is expensive, downtime of the systems and time it take to identify and fix the bug Companies not equipped to perform performance testing due to challenges of the resources required. Frustration - Teams are not collaborative and create blocks increasing time to deliver value. If you not able to deliver business value in an agile way the business it at risk. How do we solve these very real delivery issues. DevOps……
• #7 What does dev ops mean Job Title Automation Faster and Smaller Releases Development and Operations Collaboration You need to look at all of this together. Dev Ops is not just one or two of these items that are implemented.
• #8 Dev Ops is End to end process from ideas to production ready applications and realising the Business Value and ROI. Bringing the Development life cycle (tracking of work, development and testing) and the IT Operations lifecycle (releasing applications and monitoring the applications over time with the intent to improve the product all the time.) together focusing on quality and value that a business can realise in a shorter cadence.
• #9 How do we do this? We have the tools but to successfully implement DevOps DevOps is not only about tools. It is about people, processes and tools. People – people will need to adopt the agile culture. Process – process like Agile, Scrum should be adopted Tools – tools to make people doing the work using the process to be efficient At MS we have learnt from our own development of the products that we create.
• #10 What is DevOps• Why DevOps – the background, the problem statement, why is it an important discussion• Relationship between Agile and DevOps• Linking Digital Transformation and DevOps• DevOps/Agile at Microsoft• Who to engage at your customers and what to engage on – key things to look out. • Importance of selling DevOps• The MS DevOps solution
• #12 Our DevOps journey began with the definition of seven DevOps habits that we have refined over time. DevOps habits are mindset changes that everybody in our organization has to actively embrace and live every day. They are well defined – for example, Flow of Customer Value refers to an organization’s ability to move software from initial idea through creation and validation into the hands of customers and users, without impediments or rework loops. But habits are – by nature - very broad and it can seem like a daunting task to change an entire organization all at once. This is where DevOps practices come in – these are well defined, actionable best practices and workflows that a team can easily take up and implement very quickly. We prescribe no particular sequence of adoption – instead, teams should focus on where they feel they are weakest and work from there. It can be very different from organization to organization – this is a guide, not a roadmap.
• #13 Habits are like mind-set changes that you will have to adopt as an organisation. These are the guiding principals for Dev Ops process to be implemented. What are the DEVOps habits and practises? The habits are the circles on the slide. Practices are guidance to help you to get to a goal of DEV Ops. If you do all of the practices then you will be doing DEVOps (all 7 Habits) FLOW OF CUSTOMER VALUE Flow refers to an organization’s ability to move software swiftly from initial idea through creation and validation into a production release, without impedimentsor rework loops. Reduced rework allows teams to focus on delivering more net-new value. Shorter cycle times support increased responsiveness, in turn fostering stakeholder satisfaction and trust. TEAM AUTONOMY and ENTERPRISE ALIGNMENT The goal for modern application delivery is responsiveness, which relies on flexible scheduling, limiting long-term commitments in favor of iterative experiments, and close team collaboration to facilitate real-time communication and eliminate wasteful handoffs. High performers have multidisciplinary feature crews who pull from a common product backlog, minimize work in process, and deliver work ready to deploy live at the end of each sprint. BACKLOG GROOMEDWITH LEARNING The Backlog is the stack of work to be done. Different organizations plan, define and manage requirements and projects differently. This can include how you engage with stakeholders and how you request, capture, and track work. It can also include how well you align, agree, and make decisions. High performers treat the backlog as a set of hypotheses, which are turned into experiments, and for which they need to collect data that supports or diminishes the hypothesis. Based on that evidence they can determine the next move in the backlog and persevere or pivot. EVIDENCE GATHERED IN PRODUCTION Good decisions are informed by data. High performers instrument everything, not just for health, availability, performance, and other qualities of service, but to understand usage and to collect evidence relative to the backlog hypotheses. For example, they will experiment with changes to user experience and measure the impact on conversion rates in the funnel. They will contrast usage data among cohorts, such as weekday and weekend users, to hypothesize ways of improving theexperience for each. MANAGING TECHNICAL DEBT Technical debt are problems in a development effort that make forward progress on customer value inefficient. Technical debt saps productivity and makes code hard to understand, fragile, time-consuming to change, difficult to validate and creates unplanned work that blocks progress. The Technical Debt category considers behaviors for strategically managing the impact of short-term and long-term technical decisions. PRODUCTION-FIRST MINDSET Production lies at the heart of any software delivery organization, and the best ones recognize that the real production should be top priority for every team member in every role, not just IT operations. Intermediate artifacts like documents and disconnected pre-prod environments are not enough. High performers always track the live site status, remediate any live site issues at root cause, and proactively identify any outliers in performance to see why they are experiencing slowdowns. INFRASTRUCTURE AS A FLEXIBLE RESOURCE The best performers use the flexible infrastructure of the public cloud and continually improve their architecture to refactor into more independent, discrete services. Using the cloud provides scale on demand and makes it easy to stand up services for continuous feedback from constant usage.
• #14 The collection of tools and products that we have we call this the Microsoft DevOps solution. The corner stone for this is TFS or VSTS. If you using VS it makes the implementation of DevOps really integrated and easy however you are able to hook in any component other than MS into TFS or VSTS. So Ms provide you the platform for a complete end to end DEV Ops solution.
• #15 You can achieve DevOps by using TFS or Visual Studio Team Services as your DEV Ops Platform to implement your DEVOps process. Microsoft does not limit you and enables DevOps across all platforms and languages. It also is flexible to allow for your Dev Ops platform to be On Prem in the Cloud and even a Hybrid implementation.
• #16 Whilst TFs is you on prem implementation for DevOps, Visual Studio Team Services provides you with DEV Ops capability in the cloud. The platform allows you to achieve the DevOps process integrating with all your current investments to provide an end to end DevOps option. Features in Visual Studio Online get released once every three weeks and around once per quarter those features get rolled up and put into an update which goes into the on-premises Team Foundation Server. So no matter whether you prefer to do your business in the cloud, hybrid, or on-premises, Microsoft has you covered. Features Not Supported on VSTS Project Server Integration SharePoint Integration
• #17 Now lets highlight some of the tools available to you in each stage of the DevOps process that MS provide to you Get some guidance from the team on what the do in these areas: Development – code reviews unit testing – Intellitest Live Unit test Dependicy Diagrams Xamarin Testing – Management of testing work Functional testing User Acceptance Testing Visual Studio Mobile Centre Architecture Validations – Performance Testing Agile Planning Release Management Environment for testing Production Monitoring Development Visual Studio – Rich IDE offering tools for the developer to ensure quality deliverables. Xamarin allows you to develop once and deploy to many platforms with the native experience and performance. Testing Test Case Manager – Tools that can be used by the team to document test scripts and manage testing. Mobile Test Hub (Xamarin Test Cloud) – Allows you to test you application on about 2000 different devices Deployment Build Scripts and Release Manager that allow for Continues Integration and Continues Deployment with gated check ins and workflow allowing for approvals before deployment into the various environments. HockeyApp allows you to deploy the application and roles out releases. Monitor and Learn Application Insights that give you details on how the application is performing and usage patterns of the application that can be used to make decisions for the next sprint. HockeyApp – allows you to monitor the application and report on errors and user patters Agile Boards and Dashboards Use the agile tools and work items to help plan, track and mange the project. Dashboards that make relevant information available to the team So MS provide you with the end to end solutions providing great tools for all members of the team from developers, testers, project managers as well as business stake holders that will allow a great DevOps solution.
• #18 If an organization adopts even just one of the DevOps practices listed on the previous slide, it will have a positive impact on their ability to deliver better software, faster. If you looking to adopt DevOps, we recommend that you start with a few well-established practices – these are widely recognized as the basis of many successful DevOps transformations.(CLICK) But in order to be successful with DevOps practices, powerful DevOps tools are required. You can get different tools for all the tasks and steps of the end-to-end DevOps pipeline and wire them together as needed.(CLICK) However, with Visual Studio Enterprise, .NET developers get the tools and services for all phases of the end-to-end lifecycle out of the box. And even if you do not want to use just Microsoft tools and technologies, you can easily integrate any existing tool with our DevOps solution.
• #19 Now we at Ms know that DevOps is not new and that there are business that have already made investments in various Open Source products for stages of the DevOps process. We understand this and we are saying to implement your Dev Ops solution these investments are not wasted and TFS and VSTS allows you to hook these tools into TFS and makes implementing the end to end DevOps process easier TFS has service hook to all the major tools so that you could easily hook these into tfs.
• #20 VSTS is our cloud offering to TFS and you can easily implement you DevOps solution using this, it provide you a quick alternate to the on-premis option. But MS provide more if you want to use the cloud to create Dev and Testing environments. Development and Test environments using Microsoft Azure empowers development and test teams to be more agile, deliver faster, and deliver higher quality by taking advantage of cloud infrastructure and services that integrate seamlessly with the tools you have from a trusted partner.​ Challenges currently faced. Compromised agility Limited hardware budget Resource contention with VMs Realistic scale tests often challenging Procurement delays Value Provision resources in minutes, instead of days or weeks Test at production scale, to catch and fix problems before you release Improve productivity with predefined images & application services
• #21 Preview Version 1.7 (2017-04-20)
• #22 The shift to a DevOps solution is easy with MS and TFS, why remain in the old world when the new world looks so much better delivering higher value to you and your business.
• #25 Some of the enhancements one can find in TFS 2015 and VS 2015.
• #26 Ms allows external players to build services for TFS using the APIs and making these available for use. This is a great way to extend tfs to make it work for you. An example of this would a time tracking tool.
• #28 Adopt agile techniques to become more effective. Agile planning tools (like capacity planning, task boards, Kanban boards, and backlog management) offer your teams the flexibility to adopt incremental development techniques and agile methodologies (like Scrum) at their own pace. Use the same tools to enhance your current methodology more gradually.
• #29 <1> Adding and editing directly from the board First, notice that all cards have a slightly updated look—cards are now a bit wider, and have a solid white background (instead of a colored background). Why the changes? We’re laying the groundwork for more customization options on the cards, including adornments, additional fields, and tags. Those customizations options aren’t ready in this deployment, but they’re coming soon, so stay tuned. Next, we’ve updated all boards to support adding new cards and inline editing. The Kanban board now has a New item button at the top of the first column that adds a new card. Once added, all data on the card can be edited directly from the card itself. <2> Kanban swim lanes Today’s update brings the ability to create swim lanes on your Kanban boards. A swim lane is a horizontal lane used to categorize work; the most common use is the creation of an “expedite lane” for emergency work that can skip queues and preempt other work. Our boards support creating as many lanes as the team needs. Just collapse them out of the way when not in use. To add a swim lane, click the gear in the top right hand corner of your board. Enjoy! <3> Reordering on the Kanban board Let’s switch gears and talk about a few more updates to our Kanban boards. First, we’ve turned on reordering items on the board. You can now move items up and down in priority within each column on your board. Any changes made on the board are also reflected directly on the backlog. In fact, with this change many of you may choose to use the board over the backlog, as the board now supports adding, inline editing, and reordering. <4> Split columns on the Kanban board Next, we’ve added a new feature to our Kanban board called “Split Columns”. Kanban teams use a pull model to move work through the board. To do this effectively, each column on your board is split into two subcolumns—Doing and Done. Moving a card into the Done column provides a clear signal that work is ready to progress, and that the card can be pulled by the person/team who owns that next stage. Click the Customize Columns link on the toolbar to split any of the columns on your board. <5> Kanban definition of done As work moves through your board, it’s critical that you and your team are on the same page about what “done” means for each column. Today’s deployment brings a new capability that lets you specify a definition of done for each column on your board. Columns with a definition now include a small icon in the header that communicates the agreed-upon definition.
• #30 <1> Adding and editing directly from the board First, notice that all cards have a slightly updated look—cards are now a bit wider, and have a solid white background (instead of a colored background). Why the changes? We’re laying the groundwork for more customization options on the cards, including adornments, additional fields, and tags. Those customizations options aren’t ready in this deployment, but they’re coming soon, so stay tuned. Next, we’ve updated all boards to support adding new cards and inline editing. The Kanban board now has a New item button at the top of the first column that adds a new card. Once added, all data on the card can be edited directly from the card itself. <2> Kanban swim lanes Today’s update brings the ability to create swim lanes on your Kanban boards. A swim lane is a horizontal lane used to categorize work; the most common use is the creation of an “expedite lane” for emergency work that can skip queues and preempt other work. Our boards support creating as many lanes as the team needs. Just collapse them out of the way when not in use. To add a swim lane, click the gear in the top right hand corner of your board. Enjoy! <3> Reordering on the Kanban board Let’s switch gears and talk about a few more updates to our Kanban boards. First, we’ve turned on reordering items on the board. You can now move items up and down in priority within each column on your board. Any changes made on the board are also reflected directly on the backlog. In fact, with this change many of you may choose to use the board over the backlog, as the board now supports adding, inline editing, and reordering. <4> Split columns on the Kanban board Next, we’ve added a new feature to our Kanban board called “Split Columns”. Kanban teams use a pull model to move work through the board. To do this effectively, each column on your board is split into two subcolumns—Doing and Done. Moving a card into the Done column provides a clear signal that work is ready to progress, and that the card can be pulled by the person/team who owns that next stage. Click the Customize Columns link on the toolbar to split any of the columns on your board. <5> Kanban definition of done As work moves through your board, it’s critical that you and your team are on the same page about what “done” means for each column. Today’s deployment brings a new capability that lets you specify a definition of done for each column on your board. Columns with a definition now include a small icon in the header that communicates the agreed-upon definition.
• #31 Visualize full requirements traceability. Gain full traceability and visibility into the progress and quality of each requirement, tracking back work items and test cases to business goals.   Work Item Charting allows you to use a browser based interface to create visual chart representations of the data returned from a TFS query. This allows us to build up a view of visual representations of work item data that help us understand the state of our projects better in a simple to use way.
• #32 Capture requirements efficiently and trace them through the development cycle. Business teams can easily capture lightweight requirements from end-user stakeholders using the Storyboard tool. It also helps to foster new ideas, get feedback, and directly integrate with the development process.
• #33 Demo
• #40 Demo
• #43 Demo
• #44 Demo
• #46 Demo
• #47 Is my application crashing? What exactly happened? Is my application fast enough? Is my server able to handle the load? How responsive are my dependencies? Is my application UP or DOWN? What is the root cause? How many people are impacted?
• #49 Demo