filter_list help_outline
  • Liked Dave Snowden
    keyboard_arrow_down

    Dave Snowden - Is Mindset yet another agile buzzword?

    45 Mins
    Keynote
    Executive

    While it is true to say that people’s attitudes and beliefs are key to implementing an agile project, or Agile in itself, much of the use of the term ‘mindset’ implies a mental model that can be defined and engineered. In this presentation, we will look at how we can measure attitudes within an organization and use multiple small actions to trigger the rapid evolution of organizational culture, so that it can sustain agile developments. Mindset and the alignment-based ideas of some on the Agile movement too often imply creating homogeneous beliefs and values that will lead to full alignment. In practice, this damages resilience and can be dangerous. This presentation will introduce the idea of coherence instead of alignment - the celebration of cognitive and behavioral differences that can align if needed to support the delivery of sustainable solutions.

  • Liked Vilas Veeraraghavan
    keyboard_arrow_down

    Vilas Veeraraghavan - Measuring the cost and tracking the effectiveness of a high-impact Chaos Engineering program

    45 Mins
    Case Study
    Beginner

    The practice of Chaos Engineering has established the importance of running resiliency experiments in cloud-native application ecosystems. As the field of Chaos/Resilience Engineering has matured and attained widespread adoption, a need has emerged for engineering organizations to quantify the costs of running such a program. Additionally, sustained investment in any long-running program will require metrics (KPIs) to show effectiveness to Executive Leadership.

    In this talk, we will discuss the setup, running and maintenance stages of a high performing Chaos/Resilience engineering program irrespective of the size of the organization. We will analyze the key metrics that should be tracked along with the optimum cadence of chaos exercises. Also, with the rapid advancement of CI/CD tools and cloud deployment technologies, we look at enhancing the impact of chaos engineering by deep integration into the continuous deployment pipeline.

  • 480 Mins
    Workshop
    Advanced

    n this one-day Workshop, Dave Snowden, the creator of the Cynefin framework and famous in the agile community as an inspiring and sometimes controversial speaker, will address agility from the point of view of complexity. Participants will be exposed to a realistic approach that puts context before dogma and shows a future for Agile that goes beyond fighting over methods and towards a sophisticated application of agility in organizations.

    This class will offer an introduction to the Cynefin framework by its creator: the Cynefin framework is a transformational idea that uses a situation-specific approach to making sense of the world in order to act in it, and ensures effective work, decision making, and management even in complex and uncertain environments. For Agile practitioners, this framework supports effectively tailoring methods and practices to different situations. Cynefin-informed methods and practices help Agile organizations harness change and turn complex situations into a competitive advantage for customers and the business.

  • Liked Adam Tornhill
    keyboard_arrow_down

    Adam Tornhill - Manage Technical Debt in Microservices and Monoliths

    Adam Tornhill
    Adam Tornhill
    Author
    Software Design X-Rays
    schedule 1 week ago
    Sold Out!
    480 Mins
    Workshop
    Intermediate

    Many codebases contain code that is overly complicated, hard to understand, and hence expensive to change and evolve. Prioritizing the technical debt to pay down is a hard problem since there's always a trade-off between improving existing code versus adding new features. In this masterclass, you learn how easily accessible development data let us uncover the technical debt with the highest business impact. The techniques cover both technical and organizational decisions around your codebase, and we cover both traditional architectures as well as microservice architectures where you learn to measure non-code properties like team coupling, system mastery, and detect implicit dependencies between services.

    • Identify the code that's most expensive to maintain amongst millions of lines of code.
    • Put costs on technical debt and assess its delivery impact.
    • Detect architectural decay and learn to control it.
    • Perform architectural analyses of layers and microservices to uncover team coupling and implicit dependencies.
    • Learn refactoring patterns to address technical- and architectural debt.
    • Measure how organizational patterns influence code quality and the link to software architecture.
    • Uncover the social side of your codebase and use data to mitigate off-boarding risks.

    Participants are encouraged to take this opportunity and analyze their own codebases. As part of the workshop, you also get access to CodeScene – a tool that automates the analyses – which we use for the practical exercises. We also look at open-source alternatives, and see how we can use Git itself for data mining; the workshop is not about tools, but rather about the techniques and their applications. This is a new perspective on software development that will change how you view code.

  • Liked Lyndsay Prewer
    keyboard_arrow_down

    Lyndsay Prewer - Embracing collaborative chaos - running Chaos Days on large platforms

    45 Mins
    Case Study
    Intermediate

    Today’s systems are inherently complex, with some component parts often operating in or close to suboptimal or failure modes. Left unchecked, as complexity increases, the compounding of failure modes will inevitably lead to catastrophic system failure. Chaos Days help us address this risk by spending time deliberately inducing failures, then analysing the response.This session summarises our experience of running Chaos Days on a large scale platform. We’ll explore the what, why, how and when of running a Chaos Day.

    As engineers we spend a lot of our time thinking about how best to shield our clients and customers from the risks inherent in the systems we build. We ask ourselves “what’s the worst that could happen?” – and work hard to mitigate the risk. A common risk in most systems, particularly distributed ones, is the unexpected failure of a component part. As a system’s complexity and its number of subsystems grows, so does the likelihood of a subsystem failure. Subsystem failures can compound in such a manner that catastrophic system failure becomes a certainty. The only uncertainty is when the system will fail.

    Chaos Engineering addresses the risks inherent in distributed systems that stem from unexpected component failure. It does so by running experiments that explore the impact of sub-system failures by deliberately inducing different types of failure in different components. Outcomes are then analysed and learnings applied to improve the system’s resilience. These learnings deepen our understanding of the system and its failure modes, which aids the identification of new failure scenarios. This feedback loop informs subsequent rounds of experimentation, and thus the cycle repeats. In addition, planned failures provide a safe environment for teams to improve their incident response and how they conduct subsequent postmortems.

    Chaos experiments can take many forms, ranging from continuous, automated failure injection (made famous by the Netflix Chaos Monkey), to one off Chaos Days (similar to Amazon’s Game Day), where disruption is manually instigated. Chaos engineering is similar to the ethos of “building quality in”: it’s a mindset, not a toolset: you don’t need to be running EKS on AWS to benefit from being curious about failure modes and how to improve a system’s resilience towards them. It just requires a focus on “building resilience in”.

    This session shares our experience of running Chaos Days over the last year, with one of our clients – a major Government department that hosts around 60 distributed, digital delivery teams. These teams design, deliver and support hundreds of microservices that serve online content to the department’s varied customers.

    The microservices all run on a single platform, itself run by seven Platform Teams that take responsibility for distinct areas (infrastructure, security and so on). Inspired by the Netflix Chaos Monkey and Amazon’s Game Day, the Platform Teams have planned and executed several Chaos Days – to see just how well they and the Platform coped when everything that could go wrong, does go wrong.

  • Liked Subbu Allamaraju
    keyboard_arrow_down

    Subbu Allamaraju - Finding Your Middle

    Subbu Allamaraju
    Subbu Allamaraju
    Vice President
    Expedia Group
    schedule 1 week ago
    Sold Out!
    45 Mins
    Case Study
    Intermediate

    As organizations break barriers between dev and ops, are we entering a new era of another extreme? In this extreme, every team owns their service from dev to ops, and introducing central teams for shared activities is considered as an anti-pattern. Is that so? Is there a role for centralization? How should you structure your teams to get be best possible outcomes? What guardrails should you consider? Based on real-world experience dealing with operations at large organizations, in this talk, you will find answers to find your middle ground.

  • Liked Subbu Allamaraju
    keyboard_arrow_down

    Subbu Allamaraju - The Surprise Factor

    Subbu Allamaraju
    Subbu Allamaraju
    Vice President
    Expedia Group
    schedule 1 week ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Regardless of how well your org might have adopted DevOps culture and practices, your dev teams are likely spending a majority of their time planning for creating new things, adding features to existing products, or "replatforming" to take advantage of contemporary approaches. All these activities are centered around the "as intended" state of your systems. Consequently, you get surprised and frustrated when things don’t go well in production. How do you balance between the "as intended" and "as it is" (production) states? What does the "as it is" has to offer? Why and how to turn production surprises into opportunities? Join this session to find answers.

  • Liked Adam Tornhill
    keyboard_arrow_down

    Adam Tornhill - Meet The Social Side of Your Architecture

    Adam Tornhill
    Adam Tornhill
    Author
    Software Design X-Rays
    schedule 2 weeks ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Software projects often mistake organizational problems for technical issues and treat the symptoms instead of the root cause. The main reason is that the organization that builds the system is invisible in our code. From code alone, we cannot tell if a module is a productivity bottleneck for five different teams, or whether our microservice boundaries support the way our codebase evolves or not. This session closes that gap by taking a behavioral view of code combined with insights from social psychology to measure aspects of software development that we haven't been able to capture before. You learn how this information lets you detect modules with excess coordination needs, measure how well your architecture supports your organization, as well as why Conway's law is an oversimplification. To make it specific, each point is illustrated with a case study from a real-world codebase.

  • Liked Adam Tornhill
    keyboard_arrow_down

    Adam Tornhill - A Crystal Ball to Prioritize Technical Debt

    Adam Tornhill
    Adam Tornhill
    Author
    Software Design X-Rays
    schedule 2 weeks ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    The technical debt metaphor has taken the software world with storm. No wonder, since software projects have their fair share of challenges. Most organizations find it hard to prioritize and repay their technical debt. The main reason is due to the scale of modern systems with million lines of code and multiple development teams; No one has a holistic overview. So what if we could mine the collective intelligence of all contributing programmers and start to make decisions based on data from how the organization actually works with the code? This session introduces one such approach with the potential to change how we view software systems.

    In this session, you'll get an introduction to techniques that help us uncover both problematic code as well as the social dimension of the teams that build your software. The techniques are based on software evolution and findings from various fields within psychology. This combination lets you prioritize the parts of your system that benefit the most from improvements, detect organizational issues and make practical decisions guided by data. Each point is illustrated with a case study from a real-world codebase.

  • Liked Renesh Moodley
    keyboard_arrow_down

    Renesh Moodley - Devops = Culture + Ownership + Empowerment

    Renesh Moodley
    Renesh Moodley
    Agile Consultant
    IQ Business
    schedule 2 months ago
    Sold Out!
    90 Mins
    Workshop
    Beginner

    The three spheres of a DevOps adoption being Culture, Processes and Tools are fundamental to any organisation. The focus on tools often supersedes any work being done at the process levels and almost always, the culture aspect is 'ignored'. Through my years of helping teams adopt agile and eventually pursue DevOps, I've identified certain patterns that address the varying levels of change that are needed by a team pursuing Agile Ways of Work.

    In this talk, I'll highlight the most important patterns that are needed along with suggestions to help embed these patterns. We'll utilise Value Stream Mapping, A4 Problem Solving and Team Skill Coaching as patterns for helping a team adopt DevOps thinking. I will be using the DevOps radar (from SAFe) as a guidepost for patterns to get an organisation moving towards the promised land.

    Whilst there isn't an 'endpoint' for a DevOps adoption, these patterns reflect milestones on a DevOps transformation roadmap and serve as a possible ‘quick start’.

    NOTE: This is not. A SAFe pitch or SAFe sales workshop. The DevOps radar can be used, regardless of the presence of SAFe.

  • Liked Anand Bagmar
    keyboard_arrow_down

    Anand Bagmar - Visual Validation - The Missing Tip of the Automation Pyramid

    45 Mins
    Demonstration
    Intermediate

    The Test Automation Pyramid is not a new concept.

    Test Automation Pyramid

    The top of the pyramid is our UI / end-2-end functional tests - which simulate end-user behavior and interactions with the product-under test.

    While Automation helps validate functionality of your product, aspects of UX validations can only be seen and captured by the human eye and is hence mostly a manual activity. This is an area where AI & ML can truly help.

    With everyone wanting to be Agile, make quick releases, the look & feel / UX validation, which is a slow, and error-prone activity, quickly becomes a huge bottleneck. In addition, with any UX related issues propping up cause huge brand-value and revenue loss, may lead to social-trolling and worse - dilute your user-base.

    In this session, using numerous examples, we will explore:

    • Why Automated Visual Validation is essential to be part of your Test Strategy
    • Potential solutions / options for Automated Visual Testing, with pros & cons of each
    • How an AI-powered tool, Applitools Eyes, can solve this problem.
  • Liked Dana Pylayeva
    keyboard_arrow_down

    Dana Pylayeva - DevOps Culture Simulation (with Lego and Chocolate Game)

    90 Mins
    Workshop
    Beginner

    Organizations today can no longer afford to deliver new features to their respective markets once a year or even once a quarter. In an attempt to catch up with the competition, they jump start their DevOps journey with the "How", while losing the sight of "Why" and "What".

    Join this tutorial to gain a solid understanding of fundamental principles of the DevOps culture and avoid typical DevOps anti-patterns.

    In this gamified simulation you will become a part of a "large enterprise" and experience how DevOps will help to eliminate silos. You will experience the benefits of cross-training and start adopting systems thinking. You will participate in the debriefing with Liberating Structures and gain valuable insights that can be immediately applied in your organisation.

    The workshop is designed to be equally accessible to technical and non-technical audience alike. It bring together years of practical experience in IT, experiential learning models, elements of game design, Lego, Chocolate, and facilitation with Liberating Structures.

    Engaging, simple and powerful, this workshop is not to be missed.

  • Liked Gunnar Grosch
    keyboard_arrow_down

    Gunnar Grosch - Performing Chaos in a Serverless World

    45 Mins
    Talk
    Intermediate

    The principles of chaos engineering have been battle-tested for years using traditional infrastructure and containerized microservices, but how do they work with serverless functions and managed services? In this session we'll cover the motivations behind chaos engineering, how we perform chaos experiments, what some of the common weaknesses we can test for in our serverless applications are and run some actual experiments in a serverless environment. Join as we move from talking about principles to performing real chaos engineering experiments for serverless!

  • Liked Pramod Sadalage
    keyboard_arrow_down

    Pramod Sadalage - DevOps Practices for the Database Team

    Pramod Sadalage
    Pramod Sadalage
    Software Developer
    Thoughtworks
    schedule 2 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    This talk will focus on understanding the DevOps movement from the perspective of the database professional. We will discuss the Values, Principles, Methods, Practices, and Tools applied and provide an example of how these will affect the database teams. This talk will discuss techniques such as version control of the database, continuously integrating database changes, deploying databases changes in an automated way, automated database sandbox creation, automated database comparison, using tools such as dbdeploy, dbmaintain, liquibase, flyway, and many others. Practices for setting up development work areas and how to include the dba as a ops role into the dev team

  • 480 Mins
    Workshop
    Beginner

    The Disciplined Agile (DA) toolkit provides straightforward guidance to help organizations choose their way of working (WoW) in a context-sensitive manner, providing a solid foundation for business agility.

    DA builds on the existing proven practices from agile methods such as Scrum, Extreme Programming (XP), Lean software development, Unified Process, and Agile Modeling to include other aspects necessary for success in the enterprise. DA fills in the gaps left by mainstream methods by providing guidance on how to enable software development team to choose their WoW, how to address DevOps in an enterprise-class setting, how to apply agile and lean strategies to IT, and how to support business agility within your organization.

    Our fundamental advice is to start where you are, do the best that you can given the situation that you face, and always try to get better.

    The one-day workshop is not technical and is suitable for all team members. Many group exercises reinforce the principles learned. The workshop is also valuable for management tasked with moving from traditional approaches to agile.

  • Liked Scott Ambler
    keyboard_arrow_down

    Scott Ambler - #NoFrameworks: How We Can Take Agile Back!

    45 Mins
    Talk
    Advanced

    A fundamental philosophy from the early days of Agile, and particularly of XP, is that teams should own their process. Today we would say that they should be allowed, and better yet, enabled, to choose their own way of working (WoW).

    This was a powerful vision, but it was quickly abandoned to make way for the Agile certification gold rush. Why do the hard work of learning your craft, of improving your WoW via experimentation and learning, when you can instead become a certified master of an agile method in two days or a program consultant of a scaling framework in four? It sounds great, and certainly is great for anyone collecting the money, but 18 years after the signing of the Agile Manifesto as an industry we’re nowhere near reaching Agile’s promise. Nowhere near it.

    We had it right in the very beginning, and the lean community had it right all along – teams need to own their process, they must be enabled to choose their WoW. To do this we need to stop looking for easy answers, we must reject the simplistic solutions that the agile industrial complex wants to sell us, and most importantly recognize that we need #NoFrameworks.

  • Liked Karthik Gaekwad
    keyboard_arrow_down

    Karthik Gaekwad - 10 years of DevOps- Where are we today?

    Karthik Gaekwad
    Karthik Gaekwad
    Principal Engineer
    Oracle
    schedule 1 month ago
    Sold Out!
    20 Mins
    Talk
    Beginner

    Happy birthday, Devops- you are officially ten years old this year!!! Let’s blow out the candles on our cake, and reflect on our devops journey!

    This session will cover the evolution of devops over the past ten years, and talk about the initial idea, the growth of devops, to the state of the world today! You will leave with an understanding of the different successes that it has provided for organizations, the challenges that devops faces today, and where devops might be in another ten years.

  • Liked Shama Ugale
    keyboard_arrow_down

    Shama Ugale - Testing Conversational AI - Stragegy to Automation

    Shama Ugale
    Shama Ugale
    Sr. QA Consultant
    Thoughtworks
    schedule 1 month ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    Last year was dominated by the smart devices and voice based home assistants. These use the conversational interfaces unlike other application to interact with. They are built using advanced algorithms, ranging from pattern and expression matching engines to natural language processing and AI/Machine learning techniques. These systems are constantly learning by themselves improving the interactions with the user bringing up the challenge in the testing world of non-deterministic output. To such interfaces, natural language is the input and we humans really love having alternatives and love our synonyms and our expressions using emojis gifs and pictures. Testing in this context moves to clouds of probabilities.

    In this session I will cover the strategy for testing such interfaces, testing the NLP models and sharing experience on how to automate these tests and add it to the CI/CD build pipelines.


    Key learning:
    * How What and why of a conversational interface?
    * How can I build my testing approach for such an interface?
    * What from my current tool set can I use for this new context?
    * How do I automated and add it for my CI/CD pipeline for instant feedback?
    * How do I measure the quality?

  • Liked Nikhil Barthwal
    keyboard_arrow_down

    Nikhil Barthwal - Managing Modern Serverless Workloads Using Knative & Cloud Run

    Nikhil Barthwal
    Nikhil Barthwal
    Product Manager
    Google
    schedule 1 month ago
    Sold Out!
    45 Mins
    Talk
    Advanced

    This introduces Knative & Cloud Run and shows how they can be used to run modern serverless workloads. Knative is a reference API &
    implementation and Cloud Run is a product built on the Knative specification.

    Knative is a Kubernetes-based platform to build, deploy, and manage modern serverless workloads. It provides a set of middleware
    components that are essential to build modern, source-centric, and container-based applications. Knative components are built on
    Kubernetes and codify the best practices shared by successful real-world Kubernetes-based frameworks.

    Cloud Run is a managed compute platform that is built upon Knative that automatically scales your stateless containers. Cloud Run
    is serverless: it abstracts away all infrastructure management. It is compatible with Knative, letting you choose to easily run
    your containers either fully managed with Cloud Run, or in your Google Kubernetes Engine cluster with Cloud Run on GKE.

  • Liked Aaron Rinehart
    keyboard_arrow_down

    Aaron Rinehart - Security & Chaos Engineering: A Novel Approach to Crafting Secure and Resilient Distributed Systems

    Aaron Rinehart
    Aaron Rinehart
    CTO Founder
    Verica
    schedule 1 month ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Modern systems pose a number of thorny challenges and securing the transformation from legacy monolithic systems to distributed systems demands a change in mindset and engineering toolkit. The security engineering toolkit is unfortunately out-of-style and outdated with today's approach to building, security and operating distributed systems. The speed, scale, and complex operations within microservice architectures make them tremendously difficult for humans to mentally model their behavior. If the latter is even remotely true how is it possible to adequately secure services that are not even fully comprehended by the engineering teams that built them. Security Chaos Engineering helps teams realign the actual state of operational security as well as build confidence that their security actually works the way the think it does. Chaos Engineering allows for security teams to proactively experiment on recurring incident patterns to derive new information about underlying factors that were previously unknown by reversing the postmortem and preparation phases. This is done by developing live fire exercises that can be measured, managed, and automated. It develops teams by building a learning culture around system failure to challenge engineering teams to proactively, safely discover system weakness before they disrupt business outcomes. In this session we will introduce a new concept known as Security Chaos Engineering and how it can be applied to create highly secure, performant, and resilient distributed systems.