Agile + DevOps West 2023 - Continuous Integration/ Continuous Delivery
Tuesday, June 6
Agile Project Failures: Root Causes and Corrective Actions
Agile initiatives always begin with high expectations—accelerate delivery, meet customer needs, and improve software quality. The truth is that many agile projects do not deliver on some or all of these expectations. If you want help to ensure the success of your agile project or to get an agile project back on track, this tutorial is for you. Jeffery Payne discusses the most common causes of agile project failure and how you can avoid these issues or mitigate their damaging effects. Poor project management, ineffective requirements development, failed communications, software development...
Approaching Conflict Productively
NewWhen it comes to high-performing teams, conflict is inevitable and necessary. The very essence of gaining the best value outcomes is a result of leveraging the wisdom of various perspectives and experiences. Those variances will generate conflict. Yet, this is only a negative if we are unequipped with the knowledge and tools to embrace and approach conflict. In this tutorial, expect to unpack the differences and the relationship between conflict and drama. Discover tools for helping all voices be heard. Plus, have fun practicing skills in preparing how to react to conflicts productively...
What DevOps Means for Testers and Testing
DevOps is more than a buzzword or a passing fad. It's a radically new approach to rapidly deliver high-quality software applications. However, many organizations don’t fully grasp the magnitude of this change or what it means for everyone involved in the software development lifecycle. Jeffery Payne says that DevOps—when done right—drives higher quality and efficiency into software development, software testing, and application management activities. It empowers teams to remove impediments to quality and productivity throughout the entire software lifecycle. However, when DevOps is done...
Wednesday, June 7
.jpg%3Fitok=owdvb9yS&sc=99410af1980838bc65014bc2b12db659)
The Art of Defensive Programming
With every commit, the threat landscape increases. One single vulnerability is all a hacker needs. Vulnerabilities have multiple sources, and you must have a plan for securing each potential risk vector and identify vulnerabilities early. In this session, we will describe defensive coding techniques you can use as a daily practice and how you can build a security champion program. We will practically cover ways of identifying security vulnerabilities in your IDE using CodeQL as a Static Code Analysis tool. This is an important step in the pre-commit stage to identify security...
Reimagining Digital Cloud Transformation: Automation and DevOps Pipeline
Organizations face numerous challenges during their journey to Digital Cloud Transformation—the most pressing challenges are frequent failures and the absence of a “big-picture” mindset. Driven by KPMG’s quest to deliver a superior customer experience, their Digital Cloud Transformation framework delivers improved quality, reduced time to market, reliability, and sustainable Cloud Transformation. Moving away from the archaic approach from replicating traditional regression onto cloud integration validations, KPMG has helped customers minimize risk and increase test coverage by E2E...
You Want to Test What in the Build Pipeline? How to Move Integration, E2E, and Other Large Tests Reliably into the CI/CD Pipeline
Testing automation has a reputation for being slow and unreliable, but automated tests which are not run as a part of the CI/CD pipeline are often ignored or written off when they don't pass. If nobody pays attention to the results though, automated tests are not very useful. Any tests which depend on another system will eventually break, unless special care is taken, keeping the addition of integration (or larger) tests to the build pipeline just out of reach. During this session, John Jenkins will show attendees how these larger tests can be reliably automated, so that these tests can be...
Thursday, June 8
Why Kubernetes Applications Require a New Approach to Testing Using Testkube
Microservices, CI/CD, DevOps, GitOps, cluster networking, etc.—more and more teams are building software fundamentally differently than they did even a few years ago. However, testing approaches and tooling have not caught up yet. At least not until now. What if you could apply the same type of GitOps and DevOps methodologies to your testing activities? Tests could be deployed and stored in a Kubernetes cluster, they could be decoupled from your CI/CD, orchestrated in the cluster in the same way you do with your applications and not in your CI/CD, publish results aggregated in a common...
A Test Automation Workflow for Mobile Software That Actually Works
The vision is shared amongst many engineering and quality teams: we’re going to automate our testing end to end and integrate it seamlessly into our CI/CD pipeline. It sounds beautiful and efficient. And for much of your software testing infrastructure, you’re probably making it happen! Then reality hits hard as soon as you deploy the latest release of your mobile app. You don’t have control over the third-party devices or SDKs your app depends on, or the universe of operating systems users actually use. If you care about quality, and you want complete coverage for your mobile app, it isn’...
Continuous Build and Other DevOps Anti-Patterns and How to Overcome Them
Software development is hard and poorly implemented or broken tools, techniques, and patterns just make it worse. Learn to spot DevOps anti-patterns and how to work your way back to a sane way of working. Continuous Build is an anti-pattern that Tom Stiehm has seen often, where a team will have what they call Continuous Integration (CI) in place, but it only builds the code. There are no unit tests or static analysis run. Certainly, this is better than not building, but it leaves a lot of health check information on the table that is considered part of CI. Without this information, you can...
A Journey in Improving Test Pipeline Stability
Building automated tests is only the first step. The true challenge is building them with high enough reliability that they can be run as part of a deployment pipeline. But understanding how to get to that point is hard, and getting to that point often seems unsurmountable. This session will focus on exactly how Olo went from having a few hundred tests being triggered manually, to having thousands of tests running as part of a deployment pipeline. Brian Kitchener will give concrete examples of what tools were used at each step of the process, what challenges were faced, what tools needed...