This document summarizes a presentation given by Bianca Jiang and Ginny Ghezzo at the O'Reilly Software Architecture Conference on March 18, 2015 about re-architecting maintenance for continuous delivery. The presentation discussed the challenges faced with traditional maintenance approaches and how adopting DevOps practices like automation, continuous delivery and testing can help improve maintenance by providing quicker, higher quality updates on a more predictable schedule with lower costs. Key aspects covered included implementing maintenance as incremental patches in an automated pipeline, generating documentation, and ensuring quality through continuous testing. The goal is to make maintenance a seamless process for customers.
7 Practices to Expand Performance and Effective Collaboration in DevOpsDynatrace
When apps fail, whose fault is it? In today’s DevOps world, every stakeholder in the app delivery chain is accountable for various aspects of performance, scalability, and availability.
Mark Tomlinson, performance engineering veteran and founder of the popular PerfBytes podcast, and Andreas Grabner, Dynatrace performance advocate, share seven practices to help you expand performance and effective collaboration into your DevOps team, including:
• Why DevOps means you need to check your ego at the door
• What metrics each role across teams can focus on to build quality and performance
• How to use, measure and report these metrics
• What performance means for different stakeholders and the resources required
• Examples of how increased collaboration and responsibility can improve performance
The Challenges & Pitfalls of Database Continuous DeliveryPerforce
Practicing database Continuous Delivery saves time and money and prevents downtime in production. However, dealing with automating database deployments is tricky. In this presentation, you will learn how to overcome the challenges and potential pitfalls of database Continuous Delivery and proven best practices for automating database changes.
This document provides an overview of a webinar on best practices for continuous delivery and including databases. It discusses how continuous delivery is becoming more important and widespread. However, databases are often left out of continuous delivery processes due to challenges like manual scripting and lack of version control. To fully realize the benefits of continuous delivery, databases need to be brought into the process through practices like source control for all files including database scripts, automation, and ensuring the database is in sync with other code changes. Vendor tools discussed help achieve this through features like database version control, deployment automation, and change impact analysis.
Talk about the basic principles and concepts of CI/CD as a set of practices in order to reduce integration errors through automated implementations for testing and deployments as well as the tooling behind this philosophy.
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.
5 Key Metrics to Release Better Software FasterDynatrace
No matter how often you deploy your application, or how sophisticated your delivery pipeline is, you always need to know the quality status of the software you are building. This can only be done if you measure it. But measure what exactly?
Andreas Grabner and Brett Hofer, app performance evangelists, explain five key metrics to increase your confidence in securing a safe build for production.
• Learn why metrics can be huge quality gateways
• Identify key metrics to take back to your team (Dev, Test, Ops and Business)
• Understand how to use, measure and report these metrics
• 3 short use cases and how using metrics can help you avoid them
Continuous integration (CI) and continuous delivery (CD) are practices that allow developers to integrate code changes frequently and reliably while automating the process of building, testing, and deploying the code. With CI/CD, code changes are validated through automated builds and tests before being deployed to staging environments and potentially production. The CI/CD workflow involves committing code to a repository, running automated tests, building if tests pass, deploying to staging for further testing, and deploying to production if all tests are passed, with the ability to rollback changes if needed. Tools used in CI/CD include those for version control, building, testing, and deploying code changes across environments.
This document discusses challenges with deploying certain types of application components and strategies for addressing them. It begins by noting that database schema updates, mainframe code changes, and application server configuration changes can be difficult to deploy due to issues like lack of source control and inconsistent processes. Automating the deployment of these components is important to avoid errors and ensure consistency. The document then provides examples of how tools can help with tasks like database change management, modeling application server configurations, and managing mainframe code deployments in an incremental fashion. Overall, it advocates for representing complex deployment components as code that can be versioned and deployed in a reliable, automated manner.
7 Practices to Expand Performance and Effective Collaboration in DevOpsDynatrace
When apps fail, whose fault is it? In today’s DevOps world, every stakeholder in the app delivery chain is accountable for various aspects of performance, scalability, and availability.
Mark Tomlinson, performance engineering veteran and founder of the popular PerfBytes podcast, and Andreas Grabner, Dynatrace performance advocate, share seven practices to help you expand performance and effective collaboration into your DevOps team, including:
• Why DevOps means you need to check your ego at the door
• What metrics each role across teams can focus on to build quality and performance
• How to use, measure and report these metrics
• What performance means for different stakeholders and the resources required
• Examples of how increased collaboration and responsibility can improve performance
The Challenges & Pitfalls of Database Continuous DeliveryPerforce
Practicing database Continuous Delivery saves time and money and prevents downtime in production. However, dealing with automating database deployments is tricky. In this presentation, you will learn how to overcome the challenges and potential pitfalls of database Continuous Delivery and proven best practices for automating database changes.
This document provides an overview of a webinar on best practices for continuous delivery and including databases. It discusses how continuous delivery is becoming more important and widespread. However, databases are often left out of continuous delivery processes due to challenges like manual scripting and lack of version control. To fully realize the benefits of continuous delivery, databases need to be brought into the process through practices like source control for all files including database scripts, automation, and ensuring the database is in sync with other code changes. Vendor tools discussed help achieve this through features like database version control, deployment automation, and change impact analysis.
Talk about the basic principles and concepts of CI/CD as a set of practices in order to reduce integration errors through automated implementations for testing and deployments as well as the tooling behind this philosophy.
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.
5 Key Metrics to Release Better Software FasterDynatrace
No matter how often you deploy your application, or how sophisticated your delivery pipeline is, you always need to know the quality status of the software you are building. This can only be done if you measure it. But measure what exactly?
Andreas Grabner and Brett Hofer, app performance evangelists, explain five key metrics to increase your confidence in securing a safe build for production.
• Learn why metrics can be huge quality gateways
• Identify key metrics to take back to your team (Dev, Test, Ops and Business)
• Understand how to use, measure and report these metrics
• 3 short use cases and how using metrics can help you avoid them
Continuous integration (CI) and continuous delivery (CD) are practices that allow developers to integrate code changes frequently and reliably while automating the process of building, testing, and deploying the code. With CI/CD, code changes are validated through automated builds and tests before being deployed to staging environments and potentially production. The CI/CD workflow involves committing code to a repository, running automated tests, building if tests pass, deploying to staging for further testing, and deploying to production if all tests are passed, with the ability to rollback changes if needed. Tools used in CI/CD include those for version control, building, testing, and deploying code changes across environments.
This document discusses challenges with deploying certain types of application components and strategies for addressing them. It begins by noting that database schema updates, mainframe code changes, and application server configuration changes can be difficult to deploy due to issues like lack of source control and inconsistent processes. Automating the deployment of these components is important to avoid errors and ensure consistency. The document then provides examples of how tools can help with tasks like database change management, modeling application server configurations, and managing mainframe code deployments in an incremental fashion. Overall, it advocates for representing complex deployment components as code that can be versioned and deployed in a reliable, automated manner.
This presentation provides a clear path for your agile project by using a handful of simple steps. Don’t expect an ambiguous restatement of the Agile Manifesto. You will learn specific steps that will challenge your team and delight your customers.
Serena DevOps Drive-in: Leading the Agile and DevOps transformation with Gary...Serena Software
DevOps is not just for start-ups! However, scaling DevOps in large enterprises requires shifting of culture, coordination of work across teams, reinvention of legacy applications and much more. Before you undertake any change to improve your software development processes, you would want to learn from the person who has gone before you and tasted success. Join the conversation with Gary Gruver on our next DevOps drive-in webcast. Gary will share his best practices and recommendations from his groundbreaking work at HP and Macy's and talk about how to lead a successful DevOps transformation.
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.
Case Study: How The Home Depot Built Quality Into Software DevelopmentCA Technologies
This session will cover how The Home Depot built quality into its software development as it migrated from waterfall to agile delivery.
For more information on DevOps: Continuous Delivery, please visit: http://ow.ly/hAXz50g62ZM
Get Mapped: Using Value Stream Mapping to Create a DevOps Adoption RoadmapIBM UrbanCode Products
Adopting DevOps is not a “one-and-done” project. It is adopting a mindset, a culture. It is a commitment to a journey of continuous improvement by adopting a set of capabilities and practices that are based on Lean principles. Adopting DevOps requires process improvement, automation of the processes using tools, and organizational change to enable a DevOps culture.
The question then becomes – where does one start?
Best Practices for Continuous Delivery in Financial ServicesDynatrace
The document discusses best practices for continuous delivery in financial services. It advocates for starting with the customer experience rather than the application, preventing problems before they impact customers. Gap-free data across the entire delivery chain is essential. The goal is enabling DevOps rather than just operations. Dynatrace provides unified user and application insights to help optimize spend, improve release quality, and keep up with changing customer expectations.
Continuous Delivery is hot. As we all increasingly compete using software, the business always wants more change faster. However, change is seen as risky. How do we deliver quickly while not exposing the business to excessive risk? What does this imply for how we update our mission critical databases?
Successful continuous delivery efforts use quality as an enabler of rapid change. Rapid feedback on the quality of the application, and a disciplined, high quality process support frequent delivery of business value, rather than frequent outage.
IBM UrbanCode’s Eric Minick and DBmaestro’s Yaniv Yehuda present how to build safety in to your delivery process. We will look at database change in some detail while delivering generally applicable lessons.
DevOps Continuous Integration & Delivery - A Whitepaper by RapidValueRapidValue
In this whitepaper, we will deep dive into the concept of continuous integration, continuous delivery and continuous deployment and explain how businesses can benefit from this. We will also elucidate on how to build an effective CI/CD pipeline and some of the best practices for your enterprise DevOps journey.
This talk will explain the secret of the success of the Eclipse Platform team. The Eclipse Way is an agile software development process that we started right at the beginning when we started to develop Eclipse back in 1999. It was and is used by the Eclipse Platform team and got continuously improved over time. During the session you will hear about all our practices, like milestones, early and iterative planning, continuous integration and the endgame. I will also reveal some of the history behind the Eclipse top-level project.
More details: https://confengine.com/eclipse-summit-2016/proposal/2386/the-eclipse-way
Software Defect Prevention via Continuous InspectionJosh Gough
Research and guidance for educing software development risk and cost while improving speed, quality and maintainability by applying review at all levels.
From Continuous Integration to Continuous Delivery and DevOpsLuca Minudel
An overview of Continuous Delivery from a business and a technical point of view.
Includes an overview of:
- business value proposition of CD
- prerequisites and tips for CD implementation
- CD implementation was stories and strategies
- CD technical practices
JavaOne 2015 - Swimming upstream in the container revolutionBert Jan Schrijver
Bert Jan Schrijver discusses Malmberg's transition from traditional operations to a containerless continuous delivery model using DevOps principles. Some key challenges included cultural resistance to change, infrastructure limits with Amazon, and ensuring proper testing environments. The approach established expert teams, defined clear principles like infrastructure as code and no downtime, and benefited the business through increased agility, availability, and cost reductions. Areas of ongoing focus include monitoring, performance and security testing, and automated resilience testing.
There in an obsessions to jump to implementation of CI, CD tools when we talk about DevOps. In this talk, I focus on the many aspects that one needs to focus on when going on a DevOps journey
Many companies are investing heavily in automation. Good high quality automation is key as companies move towards a successful DevOps model. The problem is that automation scripts can be very brittle and tend to not cover or test the entire application. They are also very difficult and time consuming to keep up to date.
This presentation will include a demonstration of how to design, create and update automation scripts as well as their associated test data and end points.
On this webcast learn how to make automated testing a reality.
Continuous delivery requires more that DevOps. It also requires one to think differently about product design, development & testing, and the overall structure of the organization. This presentation will help you understand what it takes and why one would want to deliver value to your customers multiple times each day. #CIC
Jeff "Cheezy" Morgan Ardita Karaj
Startup safari 2020 making s3 more resilient using lambda@edgeJúlia Biró
The document discusses using Lambda@Edge to modify requests to enable active-active file delivery from S3 across multiple regions for high availability. Specifically, it describes using Lambda@Edge functions to change the host header and S3 region in requests to allow routing requests to S3 buckets in different regions for files. This provides active-active capabilities for S3 file delivery across regions without downtime for failover or maintenance by dynamically routing requests.
Organizations like Google, Amazon, Facebook, and Netflix employ DevOps practices to deploy code into production hundreds, or even thousands, of times per day, while providing world-class availability, reliability, and security. In contrast, many organizations struggle to release every nine months.
But DevOps isn't just for the Unicorns.
Gene Kim, co-author of The Phoenix Project and the upcoming DevOps Cookbook, shares:
• How you can replicate the DevOps practices and outcomes of the so-called “Unicorns”
• The top lessons learned in his study of high-performing technology organizations
• How you can apply these lessons at your company
Register for “DevOps: From Adoption to Performance” and learn how even large, complex organizations across almost every vertical are using DevOps practices to replicate the technology and performance feats of the “Unicorns.”
https://info.dynatrace.com/apm_wc_Gene_Kim_webinar_na_registration.html
Required to work on Budgeting and Forecasting project where there is a short release cycle of 2-3 months we created multiple review cycles that assured that there was no requirement miss for testing. This further helped in reducing production issues, which needed patch releases, saving both time and cost for the client.
The document discusses shifting development processes left to improve quality and reduce costs. It outlines five simple steps to achieve this: 1) build every change, 2) code review every change, 3) use static analysis regularly, 4) be aware of third-party vulnerabilities, and 5) provide visibility of changes. Continuous inspection is presented as a way to put code changes through expert reviews to rapidly identify issues. The benefits of practices like continuous integration, continuous delivery, and DevOps for regulated industries are also discussed.
Case Study: How The Home Depot Built Quality Into Software DevelopmentCA Technologies
This session will cover how The Home Depot built quality into its software development as it migrated from waterfall to agile delivery.
For more information on DevOps: Continuous Delivery, please visit: http://cainc.to/CAW17-CD
This presentation provides a clear path for your agile project by using a handful of simple steps. Don’t expect an ambiguous restatement of the Agile Manifesto. You will learn specific steps that will challenge your team and delight your customers.
Serena DevOps Drive-in: Leading the Agile and DevOps transformation with Gary...Serena Software
DevOps is not just for start-ups! However, scaling DevOps in large enterprises requires shifting of culture, coordination of work across teams, reinvention of legacy applications and much more. Before you undertake any change to improve your software development processes, you would want to learn from the person who has gone before you and tasted success. Join the conversation with Gary Gruver on our next DevOps drive-in webcast. Gary will share his best practices and recommendations from his groundbreaking work at HP and Macy's and talk about how to lead a successful DevOps transformation.
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.
Case Study: How The Home Depot Built Quality Into Software DevelopmentCA Technologies
This session will cover how The Home Depot built quality into its software development as it migrated from waterfall to agile delivery.
For more information on DevOps: Continuous Delivery, please visit: http://ow.ly/hAXz50g62ZM
Get Mapped: Using Value Stream Mapping to Create a DevOps Adoption RoadmapIBM UrbanCode Products
Adopting DevOps is not a “one-and-done” project. It is adopting a mindset, a culture. It is a commitment to a journey of continuous improvement by adopting a set of capabilities and practices that are based on Lean principles. Adopting DevOps requires process improvement, automation of the processes using tools, and organizational change to enable a DevOps culture.
The question then becomes – where does one start?
Best Practices for Continuous Delivery in Financial ServicesDynatrace
The document discusses best practices for continuous delivery in financial services. It advocates for starting with the customer experience rather than the application, preventing problems before they impact customers. Gap-free data across the entire delivery chain is essential. The goal is enabling DevOps rather than just operations. Dynatrace provides unified user and application insights to help optimize spend, improve release quality, and keep up with changing customer expectations.
Continuous Delivery is hot. As we all increasingly compete using software, the business always wants more change faster. However, change is seen as risky. How do we deliver quickly while not exposing the business to excessive risk? What does this imply for how we update our mission critical databases?
Successful continuous delivery efforts use quality as an enabler of rapid change. Rapid feedback on the quality of the application, and a disciplined, high quality process support frequent delivery of business value, rather than frequent outage.
IBM UrbanCode’s Eric Minick and DBmaestro’s Yaniv Yehuda present how to build safety in to your delivery process. We will look at database change in some detail while delivering generally applicable lessons.
DevOps Continuous Integration & Delivery - A Whitepaper by RapidValueRapidValue
In this whitepaper, we will deep dive into the concept of continuous integration, continuous delivery and continuous deployment and explain how businesses can benefit from this. We will also elucidate on how to build an effective CI/CD pipeline and some of the best practices for your enterprise DevOps journey.
This talk will explain the secret of the success of the Eclipse Platform team. The Eclipse Way is an agile software development process that we started right at the beginning when we started to develop Eclipse back in 1999. It was and is used by the Eclipse Platform team and got continuously improved over time. During the session you will hear about all our practices, like milestones, early and iterative planning, continuous integration and the endgame. I will also reveal some of the history behind the Eclipse top-level project.
More details: https://confengine.com/eclipse-summit-2016/proposal/2386/the-eclipse-way
Software Defect Prevention via Continuous InspectionJosh Gough
Research and guidance for educing software development risk and cost while improving speed, quality and maintainability by applying review at all levels.
From Continuous Integration to Continuous Delivery and DevOpsLuca Minudel
An overview of Continuous Delivery from a business and a technical point of view.
Includes an overview of:
- business value proposition of CD
- prerequisites and tips for CD implementation
- CD implementation was stories and strategies
- CD technical practices
JavaOne 2015 - Swimming upstream in the container revolutionBert Jan Schrijver
Bert Jan Schrijver discusses Malmberg's transition from traditional operations to a containerless continuous delivery model using DevOps principles. Some key challenges included cultural resistance to change, infrastructure limits with Amazon, and ensuring proper testing environments. The approach established expert teams, defined clear principles like infrastructure as code and no downtime, and benefited the business through increased agility, availability, and cost reductions. Areas of ongoing focus include monitoring, performance and security testing, and automated resilience testing.
There in an obsessions to jump to implementation of CI, CD tools when we talk about DevOps. In this talk, I focus on the many aspects that one needs to focus on when going on a DevOps journey
Many companies are investing heavily in automation. Good high quality automation is key as companies move towards a successful DevOps model. The problem is that automation scripts can be very brittle and tend to not cover or test the entire application. They are also very difficult and time consuming to keep up to date.
This presentation will include a demonstration of how to design, create and update automation scripts as well as their associated test data and end points.
On this webcast learn how to make automated testing a reality.
Continuous delivery requires more that DevOps. It also requires one to think differently about product design, development & testing, and the overall structure of the organization. This presentation will help you understand what it takes and why one would want to deliver value to your customers multiple times each day. #CIC
Jeff "Cheezy" Morgan Ardita Karaj
Startup safari 2020 making s3 more resilient using lambda@edgeJúlia Biró
The document discusses using Lambda@Edge to modify requests to enable active-active file delivery from S3 across multiple regions for high availability. Specifically, it describes using Lambda@Edge functions to change the host header and S3 region in requests to allow routing requests to S3 buckets in different regions for files. This provides active-active capabilities for S3 file delivery across regions without downtime for failover or maintenance by dynamically routing requests.
Organizations like Google, Amazon, Facebook, and Netflix employ DevOps practices to deploy code into production hundreds, or even thousands, of times per day, while providing world-class availability, reliability, and security. In contrast, many organizations struggle to release every nine months.
But DevOps isn't just for the Unicorns.
Gene Kim, co-author of The Phoenix Project and the upcoming DevOps Cookbook, shares:
• How you can replicate the DevOps practices and outcomes of the so-called “Unicorns”
• The top lessons learned in his study of high-performing technology organizations
• How you can apply these lessons at your company
Register for “DevOps: From Adoption to Performance” and learn how even large, complex organizations across almost every vertical are using DevOps practices to replicate the technology and performance feats of the “Unicorns.”
https://info.dynatrace.com/apm_wc_Gene_Kim_webinar_na_registration.html
Required to work on Budgeting and Forecasting project where there is a short release cycle of 2-3 months we created multiple review cycles that assured that there was no requirement miss for testing. This further helped in reducing production issues, which needed patch releases, saving both time and cost for the client.
The document discusses shifting development processes left to improve quality and reduce costs. It outlines five simple steps to achieve this: 1) build every change, 2) code review every change, 3) use static analysis regularly, 4) be aware of third-party vulnerabilities, and 5) provide visibility of changes. Continuous inspection is presented as a way to put code changes through expert reviews to rapidly identify issues. The benefits of practices like continuous integration, continuous delivery, and DevOps for regulated industries are also discussed.
Case Study: How The Home Depot Built Quality Into Software DevelopmentCA Technologies
This session will cover how The Home Depot built quality into its software development as it migrated from waterfall to agile delivery.
For more information on DevOps: Continuous Delivery, please visit: http://cainc.to/CAW17-CD
Dev Tested, Ops Approved: 10 Guardrails from Atlassian for Better, Faster Dev...Amazon Web Services
Over the years, Atlassian's engineering teams have developed a set of proven and dependable DevOps practices that have allowed us to increase velocity and ship more reliably. Like many of you, Atlassian is grappling with complex, distributed teams; ever-increasing demand on our products and services; and a greater need than ever for a fast, stable release cadence and reliable uptime. This year, we're going to be sharing 10 of our dev tested, ops approved practices with you. In this session, we discuss: how Atlassian tools integrate with AWS to break down silos, increase development speed, and minimize system outages; how to scale the DevOps basics, from building a culture of collaboration to quadrupling your release cadence; and how to track the business value of what you're building, using, deploying, and repairing.
Session Sponsored by Atlassian.
How to Better Manage Technical Debt While Innovating on DevOpsDynatrace
Forget the “Unicorns.” There is a lot to learn from “DevOps Unicorns” such as Etsy or Facebook, but for enterprises dealing with technical debt in legacy systems developed by teams no longer with the company, copying the unicorns is not an option.
Richard Dominguez, Operations Developer at Prep Sportswear, needed to “keep the lights on” for their legacy systems, while enabling his DevOps teams to launch new features much faster. Today Prep Sportswear releases more updates to their legacy systems than ever before by reducing MTTR (Mean Time To Repair), giving them more time to innovate on DevOps and Continuous Delivery on their new platform. You’ll learn:
• Top metrics for an Ops dashboard to catch potential issues early
• Tips to manage technical debt in legacy code caused by dev teams long gone
• Efficient ways to close loops while providing input to DevOps so they can optimize innovation and releases
This document provides a summary of the applicant's professional experience in infrastructure services including storage and backups. The applicant has over 15 years of experience working with various storage technologies such as Hitachi, EMC, and NetApp arrays. Some of the projects summarized include disaster recovery, backup performance improvement, operating system upgrades, and automation of media recall processes. The applicant aims to ensure high availability, meet SLAs, and minimize downtime through their work.
Arguments in favor of a progressive software rewrite Sylvain Leroy
Arguments in favor of a progressive software rewrite .
It's a presentation about why software should be preserved and .
Written and adapted for Byoskill.
Byoskill.com
Arguments in favor of a progressive software rewrite Sylvain Leroy
Arguments in favor of a progressive software rewrite .
Blog post here : https://sylvainleroy.com/2018/06/18/to-rewrite-or-not-to-rewrite-a-software/
It's a presentation about why software should be preserved and .
Written and adapted for Byoskill.
Byoskill.com
This document discusses continuous delivery and DevOps. It begins by providing background on the speaker and his previous experience implementing continuous delivery. It then discusses the pillars of continuous delivery, including continuous integration, automated testing, and DevOps. Continuous integration involves frequent code check-ins and automated testing. Automated testing emphasizes testing software throughout development rather than after completion. DevOps aims to break down silos between teams and foster collaboration. The document argues these practices can help teams make decisions and get feedback faster to continuously improve products. Case studies from Netflix, HP, and others demonstrate how continuous delivery can reduce costs and cycle times. The ultimate goal is reaching a state where software can be deployed to production on demand without issues.
Textbook continuous delivery sounds great. We commit code, build it, deploy into a test lab, test and then promote to production. Clean, simple and effective. The reality for most applications is that some of their test environments are named things like "system integration". When tests validate integrated systems, releases to production generally involve all the services that were changed and tested together rather than just a single build. We have release managers who specialize in making sure all the moving parts get delivered together. Meanwhile, some parts of systems are not even built and others like database schemas are updated incrementally. The textbook build pipeline may not be good enough.
OpenTuesday: Aktuelle Standards der agilen SoftwareentwicklungDigicomp Academy AG
Dieses OpenTuesday-Referat von Michael Palotas ging gezielt auf die sogenannten «Agile Engineering Practices» ein und zeigte anhand praktischer Beispiele auf, wie die Anwendung dieser Praktiken als Enabler für agile Softwareentwicklung fungieren.
Es gibt wohl kaum eine Firma, bei der agile Softwareentwicklung kein Thema ist. Viele Organisationen haben sich schon auf den Weg begeben, agil zu werden. Im ersten Schritt bedeutet dies in der Regel, die Prozesse auf eine agile Methodik wie z.B. SCRUM zu ändern.
Auf der Strecke bleiben jedoch oft die (agilen) Entwicklungs-, Test- und Liefermethoden wie Continuous Integration, Test-Automatisierung, Test Driven Development, Pair Programming etc., die eine agile Vorgehensweise erst richtig ermöglichen.
[WSO2Con EU 2017] Continuous Integration, Delivery and Deployment: Accelerate...WSO2
Continuous integration, continuous delivery, and continuous deployment are essential practices adopted by agile organizations to meet the new demands of digital transformation. Ultimately, the goal is to accelerate development and test processes and get new code out to production fast. This slide deck focuses on sustainably flowing ideas into the hands of customers in the form of innovative digital capabilities and applications, and continuously improving the digital business with CI/CD.
This document discusses agile software development and the Scrum framework. It provides an overview of traditional waterfall and V-model development approaches and their limitations. It then introduces agile principles and Scrum roles, ceremonies, and artifacts. Key aspects of Scrum covered include user stories, product backlogs, sprint planning, daily stand-ups, and scaling Scrum through Scrum of Scrums. The document aims to provide information to teams on transforming to agile development practices.
The promise of DevOps is that we can push new ideas out to market faster while avoiding delivering serious defects into production. Andreas Grabner explains that testers are no longer measured by the number of defect reports they enter, nor are developers measured by the lines of code they write. As a team, you are measured by how fast you can deploy high quality functionality to the end user. Achieving this goal requires testers to increase their skills. It’s all about finding solutions—not just problems. Testers must transition from reporting “app crashes” to providing details such as “memory leak caused by bad cache implementation.” Instead of reporting “it’s slow,” testers must discover “wrong hibernate configuration causes too much traffic from the database.” Using three real-life examples, Andreas illustrates what it takes for testing teams to become part of the DevOps transformation—bringing more value to the entire organization.
PPT Presented at Morton's Steak House in San Francisco. It covers the Monitoring Redefined message as well as how Dynatrace transformed to maintain market share in the new world.
The document summarizes a presentation about progressive web applications (PWAs). It defines PWAs as web applications that use common web technologies like HTML, CSS, and JavaScript to provide native-like experiences on mobile and desktop. It outlines key technical aspects PWAs must have like service workers, manifest files, and HTTPS. It discusses benefits of PWAs like increased engagement, performance, and ease of development/maintenance compared to native apps and regular web apps. Finally, it provides a comparison of capabilities for web apps, native apps, and PWAs.
Traditional testing isn't keeping pace with the speed of DevOps and Continuous Delivery, but hope is not lost. AI will be used to make testing faster and more accessible to all.
Existing QA solutions were built for a world where software changed infrequently. Highly adopted tools such as Selenium, Appium, and JUnit require a specialized skillset, and require too much maintenance once you start factoring in the brittle nature of tests, and the infrastructure required to run tests at scale. But there is still hope for QA in machine intelligence.
Next-generation ML tools are here to help QA keep up with the agility of modern software delivery practices. You'll learn what ML strategies are being employed to make this possible, and what the future of QA - intelligent testing - looks like.
Takeaways:
- An overview of the QA tooling and vendor landscape
- Demystifying the buzzwords - what machine intelligence in testing means today and tomorrow
- How implementing DevTestOps can help increase test coverage and improve product quality
Web.dev extended : What's new in Web [GDG Taichung]Chieh Kai Yang
The document summarizes Irene Chang's presentation on Web Vitals at GDG Taichung. The presentation covered:
- An introduction to Web Vitals and the metrics of LCP, FID, and CLS which measure key aspects of page experience.
- Tools for measuring Web Vitals like Lighthouse, Chrome DevTools, and the CrUX dashboard.
- The Vital Loop process of using tools to monitor field data, prevent regressions, get optimization guidance, and diagnose issues to improve page experience.
- Other topics briefly covered included the Web Vitals library, Stories format, and more sessions available on web.dev.
Webinar: Demonstrating Business Value for DevOps & Continuous DeliveryXebiaLabs
The document discusses DevOps and continuous delivery. It begins with an introduction and agenda. It then discusses transforming IT operations for greater business value, challenges for businesses and IT that DevOps addresses, what DevOps is in terms of people, processes, and tools. It discusses continuous delivery and provides examples of goals and metrics for DevOps initiatives like release frequency, throughput time, and idle time. Finally, it discusses how DevOps tools can work with other tools and processes.
A Comprehensive Guide on Implementing Real-World Mobile Testing Strategies fo...kalichargn70th171
In today's fiercely competitive mobile app market, the role of the QA team is pivotal for continuous improvement and sustained success. Effective testing strategies are essential to navigate the challenges confidently and precisely. Ensuring the perfection of mobile apps before they reach end-users requires thoughtful decisions in the testing plan.
Project Management: The Role of Project Dashboards.pdfKarya Keeper
Project management is a crucial aspect of any organization, ensuring that projects are completed efficiently and effectively. One of the key tools used in project management is the project dashboard, which provides a comprehensive view of project progress and performance. In this article, we will explore the role of project dashboards in project management, highlighting their key features and benefits.
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
The Key to Digital Success_ A Comprehensive Guide to Continuous Testing Integ...kalichargn70th171
In today's business landscape, digital integration is ubiquitous, demanding swift innovation as a necessity rather than a luxury. In a fiercely competitive market with heightened customer expectations, the timely launch of flawless digital products is crucial for both acquisition and retention—any delay risks ceding market share to competitors.
Unveiling the Advantages of Agile Software Development.pdfbrainerhub1
Learn about Agile Software Development's advantages. Simplify your workflow to spur quicker innovation. Jump right in! We have also discussed the advantages.
Mobile App Development Company In Noida | Drona InfotechDrona Infotech
Drona Infotech is a premier mobile app development company in Noida, providing cutting-edge solutions for businesses.
Visit Us For : https://www.dronainfotech.com/mobile-application-development/
UI5con 2024 - Keynote: Latest News about UI5 and it’s EcosystemPeter Muessig
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
A neural network is a machine learning program, or model, that makes decisions in a manner similar to the human brain, by using processes that mimic the way biological neurons work together to identify phenomena, weigh options and arrive at conclusions.
Odoo releases a new update every year. The latest version, Odoo 17, came out in October 2023. It brought many improvements to the user interface and user experience, along with new features in modules like accounting, marketing, manufacturing, websites, and more.
The Odoo 17 update has been a hot topic among startups, mid-sized businesses, large enterprises, and Odoo developers aiming to grow their businesses. Since it is now already the first quarter of 2024, you must have a clear idea of what Odoo 17 entails and what it can offer your business if you are still not aware of it.
This blog covers the features and functionalities. Explore the entire blog and get in touch with expert Odoo ERP consultants to leverage Odoo 17 and its features for your business too.
An Overview of Odoo ERP
Odoo ERP was first released as OpenERP software in February 2005. It is a suite of business applications used for ERP, CRM, eCommerce, websites, and project management. Ten years ago, the Odoo Enterprise edition was launched to help fund the Odoo Community version.
When you compare Odoo Community and Enterprise, the Enterprise edition offers exclusive features like mobile app access, Odoo Studio customisation, Odoo hosting, and unlimited functional support.
Today, Odoo is a well-known name used by companies of all sizes across various industries, including manufacturing, retail, accounting, marketing, healthcare, IT consulting, and R&D.
The latest version, Odoo 17, has been available since October 2023. Key highlights of this update include:
Enhanced user experience with improvements to the command bar, faster backend page loading, and multiple dashboard views.
Instant report generation, credit limit alerts for sales and invoices, separate OCR settings for invoice creation, and an auto-complete feature for forms in the accounting module.
Improved image handling and global attribute changes for mailing lists in email marketing.
A default auto-signature option and a refuse-to-sign option in HR modules.
Options to divide and merge manufacturing orders, track the status of manufacturing orders, and more in the MRP module.
Dark mode in Odoo 17.
Now that the Odoo 17 announcement is official, let’s look at what’s new in Odoo 17!
What is Odoo ERP 17?
Odoo 17 is the latest version of one of the world’s leading open-source enterprise ERPs. This version has come up with significant improvements explained here in this blog. Also, this new version aims to introduce features that enhance time-saving, efficiency, and productivity for users across various organisations.
Odoo 17, released at the Odoo Experience 2023, brought notable improvements to the user interface and added new functionalities with enhancements in performance, accessibility, data analysis, and management, further expanding its reach in the market.
Preparing Non - Technical Founders for Engaging a Tech AgencyISH Technologies
Preparing non-technical founders before engaging a tech agency is crucial for the success of their projects. It starts with clearly defining their vision and goals, conducting thorough market research, and gaining a basic understanding of relevant technologies. Setting realistic expectations and preparing a detailed project brief are essential steps. Founders should select a tech agency with a proven track record and establish clear communication channels. Additionally, addressing legal and contractual considerations and planning for post-launch support are vital to ensure a smooth and successful collaboration. This preparation empowers non-technical founders to effectively communicate their needs and work seamlessly with their chosen tech agency.Visit our site to get more details about this. Contact us today www.ishtechnologies.com.au
INTRODUCTION TO AI CLASSICAL THEORY TARGETED EXAMPLESanfaltahir1010
Image: Include an image that represents the concept of precision, such as a AI helix or a futuristic healthcare
setting.
Objective: Provide a foundational understanding of precision medicine and its departure from traditional
approaches
Role of theory: Discuss how genomics, the study of an organism's complete set of AI ,
plays a crucial role in precision medicine.
Customizing treatment plans: Highlight how genetic information is used to customize
treatment plans based on an individual's genetic makeup.
Examples: Provide real-world examples of successful application of AI such as genetic
therapies or targeted treatments.
Importance of molecular diagnostics: Explain the role of molecular diagnostics in identifying
molecular and genetic markers associated with diseases.
Biomarker testing: Showcase how biomarker testing aids in creating personalized treatment plans.
Content:
• Ethical issues: Examine ethical concerns related to precision medicine, such as privacy, consent, and
potential misuse of genetic information.
• Regulations and guidelines: Present examples of ethical guidelines and regulations in place to safeguard
patient rights.
• Visuals: Include images or icons representing ethical considerations.
Content:
• Ethical issues: Examine ethical concerns related to precision medicine, such as privacy, consent, and
potential misuse of genetic information.
• Regulations and guidelines: Present examples of ethical guidelines and regulations in place to safeguard
patient rights.
• Visuals: Include images or icons representing ethical considerations.
Content:
• Ethical issues: Examine ethical concerns related to precision medicine, such as privacy, consent, and
potential misuse of genetic information.
• Regulations and guidelines: Present examples of ethical guidelines and regulations in place to safeguard
patient rights.
• Visuals: Include images or icons representing ethical considerations.
Real-world case study: Present a detailed case study showcasing the success of precision
medicine in a specific medical scenario.
Patient's journey: Discuss the patient's journey, treatment plan, and outcomes.
Impact: Emphasize the transformative effect of precision medicine on the individual's
health.
Objective: Ground the presentation in a real-world example, highlighting the practical
application and success of precision medicine.
Data challenges: Address the challenges associated with managing large sets of patient data in precision
medicine.
Technological solutions: Discuss technological innovations and solutions for handling and analyzing vast
datasets.
Visuals: Include graphics representing data management challenges and technological solutions.
Objective: Acknowledge the data-related challenges in precision medicine and highlight innovative solutions.
Data challenges: Address the challenges associated with managing large sets of patient data in precision
medicine.
Technological solutions: Discuss technological innovations and solutions
Measures in SQL (SIGMOD 2024, Santiago, Chile)Julian Hyde
SQL has attained widespread adoption, but Business Intelligence tools still use their own higher level languages based upon a multidimensional paradigm. Composable calculations are what is missing from SQL, and we propose a new kind of column, called a measure, that attaches a calculation to a table. Like regular tables, tables with measures are composable and closed when used in queries.
SQL-with-measures has the power, conciseness and reusability of multidimensional languages but retains SQL semantics. Measure invocations can be expanded in place to simple, clear SQL.
To define the evaluation semantics for measures, we introduce context-sensitive expressions (a way to evaluate multidimensional expressions that is consistent with existing SQL semantics), a concept called evaluation context, and several operations for setting and modifying the evaluation context.
A talk at SIGMOD, June 9–15, 2024, Santiago, Chile
Authors: Julian Hyde (Google) and John Fremlin (Google)
https://doi.org/10.1145/3626246.3653374
8 Best Automated Android App Testing Tool and Framework in 2024.pdfkalichargn70th171
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Everything You Need to Know About X-Sign: The eSign Functionality of XfilesPr...XfilesPro
Wondering how X-Sign gained popularity in a quick time span? This eSign functionality of XfilesPro DocuPrime has many advancements to offer for Salesforce users. Explore them now!
How Can Hiring A Mobile App Development Company Help Your Business Grow?ToXSL Technologies
ToXSL Technologies is an award-winning Mobile App Development Company in Dubai that helps businesses reshape their digital possibilities with custom app services. As a top app development company in Dubai, we offer highly engaging iOS & Android app solutions. https://rb.gy/necdnt
How Can Hiring A Mobile App Development Company Help Your Business Grow?
Chaos to DevOps oreillysacon 2015
1. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Chaos to DevOps
Re-architecting Maintenance for Continuous Delivery
Bianca Jiang, Senior Software Engineer
Ginny C Ghezzo, Program Director
March 18, 2015
O’Reilly Software Architecture Conference
3. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
What is DevOps
“The agile, "devops" culture will move from the software development lab to the front office. That will
be required of sales and marketing, customer service, HR, product development… they (customers)
will expect you to behave differently. Rapid response, iterative, fast with quality. It is a rare front office
today that is ready for this.”
– Ginni Rometty, CEO IBM
3
5. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
CLM Improvements through DevOps
5
Continuous Delivery exposed some challenges in our implementation of
the IBM Software Support LifeCycle Policy
6. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Maintenance Solution in a DevOps Journey
Challenge: How do we deliver high quality, timely resolution
to defects that meets IBM’s Support Lifecycle agreement
1.Limited content through governance
2.Detailed description of content
3.Consistent for all Customers and Cumulative
4.Clarity on Upgrade Path
5.In-place installation
7.Easy Rollback
8.Right-sized
6
9. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Challenges exposed by CD
100+ product releases in Support Lifecyle in 2014
Half a million downloads from jazz.net
9
11. Cost of Traditional Maintenance - One Defect
4.0.6 Maintenance Stream
Joe’s 4.0.3 workspace
for Customer A
Mark’s 4.0.3 workspace
for Customer B
Lisa’s 3.0.1.6 workspace
for Customer B
Hot Fix
Hot Fix
Hot Fix
3.0.1.6 Maintenance Stream Full Releases
Customer A
Customer B
All
Full Releases
11
12. “The Matrix of Chaos”
APAR 1 APAR 2 APAR 3 … ...
… ...
12
13. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Mission
Quality , predictable and timely maintenance
that is a no-brainer to deploy and manage for
customers, with lower cost.
13
14. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Mission
Quality , predictable and timely maintenance
that is a no-brainer to deploy and manage for
customers, with lower cost.
L3 Subtitle:
Make customers happier, faster, with less resources
14
15. Maintenance Stream
WI 1
GA
WI 2 WI 3 WI 4 WI 5 WI 6
What is required of CLM Maintenance?
Delta
Scope:
● Corrective + Proactive Fixes
● Changes on Maintenance Stream after GA
Goal:
● Deliver the “delta”: timely, frequently, and iteratively with high quality
● Deploy the “delta”: easily, quickly, and continuously with low risk
15
16. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Mission
Quality , predictable and timely maintenance
that is a no-brainer to deploy and manage for
customers, with lower cost.
L3 Subtitle:
Make customers happier, faster, with less resources
16
17. Maintenance Stream
WI 1
GA
WI 2 WI 3 WI 4 WI 5 WI 6
Delta
Deploy
The Deploy & Build problem
Traditional Installer
1. directly modify existing
installed bits
2. can not rollback
3. big footprint
4. can’t do *iterative update*
17
18. Maintenance Stream
WI 1
Base
WI 2 WI 3 WI 4 WI 5 WI 6
Delta
Patch Service
Drop in one file to patch the entire server.
1. does not modify existing bits, run-time
2. fast, easy install, easy rollback
3. very lean
4. *iterative update* possible
Traditional Installer
1. directly modify existing
installed bits
2. can not rollback
3. big footprint
4. can’t do *iterative update*
Deploy
New Approach
The Deploy & Build problem
18
19. Maintenance Stream
WI 1
Base
WI 2 WI 3 WI 4 WI 5 WI 6
Delta
Deploy
The Deploy & Build problem
Traditional Installer
1. directly modify existing
installed bits
2. can not rollback
3. big footprint
4. can’t do *iterative update*
Patch Service
Drop in one file to patch the entire server.
1. does not modify existing bits, run-time
2. fast, easy install, easy rollback
3. very lean
4. *iterative update* possible
Make it Reusable!
19
New Approach
24. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Mission
Quality , predictable and timely maintenance
that is a no-brainer to deploy and manage for
customers, with lower cost.
24
25. Maintenance Stream
Patch
WI 1 WI 2 WI 3 WI 4 WI 5 WI 6
Easy to manage: Traceability
GA
Automation! Generate Manage
?
25
35. Manage
Automation!
Generate
Maintenance Stream
WI 1GA WI 2 WI 3 WI 4 WI 5 WI 6
Patch
readme.txt
Automation!
Deploy, Build and Documentation
Towards Continuous Delivery
resultchange
build
resultchange
build
change
build
result
35
36. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Mission
Quality , predictable and timely maintenance
that is a no-brainer to deploy and manage for
customers, with lower cost.
36
42. Quality: Continuous Testing
PipelineBuild
Unit Test
L3 DevDeploy
Acceptance Test
Scenario Test
Integration Test
Patch Content
Generate Notify
Change
Auto Auto Auto
Analyze
Failure & Fix
42
43. Quality: Continuous Testing
PipelineBuild
Unit Test
L3 Dev
Acceptance Test
Scenario Test
Integration Test
Patch Content
Additional
Manual Testing
Customer
Scenerio
Verification
change
build
feedback
deploy test
change
build
feedback
test
change
build
feedback
deploy test
change
build
result
43
44. Quality: Continuous Testing
PipelineBuild
Unit Test
L3 Dev
Acceptance Test
Scenario Test
Integration Test
Patch Content
Additional
Manual Testing
Customer
Scenerio
Verification
change
build
feedback
deploy test
change
build
feedback
test
change
build
feedback
deploy test
change
build
deploy
44
45. Quality: Continuous Testing
PipelineBuild
Unit Test
L3 Dev
Acceptance Test
Scenario Test
Integration Test
Patch Content
Additional
Manual Testing
Customer
Scenerio
Verification
change
build
feedback
deploy test
change
build
feedback
test
change
build
feedback
deploy test
change
build
deploy test
45
46. Quality: Continuous Testing
PipelineBuild
Unit Test
L3 Dev
Acceptance Test
Scenario Test
Integration Test
Patch Content
Additional
Manual Testing
Customer
Scenerio
Verification
change
build
feedback
deploy test
change
build
feedback
test
change
build
feedback
deploy test
change
build
feedback
deploy test
46
47. Quality: Continuous Testing
PipelineBuild
Unit Test
L3 Dev
Acceptance Test
Scenario Test
Integration Test
Patch Content
Additional
Manual Testing
Customer
Scenerio
Verification
change
build
feedback
deploy test
change
build
feedback
test
change
build
feedback
deploy test
change
build
feedback
deploy test
change
build
feedback
deploy test
change
build
feedback
deploy test
Quality Continuous Delivery
47
48. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Mission
Quality , predictable and timely maintenance
that is a no-brainer to deploy and manage for
customers, with lower cost.
48
49. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Process: Development & Delivery
• 1 Code Review, 1 Team Lead
Approval
•1 Code Review, 2 Team Lead
Approvals
•1 Code Review, 2 Team Lead
Approvals, 1 PMC Approval
49
50. Maintenance via iFix
Maintenance Stream
GA
Patch File 1
Non-Patch Files
Patch File 2
Non-Patch Files
Patch File 3
Non-Patch Files
iFix001
iFix002
iFix003 Latest
Customers
WI 1 WI 2 WI 3 WI 4 WI 5 WI 6
● Cumulative
● Continuous deploy
● Predictable
● Tracibility
● Upgrade Path
● Consistent
● Customer Feedback
● Agile
50
51. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Mission
Quality , predictable and timely maintenance
that is a no-brainer to deploy and manage for
customers, with lower cost.
51
52. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
CLM Maintenance Improvements
52
“The process to get the iFixes for CLM works perfect. I’m up and running with V.5.0.1 ifix004 within 30min
after announcement on first server. A big compliment to IBM Rational for this ifix concept and the
implementation of it. It’s a huge improvement for us as customers and it gives a lot of trust into the product.”
53. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
1. Smaller improvement, faster feedback loop
2. Short term investment, long term gain
3. Make it reusable, make it repeatable
4. [leadership] lead by example, lead by influence
5. [leadership] More on the why, less on the how
Feedback
Continuous Architecturing
Improve FeedbackImprove FeedbackImprove
Take away: DevOps Architecture
53
54. @BiancaJiang @GinnyGhezzo #oreillysacon #devops
Resources
● Jazz.net - https://jazz.net/
● IBM DevOps - http://www.ibm.com/ibm/devops/us/en/
● Bianca Blog - https://jazz.net/blog/index.php/2014/06/27/devops-for-clm-
maintenance-1/
● Working Like a Startup - http://radar.oreilly.com/2014/09/working-like-a-
startup-at-ibm.html
● IBM Support Lifecycle - http://www-01.ibm.
com/software/support/lifecycle/lc-policy.html
● Enterprise DevOps Best Practices for Executives - https://ibm.
biz/BestPracticesExec
● Inspirational Leadership TED talk -
http://www.ted.com/talks/simon_sinek_how_great_leaders_inspire_action
54