LinkedIn provides a technical onboarding program to teach new hires about how LinkedIn builds and operates applications and services. The summary covers the key learning outcomes around LinkedIn's architecture, development process, systems that power the platform, and core values. It also introduces some of the leadership team and major organizational groups within R&D like Product and Engineering.
This document summarizes a presentation on how to build high-performing IT teams. It begins by making the case that high-performing teams are both more agile and reliable based on data. It then discusses identifying the desired organizational state with high trust cultures, aligned goals, and other attributes. Next, it covers aligning incentives across business, development, operations, and quality teams to focus on customer value. The document also reviews common team structures and implementing technical practices like infrastructure as code, version control, peer review, and continuous delivery to measure results.
Tailoring your SDLC for DevOps, Agile and moreJeff Schneider
MomentumSI encourages tailoring an SDLC based on industry best practices and philosophies. The document discusses incorporating practices from Scrum, Test Driven Development, Feature Driven Development, Lean Software Development, Agile Manifesto, Extreme Programming, DevOps, Enterprise SOA Manifesto, Harmony SOA Tenets, OpenUP, Enterprise Unified Process, BABOK, ITIL, PMBOK, and COBIT. The tailored SDLC should provide traceability back to these influences while serving the specific needs of the organization.
Demystifying DevOps for Ops - Including Findings from the 2015 State of DevOp...Puppet
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code.
It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
DevOps 101 provides an overview of DevOps concepts and adoption in the enterprise. It discusses why DevOps is important to accelerate software delivery, improve quality, and increase collaboration between development and operations. The document outlines key aspects of adopting DevOps, including focusing on people, processes, and technologies. It also provides an overview of IBM's DevOps solution to help organizations continuously deliver innovation through improved software development and delivery.
AUG NYC - May 24 talks.
1. Atlassian Test Case Management Options and Integrations - Blaine Pryce & Bob Ho, Column Technologies
Today’s Software Economy requires a high degree of automation to make any DevOps initiative successful. The sheer velocity of DevOps is driving the need for a more integrated approach to the QA and testing processes. Blaine & Bob will explore the Atlassian Test Case Management options and an integrated technology approach that can streamline the QA and testing processes for your organization. The featured integration use case will highlight integrating Test Automation/ Test Case Management/Test Data Management and Bug Tracking
2. How to Customize, Automate and Expand the Power of JIRA - Ethan Foulkes, cPrime
Everyone knows Jira is great for development and we are seeing it used more and more for building non-development related workflows. Come and learn how easy it is to go beyond the out of box capabilities and hear Ethan speak about how to bend Jira to support any business process.
This document discusses the software development lifecycle (SDLC) and DevOps. It provides an overview of the SDLC phases and Agile Scrum framework. It describes the need for DevOps by explaining problems that can occur when development and operations teams are separated. It proposes DevOps as a solution to automate software delivery and infrastructure changes through a cross-functional team and toolchain. The document outlines various tools used in a DevOps toolchain for version control, IDEs, project management, continuous integration, testing, security, collaboration and more. It concludes by discussing future plans to implement OpenStack, Docker and gain experience with Amazon Web Services.
The document describes Aricent's implementation of a DevOps methodology to automate the delivery pipeline for their Aricloud product. It discusses the objectives of adopting DevOps, the steps taken to implement the DevOps pipeline using various Jenkins plugins, and the technical and cultural challenges overcome during implementation. Key benefits realized included reduced time between code check-ins and production deployment, improved collaboration between teams, and increased customer satisfaction through more rapid releases.
This document summarizes a presentation on how to build high-performing IT teams. It begins by making the case that high-performing teams are both more agile and reliable based on data. It then discusses identifying the desired organizational state with high trust cultures, aligned goals, and other attributes. Next, it covers aligning incentives across business, development, operations, and quality teams to focus on customer value. The document also reviews common team structures and implementing technical practices like infrastructure as code, version control, peer review, and continuous delivery to measure results.
Tailoring your SDLC for DevOps, Agile and moreJeff Schneider
MomentumSI encourages tailoring an SDLC based on industry best practices and philosophies. The document discusses incorporating practices from Scrum, Test Driven Development, Feature Driven Development, Lean Software Development, Agile Manifesto, Extreme Programming, DevOps, Enterprise SOA Manifesto, Harmony SOA Tenets, OpenUP, Enterprise Unified Process, BABOK, ITIL, PMBOK, and COBIT. The tailored SDLC should provide traceability back to these influences while serving the specific needs of the organization.
Demystifying DevOps for Ops - Including Findings from the 2015 State of DevOp...Puppet
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code.
It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
DevOps 101 provides an overview of DevOps concepts and adoption in the enterprise. It discusses why DevOps is important to accelerate software delivery, improve quality, and increase collaboration between development and operations. The document outlines key aspects of adopting DevOps, including focusing on people, processes, and technologies. It also provides an overview of IBM's DevOps solution to help organizations continuously deliver innovation through improved software development and delivery.
AUG NYC - May 24 talks.
1. Atlassian Test Case Management Options and Integrations - Blaine Pryce & Bob Ho, Column Technologies
Today’s Software Economy requires a high degree of automation to make any DevOps initiative successful. The sheer velocity of DevOps is driving the need for a more integrated approach to the QA and testing processes. Blaine & Bob will explore the Atlassian Test Case Management options and an integrated technology approach that can streamline the QA and testing processes for your organization. The featured integration use case will highlight integrating Test Automation/ Test Case Management/Test Data Management and Bug Tracking
2. How to Customize, Automate and Expand the Power of JIRA - Ethan Foulkes, cPrime
Everyone knows Jira is great for development and we are seeing it used more and more for building non-development related workflows. Come and learn how easy it is to go beyond the out of box capabilities and hear Ethan speak about how to bend Jira to support any business process.
This document discusses the software development lifecycle (SDLC) and DevOps. It provides an overview of the SDLC phases and Agile Scrum framework. It describes the need for DevOps by explaining problems that can occur when development and operations teams are separated. It proposes DevOps as a solution to automate software delivery and infrastructure changes through a cross-functional team and toolchain. The document outlines various tools used in a DevOps toolchain for version control, IDEs, project management, continuous integration, testing, security, collaboration and more. It concludes by discussing future plans to implement OpenStack, Docker and gain experience with Amazon Web Services.
The document describes Aricent's implementation of a DevOps methodology to automate the delivery pipeline for their Aricloud product. It discusses the objectives of adopting DevOps, the steps taken to implement the DevOps pipeline using various Jenkins plugins, and the technical and cultural challenges overcome during implementation. Key benefits realized included reduced time between code check-ins and production deployment, improved collaboration between teams, and increased customer satisfaction through more rapid releases.
Developing a Testing Strategy for DevOps SuccessDevOps.com
To achieve rapid time-to-market, businesses have embraced DevOps, which places a premium on speed and efficiency. But speed is not the only measure of DevOps success. To release better software faster, enterprises must optimize testing strategy and embed a culture of quality within their DevOps processes.
In this webinar, you will learn:
How to transform QA from a bottleneck to a speed enabler
How to integrate quality and increase visibility throughout the SDLC
How to help your VPs and Directors gauge the success of their current quality initiatives
This document summarizes a presentation about adopting DevOps practices to improve software delivery. It discusses how delivering software is challenging and costly, and that DevOps can help by improving collaboration between development and operations teams. A case study is presented from HM Health Solutions, who saw a 75% reduction in time spent fixing defects in testing and an 82% reduction in production after adopting DevOps practices like continuous integration, automated testing, and deployment. Tips are provided on getting started with an enterprise DevOps rollout.
DevOps evolution architecting the modern software factory - cloud expo east 2017Anand Akela
This document discusses the evolution of DevOps and how companies are adopting DevOps practices like continuous delivery to accelerate software delivery and improve customer experience. It outlines how traditional development methods can no longer keep up with rising customer expectations for faster and higher quality software. Companies are turning to DevOps and agile methodologies like continuous development, testing and delivery to reduce cycle times, improve quality and collaboration between development and operations teams. The document provides examples of how companies across industries like PayPal, L'Oreal, Sprint and Charter have benefited from DevOps adoption including increased velocity, reduced costs and better customer satisfaction.
This document provides information about a presentation titled "Integrating Automated Testing into DevOps" given by Jeff Payne of Coveros, Inc. It includes biographical information about Jeff Payne, an agenda for the presentation, and content that will be covered, including definitions of DevOps, common DevOps terminology, automated testing for continuous integration and continuous delivery, environments for testing, common tools used, and demos of automated testing.
This document provides an overview of various DevOps tools across different categories like source code management, continuous integration, infrastructure automation, container management, and more. It discusses the purpose and use of tools in each category. It also notes that the DevOps tools market is large and growing, reaching an estimated $8.8 billion by 2023, and that new tools will continue to emerge as DevOps practices mature.
Continuous Quality: What DevOps Means for QAJeff Sussna
The document discusses how DevOps is changing the role of quality assurance (QA). It argues that with software increasingly delivered as a service, the focus of QA must shift from testing software to ensuring quality across four dimensions: functionality, operability, deliverability, and coherency. The new QA role involves representing the customer perspective, facilitating requirements understanding, and acting as a "boundary-spanning mirror" to help development, operations, and other teams understand each other and customers. Continuous delivery requires QA to test outside-in across the full customer experience and help build quality into the entire service delivery process.
Mitchell International has been providing property and casualty claims services for 70 years. They are moving to continuous integration and delivery (CI/CD) to rapidly build and deliver quality software. Previously they had a slow "big build" system and manual testing. Now developers maintain componentized builds and immediately get feedback on check-ins through automated testing. It has been a journey over 7 years from centralized systems to empowering developers. They use tools like Jenkins and Artifactory to run over 1400 jobs daily across many platforms and deliver capabilities as a service.
Continuous Delivery offers a proven solution for streamlining software design that enables rapid, reliable, and repeated delivery code enhancements at low risk and with minimal overhead. Using a framework that automates processes from code design to deployment, software can be developed to high standards while reducing time-to-market. Continuous Delivery not only establishes consistent delivery of higher quality software with greater reliability, it does so at a lower overall cost.
This document discusses DevOps for mobile apps. It begins with an introduction to DevOps, including key concepts like continuous integration, continuous delivery, and infrastructure as code. It then covers challenges of DevOps for mobile, such as fragmented platforms and coordination across backend systems. Best practices are presented, such as end-to-end traceability, continuous integration, and automated builds. The document concludes with discussions of implementing continuous integration and delivery, service virtualization for testing, and mobile UI testing.
The document discusses shifting the focus of internationalization (i18n) efforts earlier in the software development process. Traditionally, i18n was seen as the responsibility of localization teams and tested later in the cycle. However, with faster release cycles and the need to reach global customers quicker, i18n needs to be integrated as a core part of the initial development process. Static analysis tools can help developers test for i18n issues proactively during development rather than waiting until localization. Catching i18n bugs earlier saves significant time and costs compared to fixing them late in the cycle during localization. The presentation advocates making world-ready software a priority from the start through processes, guidelines and tools that verify i18n compliance
Enabling DevOps in the cloud - Federal Cloud Innovation CenterSanjeev Sharma
This document discusses enabling DevOps for cloud deployments. It introduces DevOps as a lean approach to reduce waste and improve efficiency. Deploying applications to the cloud with DevOps allows for standardization, lower costs, and faster delivery. IBM's BlueMix platform and DevOps services provide tools for continuous delivery pipelines to deploy to cloud environments. Future directions involve supporting OpenStack cloud patterns to drive consistency with proven best practices.
1) The document discusses enterprise DevOps and provides an overview of what DevOps is, why it is important now, and how to implement it. It presents case studies of companies that have implemented DevOps and realized benefits like increased speed, quality, and efficiency.
2) The document outlines DevOps service offerings from HPE that can help increase automation, reduce latency, and improve visibility across various DevOps domains from build and test to deployment and operations.
3) Case studies show benefits companies achieved including reduced cycle times, deployment times, and costs through DevOps implementations with HPE's help.
Slides from this webcast: bit.ly/mTUTq4
Discussion of what DevOps is, why we need it, what sorts of shared tooling helps it, and how it fits in to an enterprise rollout.
This document provides an overview of a software factory's methodology, environments, and tools. It describes the factory's processes for requirements management, development, testing, quality control, and release management. The factory supports Java/Java EE, PHP, Android, iOS, and PhoneGap environments. It utilizes tools like Eclipse, Maven, Artifactory, Git, GitHub, Jenkins, Sonar, Selenium, Testlink, Jira, PHP Cake, PHP Unit, Ant, and Xcode across the development lifecycle.
DevOps CD and Multispeed IT in regulated industries (FUG Presentation)Serena Software
This document discusses DevOps, continuous delivery, and multi-speed IT in regulated environments. It addresses how organizations can drive competitive advantage through faster delivery while still maintaining stability, security, and compliance. DevOps aims to align development and operations goals, continuous delivery ensures software is always production-ready, and multi-speed IT understands different approaches and speeds for different applications and contexts. The document outlines challenges in regulated industries and provides recommendations around people, process, and technology to support DevOps adoption.
DevOps Transformation - technical and organizational goalsAgron Fazliu
The document discusses the technical aspects of a DevOps transformation. It states that technical aspects should include always-ready, automated, uniform, and independent releases on all virtual environments using the latest software inside resilient containers with service discovery and multi-stage history-enabled feedback systems. It then provides explanations for each of these elements across 14 slides to fully define what achieving this technical standard would entail for an organization's processes and infrastructure.
Driving Systems Stability & Delivery Agility through DevOps [Decoding DevOps ...InfoSeption
The document discusses how VMware IT drives systems stability and delivery agility through DevOps practices. It summarizes how VMware IT automated instance provisioning to reduce provisioning time from 4-6 weeks to under 22 hours. It also discusses how VMware IT uses a cloud operations management platform for instance monitoring and management to improve operational efficiency. Finally, it outlines how VMware IT leverages a continuous delivery platform and service virtualization to improve application delivery agility.
The 7 Principles of DevOps and Cloud ApplicationsSolarWinds
The document discusses the 7 principles of DevOps and cloud applications. The principles are: 1) application and end-user focus, 2) collaboration, 3) performance orientation, 4) development speed, 5) service orientation, 6) automation, and 7) monitor everything. DevOps aims to improve the speed and quality of application development through breaking down silos between development and operations teams and prioritizing collaboration, automation, and monitoring across the entire application lifecycle.
Our DevOps Journey
Transforming 6 Month Waterfalls to 1 Hour Code Deploys
https://info.dynatrace.com/17q3_wc_from_agile_to_cloudy_devops_na_registration.html
In the 2nd part of our webinar series, Anita Engleder, DevOps Lead at Dynatrace reviews and dissects lessons learned during the transformational journey moving Dynatrace from an on-prem culture to one that is cloud native. She will lend her perspective as a key member of the team that executed on the original vision: to “implement a new cloud native offering and deploy a new feature release every 2 weeks. Additionally, be able to support a 1-hour lead time from Code Change to Production”.
On November 17th at 1pm/10am PT Anita will present the challenges she and her team faced transforming 6 Months Waterfall to 1 Hour Code Deploys.
In this webinar Anita will discuss:
How to enable a complete cultural shift across multiple teams, in terms of thought process AND execution
What the specific role of her DevOps team is and how it played into the transformation
The role of Feature teams and why continuous feedback is critical for them
How to successfully influence key stakeholders for complete alignment
Today Anita’s team runs 170 production changes every day, running across several AWS Data Centers as well as On-Premise – something that would have been thought impossible only a few years prior.
DevOps Patterns Distilled: Implementing The Needed Practices In Practical StepsCA Technologies
Learn from Gene Kim, one of the “DevOps Cookbook” authors, how to help accelerate DevOps adoption, increase the success of DevOps initiatives and lower the activation energy required for DevOps transformations to start and finish.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
Ahmad Owais is a senior technical specialist with over 11 years of experience in Java/J2EE development, system design, architecture, and consulting. He has skills in technologies such as Java, XML, JSP, Servlets, Struts, Spring, Hibernate, Web Services, JMS, Oracle, MySQL, Flex, HTML, JavaScript, and more. He has contributed to projects involving middleware technologies, ecommerce portals, configuration and ordering systems, and more.
Breaking the 2 Pizza Paradox with your Platform as an ApplicationMark Rendell
In my experience many large enterprises would love the adoption of DevOps to be as simple as bringing Development closer to Operations. In practice they need to consider many development teams, multiple suppliers, multiple service providers, not to mention multiple business divisions. I describe my experiences of implementing Continuous Delivery in large enterprises with heterogeneous technology stacks and share my belief that Platform Applications will be the saviour of enterprise DevOps.
Developing a Testing Strategy for DevOps SuccessDevOps.com
To achieve rapid time-to-market, businesses have embraced DevOps, which places a premium on speed and efficiency. But speed is not the only measure of DevOps success. To release better software faster, enterprises must optimize testing strategy and embed a culture of quality within their DevOps processes.
In this webinar, you will learn:
How to transform QA from a bottleneck to a speed enabler
How to integrate quality and increase visibility throughout the SDLC
How to help your VPs and Directors gauge the success of their current quality initiatives
This document summarizes a presentation about adopting DevOps practices to improve software delivery. It discusses how delivering software is challenging and costly, and that DevOps can help by improving collaboration between development and operations teams. A case study is presented from HM Health Solutions, who saw a 75% reduction in time spent fixing defects in testing and an 82% reduction in production after adopting DevOps practices like continuous integration, automated testing, and deployment. Tips are provided on getting started with an enterprise DevOps rollout.
DevOps evolution architecting the modern software factory - cloud expo east 2017Anand Akela
This document discusses the evolution of DevOps and how companies are adopting DevOps practices like continuous delivery to accelerate software delivery and improve customer experience. It outlines how traditional development methods can no longer keep up with rising customer expectations for faster and higher quality software. Companies are turning to DevOps and agile methodologies like continuous development, testing and delivery to reduce cycle times, improve quality and collaboration between development and operations teams. The document provides examples of how companies across industries like PayPal, L'Oreal, Sprint and Charter have benefited from DevOps adoption including increased velocity, reduced costs and better customer satisfaction.
This document provides information about a presentation titled "Integrating Automated Testing into DevOps" given by Jeff Payne of Coveros, Inc. It includes biographical information about Jeff Payne, an agenda for the presentation, and content that will be covered, including definitions of DevOps, common DevOps terminology, automated testing for continuous integration and continuous delivery, environments for testing, common tools used, and demos of automated testing.
This document provides an overview of various DevOps tools across different categories like source code management, continuous integration, infrastructure automation, container management, and more. It discusses the purpose and use of tools in each category. It also notes that the DevOps tools market is large and growing, reaching an estimated $8.8 billion by 2023, and that new tools will continue to emerge as DevOps practices mature.
Continuous Quality: What DevOps Means for QAJeff Sussna
The document discusses how DevOps is changing the role of quality assurance (QA). It argues that with software increasingly delivered as a service, the focus of QA must shift from testing software to ensuring quality across four dimensions: functionality, operability, deliverability, and coherency. The new QA role involves representing the customer perspective, facilitating requirements understanding, and acting as a "boundary-spanning mirror" to help development, operations, and other teams understand each other and customers. Continuous delivery requires QA to test outside-in across the full customer experience and help build quality into the entire service delivery process.
Mitchell International has been providing property and casualty claims services for 70 years. They are moving to continuous integration and delivery (CI/CD) to rapidly build and deliver quality software. Previously they had a slow "big build" system and manual testing. Now developers maintain componentized builds and immediately get feedback on check-ins through automated testing. It has been a journey over 7 years from centralized systems to empowering developers. They use tools like Jenkins and Artifactory to run over 1400 jobs daily across many platforms and deliver capabilities as a service.
Continuous Delivery offers a proven solution for streamlining software design that enables rapid, reliable, and repeated delivery code enhancements at low risk and with minimal overhead. Using a framework that automates processes from code design to deployment, software can be developed to high standards while reducing time-to-market. Continuous Delivery not only establishes consistent delivery of higher quality software with greater reliability, it does so at a lower overall cost.
This document discusses DevOps for mobile apps. It begins with an introduction to DevOps, including key concepts like continuous integration, continuous delivery, and infrastructure as code. It then covers challenges of DevOps for mobile, such as fragmented platforms and coordination across backend systems. Best practices are presented, such as end-to-end traceability, continuous integration, and automated builds. The document concludes with discussions of implementing continuous integration and delivery, service virtualization for testing, and mobile UI testing.
The document discusses shifting the focus of internationalization (i18n) efforts earlier in the software development process. Traditionally, i18n was seen as the responsibility of localization teams and tested later in the cycle. However, with faster release cycles and the need to reach global customers quicker, i18n needs to be integrated as a core part of the initial development process. Static analysis tools can help developers test for i18n issues proactively during development rather than waiting until localization. Catching i18n bugs earlier saves significant time and costs compared to fixing them late in the cycle during localization. The presentation advocates making world-ready software a priority from the start through processes, guidelines and tools that verify i18n compliance
Enabling DevOps in the cloud - Federal Cloud Innovation CenterSanjeev Sharma
This document discusses enabling DevOps for cloud deployments. It introduces DevOps as a lean approach to reduce waste and improve efficiency. Deploying applications to the cloud with DevOps allows for standardization, lower costs, and faster delivery. IBM's BlueMix platform and DevOps services provide tools for continuous delivery pipelines to deploy to cloud environments. Future directions involve supporting OpenStack cloud patterns to drive consistency with proven best practices.
1) The document discusses enterprise DevOps and provides an overview of what DevOps is, why it is important now, and how to implement it. It presents case studies of companies that have implemented DevOps and realized benefits like increased speed, quality, and efficiency.
2) The document outlines DevOps service offerings from HPE that can help increase automation, reduce latency, and improve visibility across various DevOps domains from build and test to deployment and operations.
3) Case studies show benefits companies achieved including reduced cycle times, deployment times, and costs through DevOps implementations with HPE's help.
Slides from this webcast: bit.ly/mTUTq4
Discussion of what DevOps is, why we need it, what sorts of shared tooling helps it, and how it fits in to an enterprise rollout.
This document provides an overview of a software factory's methodology, environments, and tools. It describes the factory's processes for requirements management, development, testing, quality control, and release management. The factory supports Java/Java EE, PHP, Android, iOS, and PhoneGap environments. It utilizes tools like Eclipse, Maven, Artifactory, Git, GitHub, Jenkins, Sonar, Selenium, Testlink, Jira, PHP Cake, PHP Unit, Ant, and Xcode across the development lifecycle.
DevOps CD and Multispeed IT in regulated industries (FUG Presentation)Serena Software
This document discusses DevOps, continuous delivery, and multi-speed IT in regulated environments. It addresses how organizations can drive competitive advantage through faster delivery while still maintaining stability, security, and compliance. DevOps aims to align development and operations goals, continuous delivery ensures software is always production-ready, and multi-speed IT understands different approaches and speeds for different applications and contexts. The document outlines challenges in regulated industries and provides recommendations around people, process, and technology to support DevOps adoption.
DevOps Transformation - technical and organizational goalsAgron Fazliu
The document discusses the technical aspects of a DevOps transformation. It states that technical aspects should include always-ready, automated, uniform, and independent releases on all virtual environments using the latest software inside resilient containers with service discovery and multi-stage history-enabled feedback systems. It then provides explanations for each of these elements across 14 slides to fully define what achieving this technical standard would entail for an organization's processes and infrastructure.
Driving Systems Stability & Delivery Agility through DevOps [Decoding DevOps ...InfoSeption
The document discusses how VMware IT drives systems stability and delivery agility through DevOps practices. It summarizes how VMware IT automated instance provisioning to reduce provisioning time from 4-6 weeks to under 22 hours. It also discusses how VMware IT uses a cloud operations management platform for instance monitoring and management to improve operational efficiency. Finally, it outlines how VMware IT leverages a continuous delivery platform and service virtualization to improve application delivery agility.
The 7 Principles of DevOps and Cloud ApplicationsSolarWinds
The document discusses the 7 principles of DevOps and cloud applications. The principles are: 1) application and end-user focus, 2) collaboration, 3) performance orientation, 4) development speed, 5) service orientation, 6) automation, and 7) monitor everything. DevOps aims to improve the speed and quality of application development through breaking down silos between development and operations teams and prioritizing collaboration, automation, and monitoring across the entire application lifecycle.
Our DevOps Journey
Transforming 6 Month Waterfalls to 1 Hour Code Deploys
https://info.dynatrace.com/17q3_wc_from_agile_to_cloudy_devops_na_registration.html
In the 2nd part of our webinar series, Anita Engleder, DevOps Lead at Dynatrace reviews and dissects lessons learned during the transformational journey moving Dynatrace from an on-prem culture to one that is cloud native. She will lend her perspective as a key member of the team that executed on the original vision: to “implement a new cloud native offering and deploy a new feature release every 2 weeks. Additionally, be able to support a 1-hour lead time from Code Change to Production”.
On November 17th at 1pm/10am PT Anita will present the challenges she and her team faced transforming 6 Months Waterfall to 1 Hour Code Deploys.
In this webinar Anita will discuss:
How to enable a complete cultural shift across multiple teams, in terms of thought process AND execution
What the specific role of her DevOps team is and how it played into the transformation
The role of Feature teams and why continuous feedback is critical for them
How to successfully influence key stakeholders for complete alignment
Today Anita’s team runs 170 production changes every day, running across several AWS Data Centers as well as On-Premise – something that would have been thought impossible only a few years prior.
DevOps Patterns Distilled: Implementing The Needed Practices In Practical StepsCA Technologies
Learn from Gene Kim, one of the “DevOps Cookbook” authors, how to help accelerate DevOps adoption, increase the success of DevOps initiatives and lower the activation energy required for DevOps transformations to start and finish.
For more information on DevOps solutions from CA Technologies, please visit: http://bit.ly/1wbjjqX
Ahmad Owais is a senior technical specialist with over 11 years of experience in Java/J2EE development, system design, architecture, and consulting. He has skills in technologies such as Java, XML, JSP, Servlets, Struts, Spring, Hibernate, Web Services, JMS, Oracle, MySQL, Flex, HTML, JavaScript, and more. He has contributed to projects involving middleware technologies, ecommerce portals, configuration and ordering systems, and more.
Breaking the 2 Pizza Paradox with your Platform as an ApplicationMark Rendell
In my experience many large enterprises would love the adoption of DevOps to be as simple as bringing Development closer to Operations. In practice they need to consider many development teams, multiple suppliers, multiple service providers, not to mention multiple business divisions. I describe my experiences of implementing Continuous Delivery in large enterprises with heterogeneous technology stacks and share my belief that Platform Applications will be the saviour of enterprise DevOps.
This presentation will introduce a new DevOps reference architecture published by IBM. This technology agnostic reference architecture was developed harvesting solution architectures from dozens of clients who have been successful in adopting DevOps at scale. The presentation will present the capabilities - across practices, tools, platforms and organizational considerations, that are required for large scale DevOps adoption in an enterprise.
Agile & DevOps - It's all about project successAdam Stephensen
The document provides information on DevOps practices and tools from Microsoft. It discusses how DevOps enables continuous delivery of value through integrating people, processes, and tools. Benefits of DevOps include more frequent and stable releases, lower change failure rates, and empowered development teams. The document provides examples of DevOps scenarios and recommends discussing solutions and migration plans with Microsoft.
Rajeev Krishnapillai has over 25 years of experience in IT project management, product development, engineering, and consulting. He has worked for several major companies, managing teams and overseeing successful software development projects. His areas of expertise include product management, program/project management, business development, IT consulting, and relationship management. He has extensive experience developing and supporting various operating systems and applications.
Ankit Rustagi has over 11 years of experience in software development. He currently works as a Senior Advisory Consultant at IBM India Pvt Ltd. Previously he has worked as a Lead Engineer at PureSoftware Ltd, Senior Consultant at Capgemini India Pvt Ltd, and Senior Associate at Simplion Technologies Ltd. He has extensive skills in Salesforce development including Apex, Visualforce, Lightning, and administration. He also has experience with technologies like Java, JavaScript, HTML, and SQL. He holds certifications in Salesforce Platform Developer I, Salesforce Administrator, and SAFe 4 Practitioner.
Continuous Delivery of a Cloud Deployment at a Large Telecommunications ProviderM Kevin McHugh
This document discusses how a large telecommunications provider implemented continuous delivery for a cloud deployment. It defines continuous delivery as automating the process of software delivery through techniques like continuous integration, automated testing, and continuous deployment. It then describes the specific components and tools used in the telecom provider's implementation, including adopting agile methodology, integrating rational team concert, automated testing with a REST API, and using SmartCloud Orchestrator for automated builds and deployment.
Pete Marshall - casmadrid2015 - Continuous Delivery in Legacy EnvironmentsPeter Marshall
This document discusses practices for implementing continuous delivery in legacy software environments. It outlines key characteristics of continuous delivery like keeping software deployable throughout its lifecycle. It then provides examples of how one company transitioned their monolithic legacy application to a continuous delivery model by using techniques like the strangler pattern, refactoring to separate concerns, and restructuring their organization into cross-functional product teams. The document emphasizes establishing technical foundations, learning through the build-deploy-learn cycle, and focusing on delivering value to customers.
2016 Federal User Group Conference - DevOps Product StrategyCollabNet
The document discusses CollabNet's DevOps product strategy and focus on operational intelligence. It provides an overview of Eric Robertson's background leading DevOps product lines. It also outlines CollabNet's focus areas for agile planning, execution, and downstream traceability. The document emphasizes the importance of continuous lifecycle integration from planning to operations with traceability, visibility, automation and feedback loops across the software development lifecycle.
Sarathi T has over 6 years of experience in software development and testing. He has expertise in C#, Java, ASP.NET, SQL, Oracle, and testing tools like QTP. Some of his projects include developing a robot control application, an offline robot programming editor, and analytics reports in QlikView. He is skilled in all phases of the development life cycle from requirements gathering to testing.
Data-Driven DevOps: Mining Machine Data for 'Metrics that Matter' in a DevOps...Splunk
IT organizations are increasingly using machine data - including in DevOps practices - to get away from 'vanity metrics' and instead to generate 'metrics that matter'. These metrics provide visibility into the delivery of new application code and the business value of DevOps, to both IT and business stakeholders.
Machine data provides DevOps teams and others - including QA, secops, CxOs and LOB leaders - with meaningful and actionable metrics. This allows stakeholders to monitor, measure, and continuously improve the velocity and quality of code throughout the software lifecycle, from dev/test to customer-facing outcomes and business impact.
In this session Andi Mann, chief technology advocate at Splunk, will share core methodologies, interesting case studies, key success factors and 'gotcha' moments from real-world experience with mining machine data to produce 'metrics that matter' in a DevOps context.
The document provides a summary of Jesy George's skills and experience. It includes her contact information and 8 years of experience in design, development and testing using languages like Java, J2EE, and frameworks like Spring and Struts. It also lists her professional experience with 4 companies, educational qualifications including a bachelor's degree in computer science, skills, and details of projects involving media streaming, resource management systems, and a project management system.
The document discusses software project failures and the benefits of using an integrated platform like Visual Studio Team System (VSTS) for software development. It notes that on average in 2000-2004, software projects were 45% over budget, 63% over schedule, and only delivered 67% of planned functionality. VSTS provides features like version control, work item tracking, build automation, and reporting that help improve collaboration, accountability, visibility and quality of software projects. It discusses how one company saw a 225% ROI and 6 month payback by deploying VSTS across their development teams.
Covering topics like:
CI CD DevOps Jenkins TFS TeamCity Compile Test Package Delpoy
See Disclaimer in the last slide and/or in file comments, if available.
Luc Nguyen has over 15 years of experience in software quality assurance. He is currently an automation manager at Cisco Systems where he manages testers and automation engineers. Prior to this, he was a business owner, production engineer at Satmetrix, localization quality assurance engineer lead at PayPal, and held other software quality assurance roles. He has extensive experience in test automation, managing teams, and ensuring high quality software.
Innovate Better Through Machine data AnalyticsHal Rottenberg
This talk was presented at IP Expo Manchester in May, 2016. the themes discussed are:
- how does machine data relate to devops?
- how can tracking this data lead to better outcomes?
- what types of data are important to track?
The document introduces the IBM Rational Solution for Agile ALM, which provides integrated capabilities to support agile development needs. It discusses how the solution helps teams adopt agile practices while addressing challenges of increasing complexity, costs pressures and the need for rapid delivery. The solution includes capabilities for agile planning, continuous integration, collaborative source code management and more. It also discusses how the solution helps scale agile practices to larger project teams and extends agile ALM to areas like testing, DevOps and continuous delivery.
Introducing the Rational Solution for Agile ALMMatt Holitza
How do you keep your agile teams focused on the task at hand while still providing management with the latest status? Find out in this presentation from IBM Innovate 2013.
Leadership Ambassador club Adventist modulekakomaeric00
Aims to equip people who aspire to become leaders with good qualities,and with Christian values and morals as per Biblical teachings.The you who aspire to be leaders should first read and understand what the ambassador module for leadership says about leadership and marry that to what the bible says.Christians sh
5 Common Mistakes to Avoid During the Job Application Process.pdfAlliance Jobs
The journey toward landing your dream job can be both exhilarating and nerve-wracking. As you navigate through the intricate web of job applications, interviews, and follow-ups, it’s crucial to steer clear of common pitfalls that could hinder your chances. Let’s delve into some of the most frequent mistakes applicants make during the job application process and explore how you can sidestep them. Plus, we’ll highlight how Alliance Job Search can enhance your local job hunt.
Resumes, Cover Letters, and Applying OnlineBruce Bennett
This webinar showcases resume styles and the elements that go into building your resume. Every job application requires unique skills, and this session will show you how to improve your resume to match the jobs to which you are applying. Additionally, we will discuss cover letters and learn about ideas to include. Every job application requires unique skills so learn ways to give you the best chance of success when applying for a new position. Learn how to take advantage of all the features when uploading a job application to a company’s applicant tracking system.
Job Finding Apps Everything You Need to Know in 2024SnapJob
SnapJob is revolutionizing the way people connect with work opportunities and find talented professionals for their projects. Find your dream job with ease using the best job finding apps. Discover top-rated apps that connect you with employers, provide personalized job recommendations, and streamline the application process. Explore features, ratings, and reviews to find the app that suits your needs and helps you land your next opportunity.
A Guide to a Winning Interview June 2024Bruce Bennett
This webinar is an in-depth review of the interview process. Preparation is a key element to acing an interview. Learn the best approaches from the initial phone screen to the face-to-face meeting with the hiring manager. You will hear great answers to several standard questions, including the dreaded “Tell Me About Yourself”.
3. Learning Outcomes
How we architect apps and services
How we build insanely great products
How code gets from development to production
What systems power LinkedIn and keep them stable
Where to get the information and data you need
4. LinkedIn’s Core Values
Our members come first
Relationships matter
Be open, honest, and constructive
Demand excellence
Take intelligent risks
Act like an owner
go/values
5. The leadership team
Reid Hoffman
Executive Chairman
& Co-Founder
Jeff Weiner
CEO
Nick Besbeas
VP
Marketing
Mike Gamson
SVP
Global Solutions
Jeff Weiner
Interim Leader
Product & UX
Kevin Scott
SVP
Engineering
Steve Sordello
SVP & CFO
Shannon Stubo
VP
Corporate Comm
Pat Wadors
VP
Talent Org
Mike Callahan
General Counsel
& Secretary
12. LinkedIn’s new experience
methodology designed to be simple,
unified, delightful, and actionable.
Product Vision
“Build insanely brilliant
and simple products that
change people's lives”
- Deep Nishar
13. Product Vision
“Build insanely brilliant
and simple products that
change people's lives”
- Deep Nishar
LinkedIn’s experience methodology
is designed to be simple, unified,
delightful, and actionable.
go/katy
18. Increase engagement through
content translation, localization
and geo-customization.
go/i18n
US
94MM
NON-US
186MM
Internationalization and Localization
i18n and L10n
22. Feature Development Flow
ning
ces
d
Specification
received from
Product Manager
/or Tech Lead
4
Test Engineer
begins test
planning and
strategy
5
Developers
(back-end/
front-end)
write code
6
Code
and p
inte
envi
Initiate contact with
SRE, and stay in touch!
Remember to coordinate
ramp plan with SRE
Remember to coordinate
ramp plan with SRE
23. rs
d/
)
e
Code committed
and pushed to
integration
environment
7
Test Engineer
begins manual and
automated testing
8
Sign-off from Service
Owner, then
devise release and
ramp plan
9
Ramp
to al
in p
Remember to coordinate
ramp plan with SRE
Feature Development Flow
24. mitted
d to
on
ent
Test Engineer
begins manual and
automated testing
8
Sign-off from Service
Owner, then
devise release and
ramp plan
9
Ramp until 100%
to all members
in production
10
Remember to coordinate
ramp plan with SRE
Feature Development Flow
25. Product Design
Product
design sign-off
Only User Experience
Design (UED)
leads/managers
Product
sign-off
Executives give
final approval
BAM
office hours
Brand and Marketing
(BAM) team and
Steve Johnson
go/productreview
26. Using the vision from Product, the visuals
from Design and the infrastructure from
Engineering, Web Developers bring the
User Experience to life.
Web Development
go/webdev
27. Everyone can help! Use our products daily
to find bugs and suggest enhancements!
Test Engineers
Test Engineers live by the motto
“proud to ship with high quality”.
!
Features only make it into production if our
Testing Teams are proud to release it.
28. How we work: Agile/Scrum
10-20
days
Daily
Scrum
meeting
IterationIteration backlog
Product backlog
as prioritized by
Product owner
Backlog tasks
expanded
by team
Potentially
shippable product
increment
go/agile
31. Aspirational Architecture
“Provide abstractions that
make it easier to reason about
the LinkedIn architecture.”
- Swee Lim, Distinguished Software Engineer
go/superblock
Front end
Business logic layer
Super BlockData access layer
Infrastructure
Mid Tier
32. Framework and language agnostic
way to handle requests for data from
internal services.
Rest.li
Profile
go/restli
33. Fizzy
Combine UI components from
different applications into a single
page.
!
Server side (i18n) and client-side
(embeds) rendering logic.
go/fizzy
35. QuickDeploy against EI (QEI)
Selectively deploy and run services
during development.
!
Requests for other services handled
by our Early Integration environment.
Profile
go/qei
36. From request to front-end
*PoP may be in a data
center that is not running
the full app stack
Point of Presence*
NetScaler External Load
Balancers (SSL)
L0 Proxy
Apache Traffic Server
L1 Proxy
Apache Traffic Server
HAProxy
Context path resolution
E.g. /api/
Move all traffic to HTTPS
!
Enhance security and protection
!
Redirect logic (mobile devices)
!
Map url to applications
!
Multi-colo routing logic
LinkedIn Data Center
Application Containers
go/multicolo-routing
38. How code gets to production
ReviewBoard
approved
!
Commit/Push
Run unit tests on
CI server
!
(1-5 mins)
PCS
(integration tests)
PCL
Tests the health
of trunk
If unit tests pass, code
committed pushed
!
Artifact built
PRE PCLPCS
39. SRE’s
notified prod deploy
is about to occur
How code gets to production
Publish artifact
(certified good)
Service Owner
certifies build is
ready to go to
production
Automated service
certification.
Sends the status
back to CRT
Ramp plan should already
have been identified
Artifact is pushed to
EI/EI2
EI EI2
40. How code gets to production
Service Owner
certifies build is
ready to go to
production
Automated service
certification.
Sends the status
back to CRT
SRE’s
notified prod deploy
is about to occur
Ramp plan should already
have been identified
Publish artifact
(certified good)
Artifact is pushed to
EI/EI2
EI EI2
Artifact deployed to
production canary
machines.
If canary looks good,
deploy to all
production nodes
LIX experiment used to
control ramp to members
41. LID - LinkedIn Deployment Tool
Deployment
Next generation deployment tool for
fine grained control of distributed
systems at LinkedIn.
Artifactory
go/lid
42. CRT
Check the status of your checkin
from commit to deployment.
go/crt
How do you know where your code is?
44. Trunk Development
Trunk development - no branches
If unit test fails in PCS. Auto-revert.
If failed in PCL, lock trunk and investigate.
Once issue confirmed resolved,
unlock trunk.
“Ship it” from code owners and reviewers.
Pass local unit tests and commit to trunk.
Issue identified through CRT.
Fix committed.
go/mp
PCS
PCL
45. Network and Multiproduct
Network Trunk Multiproducts
Network trunk: original svn repository
!
Multiproduct: Code management
containers for testing, building, QA and
deployment outside of network trunk.
!
Mint: Tool for managing multiproducts.
FlexibleModular Dependency ManagementStandardized
go/mp
46. Code reviews
Small atomic commits.
!
How well are you solving the
problem?
!
Accompanying unit tests and
documentation a must.
go/codereview
Ship it!
48. Why documentation matters
"Instead of imagining that our main task is
to instruct a computer what to do, let us
concentrate rather on explaining to human
beings what we want a computer to do."
- Donald Knuth
52. Ingraphs
Dynamic visualization
for the data collected
by Autometrics and
other sources.
Week-over-week
comparisons
Real-time
browsing
Personal
dashboards
go/ingraphs
53. LiX (LinkedIn Experimentation Platform)
Allows for A/B test framework
to allow new, modified, or
experimental features to be
deployed to a small segment
of the LI user base.
!
Also used to carefully control the
ramp of new features in production.
20%80%
go/lix
54. The NOC
Centralized Team for site
monitoring and status
reporting of GCNs.
!
#noc
Network Operations Center
go/noc
55. Data Centers
ELA4 - Los Angeles LVA1 - Virginia Texas
Planned 2014
go/datacenters
56. Akamai, Limelight and Level 3
Content Delivery Networks (CDNs)
Delivers content to our members
with high availability, performance
and reduced latency.
57. Critical site issue escalation
If you see something
that doesn’t look right,
report it!
go/issuecritical
1-855-832-LINK
site-issue-critical@linkedin.com
go/issuecritical
Non Critical Email: site-issue@linkedin.com
#noc
61. Using data to drive User Centered Design
Product Data Bootcamp
Short course geared toward
new Product Managers on the
basics of using our massive
amounts of data as a PM.
Taught by data scientists and other data
experts once every quarter.
go/productdatabootcamp
62. Data Science
The Data Science Team delivers valuable data
to help us understand the
member and their site usage.
A/B
testing
Exposing
demographic trends
Product analytics and
data and business insights
63. XLNT
XLNT is an end-to-end A/B testing
solution, providing data for decisions
on product changes.
go/XLNT
64. Informed
go/informed
A stream of micro-updates about
deployments in production and
staging.
Web UI, IRC bot, CLI, REST API for reading and writing updates
66. Tech Life at LinkedIn
Hackdays
Weekly Tech Talks
Horizontal Initiatives
Incubator Program
Functional Leadership Groups
Knowledge Sharing
go/values
Hack, Collaborate, Share and Learn
71. Data storage and distribution
Data Systems
Espresso
go/espresso
Also known as Pegasus, Rest.li is a REST
+JSON framework for building robust, scalable
service architectures using dynamic discovery
and simple asynchronous APIs.
Voldemort
go/voldemort
Voldemort is an open source distributed key-
value storage system developed at LinkedIn.
Databus
go/databus
Source-agnostic distributed change data
capture system, which is an integral part of
LinkedIn's data processing pipeline.
!
Also used for offline data replication.
72. Tech
System Foundation
Fizzy
go/fizzy
Fizzy is a piece of LinkedIn infrastructure that
is responsible for aggregating UI components
served off of different web applications into a
single page.
Rest.li (Pegasus)
go/restli
Rest.li is a REST+JSON framework for
building robust, scalable service
architectures using dynamic discovery and
simple asynchronous APIs
Apache Traffic Server
go/ats
Fast, scalable and extensible reverse proxy
and forward proxy HTTP server.
73. Tech
System Foundation
EKG
go/whatisekg
With canary validation, exception monitoring,
GC monitoring and auto-tuning, EKG is our
tool for monitoring the health of our systems in
production.
Hadoop
go/hadoop
Enables the distributed processing of large
data sets across clusters of commodity
servers.
Avro
go/espresso
Apache Avro™ is a data serialization system,
providing a serialization format for persistent
data and a compact binary format for
communication between services.
74. Frameworks
System Foundation
LISpring
go/lispring
LI Spring is an extended version of Spring, the
enterprise Java application development
framework with support dependency injection
(wiring of components) and much more.
Play
go/play
Play is an open source, lightweight, fully
reactive, stateless framework that
supports hot reload for Java and Scala.
75. Craig Sebenik
Staff Site Reliability Engineer
!
Derek Brown
Lead, Web Development
Subject Matter Experts