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.

  • Liked Vilas Veeraraghavan
    keyboard_arrow_down

    Vilas Veeraraghavan - Walmart's Continuous Deployment Journey using Concord - Delving into the successes, failures and learnings

    45 Mins
    Case Study
    Intermediate

    This talk will focus on Walmart’s home-grown open sourced solution for all workflow orchestration needs - "Concord". We will discuss the extremely rewarding continuous deployment journey that we undertook at Walmart that led us down the path of creating Concord. We will dissect some key successful case studies that Concord helped us solve at Walmart scale. In addition, we will talk about the various challenges we faced and continue to face during our journey and how the fast-changing industry landscape (with respect to continuous delivery of software) influences our growth inside Walmart.

    You will be able to understand:

    • How we deal with challenges at Walmart scale
    • Why we chose to open source our solution
    • How we enable a complete CD cycle using Concord
    • How Concord empowers deployments in a hybrid cloud model
  • 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 Danny Kovatch
    keyboard_arrow_down

    Danny Kovatch - The new era of the Scrum master

    Danny Kovatch
    Danny Kovatch
    Chief Borders Removal
    Ajimeh
    schedule 1 week ago
    Sold Out!
    45 Mins
    Talk
    Advanced

    When the concept of a Scrum master was introduced to the world, it was way too far to digest. Having a coach to a team was a new time that hardly anyone could understand how to implement in a technical world. Even going back one step for being a trainer who train the team was a mission that not all the companies and the team could understand its benefits, so another one step backward was needed to be done to a facilitator. Along the time , more and more teams became more Agile mature hence the role of a Scrum master could have been gained into the right direction to again become the coach of the team.

    If you are frustrated as a Scrum master how to motivate your team, have rare idea how to motivate your team , have no idea what are motivational buttons or are not fabulist with the term intrinsic motivation, the Scrum meetings are considered to be a big waste and you have no clue how to reach the vision (doing nothing while the team is fully self managed), this session was created for you.

  • 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 2 months 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 2 months 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 2 months 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 months 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 months 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 4 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 Anna Obukhova
    keyboard_arrow_down

    Anna Obukhova - Biology of Agile Leader

    Anna Obukhova
    Anna Obukhova
    Agile Coach
    ScrumTrek
    schedule 3 months ago
    Sold Out!
    45 Mins
    Tutorial
    Intermediate

    Agile Leadership has its unique flavour of natural leadership, when power is not given with a title but taken by a person based on his/her inner abilities. We use Servant Leadership or Powerless Leader to emphasise this difference. If we look deeper into the biology and neuroscience of leadership we might find really unexpected things – that Agile leaders are the ones that are recognised by nature and we unconsciously can select these people from the crowd. How to become this type of person?

    To be an effective Agile leader we need to understand:

    • What makes a leader: Leader-Leader Agile Model

    • The difference between a leader and dominant behaviour, why leaders look younger and more active (on hormonal level)

    • Hormones and neuroscience of a natural leader (with some cases and practice)

    • Leadership differences and similarities of Scrum Master and Product Owner

    • Simple (4 words) yet powerful mindset change to become a natural leader that people will follow

  • Liked Anna Obukhova
    keyboard_arrow_down

    Anna Obukhova - Neuroscience for Product Owners

    Anna Obukhova
    Anna Obukhova
    Agile Coach
    ScrumTrek
    schedule 3 months ago
    Sold Out!
    45 Mins
    Tutorial
    Intermediate

    We usually underestimate how difficult the Product Manager or Product Owner role is. If we think about how much energy and how much brain they need to be able to generate creative ideas, be full of insights and handle market feedback – this is definitely the hardest role ever. Hopefully we have research in neuroscience that helps to understand how insights happen, how to improve decision making and how not to fall into confirmation bias (and some other biases that spoil how clear we see the situation). This talk will share ideas and tools that will help Product Managers to create even better products and keep brain fresh and creative.

  • Liked Dana Pylayeva
    keyboard_arrow_down

    Dana Pylayeva - Journey without fear. Leading your teams to high-performance.

    45 Mins
    Workshop
    Executive
    Psychological Safety has been identified as a #1 condition for creating high-performing teams by Google’s Project Aristotle. Yet, many organizations today find themselves being affected by fear in the workplace. It manifests itself in employee's disengagement, lack of innovation and toxic working environments.
    How can we start taking the first steps away from the culture of fear and towards a culture of psychological safety?
    Join this interactive session to experiment with a new "Fear in the Workplace" and "Safety in the Workplace" games (designed by the speaker) and start these difficult conversations in a fun way. Discover a number of safety enhancers that can help you, your teams and your organization on this journey.
    Highly experiential, this session is designed with elements of Training from the Back of the Room and brings together “tried and true” practices from the years of coaching teams in US, Canada, Ireland and Japan.
    Join in to learn by doing and bring back a set of practices designed to significantly improve psychological safety in teams and organizations.

  • Liked Angie Doyle
    keyboard_arrow_down

    Angie Doyle / Talia Lancaster - 3... 2... 1... We have Sprint-Off

    90 Mins
    Workshop
    Beginner

    Getting new teams to work together is hard. Really. Hard.

    Is it because there is so much hype around new Agile teams? Or is it because there is such a focus on “doing things right” (or “doing” Agile right), that we forget about the people actually doing the work? Regardless of the reason, before we can change the way people work... we need to focus on the things that are important for teamwork to work!

    We believe that the key to high-performance teams is creating an intentional culture that respects and embraces diversity - whether it be race, gender, class, culture, age, beliefs, language, skills or background. So join us as we explore the Team Canvas – sort of like a Business Model Canvas for teamwork - covering nine essential teamwork elements:

    • Purpose - Why we are doing what we are doing?
    • People & Roles - What are our names, roles, and responsibilities?
    • Common goals - What do we as a group want to achieve together?
    • Personal goals - What do I as an individual want to achieve?
    • Team values - What do we really stand for and believe in?
    • Needs and expectations - What do each of us need to be successful in a diverse team?
    • Rules & Activities - How do we communicate and keep everyone up to date?
    • Strengths & Assets - What skills do we have in the team?
    • Weaknesses & Risks - What are the weaknesses we have, as an individual and as a team?

    During this session, we walk through our agenda for team lift-offs, facilitation posters and preparation work required, materials needed, and facilitation tips and tricks. All packaged in a handy pocket guide, that you can use to explore tried and tested techniques for each essential element. You also have an opportunity to practice some of these techniques during the session.

    Get ready to lift-off your team in T-minus 3... 2... 1...

  • Liked Katy Sherman
    keyboard_arrow_down

    Katy Sherman - Agile in Legacy Apps - Mission Impossible?

    20 Mins
    Experience Report
    Beginner

    How many times did you hear: legacy systems are not a good fit for Agile transformation? Have you ever said it yourself? I want to tell you a story of a digital transformation in Premier to prove you wrong. Agile is not only a great fit for the legacy applications, it an absolute business necessity, because how else can you provide incremental value for hundreds or thousands of users through a flexible adjustable roadmap?

    My story is not going to be about an immediate success. We've had our fair share of problems, challenges, and small failures. "Legacy" means "old". It means - outdated technology stack, messy dependencies, code that nobody understands, manual testing, manual builds, manual deployments, redundant features. Also, customer issues, bugs, performance issues, scalabiity concerns. Wait, did I mention dependencies?

    Come to the session if any of this sounds familiar, if you're afraid of starting the Agile transformation, or if your company already went through a number of initiatives but the old habits die hard. I will share the valuable lessons we've learned from our experience, the strategies to apply to make the changes stick, as well as the anti-patterns to watch for.

  • Liked Anjali D leon
    keyboard_arrow_down

    Anjali D leon - Careers in the Age of Accelerations: A Well Crafted Roadmap or A Drunkard’s Walk?

    45 Mins
    Tutorial
    Intermediate

    The rules of the game have changed! Studies indicate that by the year 2030, half of jobs will be ones that do no exist today and half the jobs of today will no longer exist. The volatility, uncertainty, and ambiguity ushered in by this age of accelerations extends not just to our environment, politics, and communities, but our organizations as well. In response, organizations are undergoing a massive transformation in technology, structure, culture, and values - fundamentally changing not only what we work on, but how we work, and who we work with.

    Where does this leave our careers? If answering the question ‘Where do you see yourself five years from now?’ leaves you stuck, uncertain, confused and/or anxious, you are not alone.

    Join me for “Careers in the Agile of Accelerations”. During this workshop, we will look back at your career and look ahead at organizational and cultural trends, and understand the skills and capabilities for new and emerging roles. Build the awareness and confidence to take control and navigate a career aligned to the future of work and guided by your Ikigai (reason for being).

  • Liked Angie Doyle
    keyboard_arrow_down

    Angie Doyle / Talia Lancaster - "Boredroom" games and how to play them SMARTER

    90 Mins
    Workshop
    Beginner
    • Are your strategy workshops held in a boredroom, instead of a boardroom?
    • Does your workshop format inject new techniques to keep things interesting?
    • Have you considered that you might be introducing too many new concepts? Rather than meeting your attendees where they are?

    We see something interesting happening in the world of Agile facilitation. Techniques created many years ago are deemed to be “old-fashioned” or "traditional”! And unfortunately, this way of thinking could be alienating people that have relied on these techniques for many years. The same people who we so badly need to adopt a different way of thinking - Executives!

    It’s time to re-think the way we look at “old-fashioned” techniques – and find a way to reconnect with why they were created in the first place.

    In this session, we take you through how we help Executives make SMART goals smart, by playing a board game. The outcome of the game is a clearly stated goal that can be converted into metrics against which a team can track their success. We also provide you with all the resource to run your own SMARTER boardgame back at the office.

    Join us as we create SMARTER team metrics, by asking the rights questions – and having some fun along the way.