We overload our terms a lot in this industry. "Coupling" is one such. That word covers situations ranging from essential to accidental to comical to cosmic. Coupling seems to be the root of all ills. It is the molasses that slows our every move. And yet, in the industry from which we borrowed the term, "coupling" was not a dirty word. It meant something ingenious. Let us contemplate coupling for a time and see what we can do about it.

 
 

Target Audience

Developers, Technical leads and Architects,programmers, testers, business analysts and product owners,programmers, testers, business analysts and product owners

schedule Submitted 10 months ago

Public Feedback

comment Suggest improvements to the Author

  • 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.

  • 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.

  • Saiful Nasir
    keyboard_arrow_down

    Saiful Nasir - 10 lessons about agile from a non-agile person

    45 Mins
    Talk
    Intermediate

    As a leader, I'm always looking for new ways to improve the way I lead, the way our projects are run, and the way I can optimise our business. When agile was introduced into a more mainstream business audience, I was one of them - I saw the potential for the values and principles to work for all types of businesses, not just software development.

    Since then many years have passed and after being exposed to and in the bowels of all forms of agile mindsets converted into approaches (e.g. Scrum, SAFE, etc.), I've learnt a few things - some good and some bad. I've distilled it to 10 lessons I've learnt about agile, all coming from a non-agile practitioner.

  • Michael Nygard
    keyboard_arrow_down

    Michael Nygard - Grinding the Monolith

    45 Mins
    Talk
    Intermediate

    Microservices sound appealing, but what can we do with those ten-million-line code bases? Shared domain objects, horizontal coupling, and years of boundary erosion have left us with enormous complexity and spiderwebs of coupling. Michael will share techniques at various levels of abstraction, from implementation details to API design and responsibility allocation. There’s no silver bullet that will make it easy to decompose a monolith, but you’ll learn some techniques that have helped and some pitfalls to avoid, all based on Michael's experience with both successful and failed transformations.