Ana is an DevOps and Agile consultant and Microsoft Visual Studio Team Services/Team Foundation Server specialist at Ekobit, Croatia. Since 2005, she has been implementing ALM/DevOps environments for development teams of different sizes. This includes the full set of services related to planning, installation, integration and customization, as well as training and coaching. Besides that, her main points of interest include agile and lean software development practices and tools. Ana frequently speaks about her extensive experiences at various local and international industry conferences and regularly delivers customer tailored training workshops. She has been awarded by Microsoft as a Visual Studio ALM MVP in the award category Visual Studio and Development Technologies. Additionally, she holds certificates for MCSD: ALM, PSM I, PSM II, CSM, MCTS:TFS and MCSD.NET.
DevOps Transformation in Microsoft – Case Study
- Stopnja 300
24. maj 2018 10:15
Microsoft has embarked on its DevOps journey more than 6 years ago, when it started modeling the new set of engineering tools and practices called One Engineering System (1ES), fully based on their own platforms - Visual Studio Team Services (VSTS) and Azure. Since then, multiple product development teams have gone through a massive transition in terms of how they organize their work and deal with infrastructure, tools and processes. This session tells the story of the transformation of 50+ teams with more than 800 people that develop Visual Studio Team Services (VSTS) and Team Foundation Server (TFS). These teams have been previously producing the monolithic 3-tier on premises TFS environment every couple of years. Nowadays, they are living by the rules of the cloud cadence and delivering daily updates to VSTS, their global scale, always available, cloud service made up of dozens of micro-services. At the same time, they deliver the same capabilities on premises every few months. Join us to learn how Microsoft's teams drastically changed the way how they develop, test, deploy and monitor their products. We will explain how they manage large agile product development, how they improved their development process by switching to GIT, how they changed their approach to testing and quality control and managed to take full control over their technical debt.