Roundtable 15: Achieving compliance might be challenging when embracing DevOps due to the rapid pace of development. However, the agility and automation associated with DevOps might actually simplify compliance. When integrating compliance into the SDLC, DevOps teams may have to use different tools or slightly modify part of their processes to adapt to specific requirements.
Roundtable 14: Across all industries, software is vital for companies’ interactions with their customers, suppliers, partners, and employees. The imperative for software quality is taking on even greater importance with the movement to cloud computing, requiring more modular and dynamic approaches to software development and deployment. Increasingly, organizations are building cloud-native applications utilizing microservices and containers. But is testing still considered the bottleneck to delivering software in the era of DevOps?
Roundtable 13: Site reliability engineering (SRE) and DevOps have a unified goal of combining development and IT operations teams to introduce visibility and to create scalable and highly reliable software systems. While DevOps focuses on what needs to be done, SRE looks for ways to accomplish it.
Roundtable 12: Healthcare, financial and governmental organizations are common targets for cyberattacks, making proper security guardrails and implementing the right compliance strategies critical for these highly regulated industries. Entities functioning in highly regulated environments can benefit from implementing DevOps while also adopting strategies that help them meet challenging regulations and policies.
Roundtable 11: Continuous integration (CI) and continuous delivery (CD) are scalable software development practices for automation and shortening feedback times. With a CI/CD pipeline you can identify vulnerabilities and errors earlier in the SDLC, reduce the amount of potential risk and improve the quality of your software. However, as the tech landscape is constantly and rapidly changing, it’s difficult to keep up with the constant evolution around CI/CD.
Roundtable 10: As part of their digital transformation, businesses have been adopting cloud-native technologies to drive innovation, resilience and agility. Cloud-native application development has helped organizations stay ahead by delivering faster time to market, achieving greater flexibility, scalability and cost effectiveness. However, the growth in cloud computing has also presented new testing challenges for DevOps teams. Traditional testing methodologies aren’t enough to address security holistically for cloud-native apps.
Roundtable 9: Every period of significant economic, market or technology disruption creates winners and losers, but the reality for businesses is more nuanced than those binary outcomes. Those who survive, and even thrive, successfully escape the event horizon of disruption, creating innovative new business, product and operational models. They also leverage and harness technology in new and innovative ways through digital transformation. Not escaping the event horizon leaves companies who languish in survival mode, or worse.
Roundtable 8: DevOps is all about people, process and tools. People, or humans, are critical to DevOps success. Just as we invest in tools and build processes, software leaders recognize it is vital to invest in DevOps skills for their people and software teams.
Roundtable 7: Much of what we think of as DevOps is happening now within GitOps. Example: Testing happening from GitOps then directly deploying with Kubernetes, vs the typical DevOps CI/CD pipeline workflow. Is GitOps the next stepping stone from DevOps? Will organizations go directly to GitOps? What does this mean for organizations working to implement CI/CD? Our panel of experts explore GitOps and its impact on DevOps.
Roundtable 6: The SolarWinds and FireEye compromise demonstrated the devastating effectiveness of a supply chain cybersecurity attack leading to the infiltration of government and corporate networks by a nation-state actor. It’s not “just” a security issue. The impact and response will alter application delivery far beyond the traditional boundaries of security.
Roundtable 5: Most enterprises are either contemplating or have already begun their DevOps adoption/digital transformation, but once started, the next logical question is “What’s next?” DevOps success begins with success on a few software teams, expanding to more teams, leading to dreams of adoption by the larger organization. Welcome to Day 2 DevOps, now…what’s next?
Roundtable 4: Testing is routinely cited as the number one source of DevOps delays — and defects are still a major issue for 48% of DevOps teams. Are we approaching testing the wrong way? Have we failed to scale and/or accelerate it properly for enterprise DevOps? Do we need to rethink our overall testing objectives, or do we just need to find better ways of achieving them?
Roundtable 3: Anyone who’s frightened by the ghouls, goblins and demons of Halloween has obviously never been in the depths of a DevOps initiative. Even the most successful projects can’t escape the scares that inevitably arise when you fundamentally transform—and continuously optimize—culture, processes and technologies. The troubles terrorizing new and less mature DevOps initiatives can be downright ghastly.
Roundtable 2: SAP and DevOps were born of distinctly different worlds, but those two worlds have now collided. The SAP core, an organization’s SAP customizations, and all the connected applications are growing inextricably intertwined as SAP plays a larger role in digital transformation. What’s needed to make SAP a successful—and integral—part of the DevOps culture and CI/CD pipelines?
Roundtable 1: We won’t bore you with all the reasons DevOps requires alignment across business, development, testing, security, and of course operations. That’s established. But the real question is how to coordinate all these elements at the enterprise level—beyond the high-performing DevOps native teams and across the ones with vastly different cultures, application stacks, and compliance requirements.