Pre-Conf Workshop

Mon, Mar 16
09:30

    Registration - 30 mins

10:00
  • schedule  10:00 AM - 06:00 PM place Magnolia people 32 Interested

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

  • Added to My Schedule
    keyboard_arrow_down
    Jutta Eckstein

    Jutta Eckstein / John Buck - Beyond KPIs and OKRs: Creating an environment for high-performing, innovative teams that leads to true effectiveness

    schedule  10:00 AM - 06:00 PM place Plumeria people 21 Interested

    Too often innovative people in medium to large organizations have the feeling of being in a box - with startling new ideas - and no one really listens. In essence, these innovators are trying to “measure performance upwards.” This upward voice intrinsically measures strategies and customer impact, and applying the concept can significantly improve the overall performance without relying on top down OKRs and KPIs. Moreover, “measuring from above,” tends to measure the output of production rather than the truly important outcome: what is really making a difference for our customers and therefore for our company.

    Adding “measurement from below” to a company can create a mindset that empowers everyone to follow their passion and interest and nourish the company’s effectiveness. Implementing a “from below” approach to measurement involves a fundamental shift that asks the company to synthesize a variety of new approaches. One such synthesis is Beyond Budgeting, Open Space, Sociocracy, and Agile (BOSSA nova). This synthesis enables a company to “measure upwards” without jeopardizing the strengths of “leading downwards.” Fortunately, the implementation can be done in small steps that probe and demonstrate new measurement ideas on a small scale such that the proof cascades beyond the demonstration. This session will enable you to get started on your journey to spreading the idea of upwards measurement company-wide.

    This workshop asks participants to start where they are, explains what it means to probe, and helps them develop strategies and experiments they can use in their own situation to create an environment for high performance that goes beyond what OKRs and KPIs can offer.

  • Added to My Schedule
    keyboard_arrow_down
    Tony Morris

    Tony Morris - Functional Programming Deep-Dive with Types and Property-Based Testing

    schedule  10:00 AM - 06:00 PM place Jacaranda people 6 Interested

    This workshop will first introduce Functional Programming concepts using the Haskell programming language syntax and tools.

    We will then present a series of exercises that utilise the static type system of Haskell and with some guidance, solve the exercises. Subsequent exercises will introduce property-based testing using the hedgehog library. Finally, we will tackle some exercises where a trade-off must be considered, and solve those using both types and property-based tests.

    The focus of this workshop will be on introducing the tools for achieving software resiliency and robustness. The techniques learned here may be applied in other programming language environments.

  • schedule  10:00 AM - 06:00 PM place Cassia people 16 Interested

    As an executive, learn how to create a culture in your Product Development Organisation that Delivers On-Time and Under-Budget, every time.

    The Problem: Even when having an Agile organisation, projects tend to deliver late and over budget. As a result, executives can not promise delivery times and meet them, and they can not set prices and ensure a profit.

    The Solution: There is now a growing group of companies that do things differently. They have learned how to deliver on-time and under-budget, every time. Maybe even more importantly, they have learned to deliver the expected improvements desired by their customers and stakeholders.

Agile Mindset

Tue, Mar 17
08:30

    Registration - 30 mins

09:00
  • Added to My Schedule
    keyboard_arrow_down
    Dave Snowden

    Dave Snowden - Is Mindset yet another agile buzzword?

    schedule  09:00 - 09:45 AM place Mysore Hall people 27 Interested

    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.

10:00

    Welcome Address & Agile Mindset Day Overview - 30 mins

10:30

    Coffee/Tea Break - 30 mins

11:00
  • Added to My Schedule
    keyboard_arrow_down
    Emily Webber

    Emily Webber - Communities of Practice: The Missing Piece of your Agile Organisation

    schedule  11:00 - 11:45 AM place Mysore Hall 1 people 14 Interested

    Connecting with other people, finding a sense of belonging and the need for support are natural human desires. Employees who don’t feel supported at work don’t stay around for long — or if they do, they quickly become unmotivated and unhappy. At a time when organizational structures are flattening and workforces are increasingly fluid, supporting and connecting people is more important than ever. This is where organizational communities of practice come in.

    Modern organizations with cross functional teams, have the ability to silo organizations into teams, programmes and functions. They can take people further away from other people that they can learn with. We need a way to bring people with the same concerns back together and this is what communities of practice do.

    Communities of practice have many valuable benefits for both individuals and organizations. They include accelerating professional development; breaking down organizational silos; enabling knowledge sharing and management; building better practice; helping to hire and retain staff; and making people happier.

    In this session, Emily will pull from experiences of building and growing communities of practice at the Government Digital Service, other government departments and organizations as well as case studies from her ongoing research into this area. You will gain an understanding of why community of practice are so important in modern organizations and practical advice to those who are thinking about setting one up or looking to reinvigorate one that already exists.

  • Added to My Schedule
    keyboard_arrow_down
    Shane Hastie

    Shane Hastie - The Ethics of Agile Coaching

    schedule  11:00 - 11:45 AM place Mysore Hall 2 people 6 Interested

    Agile Coaching is currently hit and miss – there are no guidelines and standards around what good coaching is and active harm is being done by some unethical coaches. Having a voluntary Code of Conduct will not prevent this from happening but it could raise visibility around what behaviors should be expected of a professional, ethical agile coach.

    In this interactive session Shane presents some ideas around what a Code of Conduct for Agile Coaching could be and draws from the participants areas they feel should be included in such a code.

  • Added to My Schedule
    keyboard_arrow_down
    Dana Pylayeva

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

    schedule  11:00 - 11:45 AM place Mysore Hall 3 people 6 Interested
    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.

  • Added to My Schedule
    keyboard_arrow_down
    Jakub Jurkiewicz

    Jakub Jurkiewicz - Agile Coaching Dōjō - space for deliberate practise

    schedule  11:00 AM - 12:30 PM place Magnolia people 3 Interested

    A dōjō (道場) is a hall or space for immersive learning or meditation. This is traditionally in the field of martial arts, but has been seen increasingly in other fields, such as meditation and software development (and now also Agile Coaching!).

    It will be a space for the immersive practice of coaching. Imagine a place where you can come and try out new coaching techniques, get feedback, give feedback and learn from your successes and failures? This is what coaching dōjō is about!

    Coaching is one of the four main skills of every Agile Coach (along mentoring, teaching and facilitating) and for many of us coaching is the hardest skill to master. Way too often we go back to the mentoring mode, giving pieces of advice and sharing our points of view. Guess what, asking questions and giving space to reflect and come up with actions is hard, it's extremely hard! That's why we want to create a space for deliberate practice of coaching.

    The coaching dōjō will be very to the Code Katas exercises knows from the software development world. We will come together, work in groups of 3s, one person will be a coach, one will be a coachee and one will be an observer. We will run 3 rounds of 10-15 minutes coaching so everyone will get a chance to be a coach. At the end of the round, the coach will hear feedback from the coachee and from the observer. In every session (this will be the 1st one) we will work with different challenges and/or different coaching techniques.

12:00
  • Added to My Schedule
    keyboard_arrow_down
    Anna Obukhova

    Anna Obukhova - Biology of Agile Leader

    schedule  12:00 - 12:45 PM place Mysore Hall 1 people 14 Interested

    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

  • Added to My Schedule
    keyboard_arrow_down
    David Horowitz

    David Horowitz - Stop complaining and start learning! Retrospectives that drive real change

    schedule  12:00 - 12:45 PM place Mysore Hall 2 people 16 Interested

    Good retrospectives (you know, the ones that actually lead to real change?) rest on three pillars:

    * people,
    * process, and
    * follow-through


    What makes retrospectives so difficult is that if any of these three pillars starts to crack, it's very difficult for the retrospective to be a success.

    Ultimately, getting the right people in the room, utilizing a good process to facilitate the conversation, and following-through on the learning outcomes depend on having an organizational culture that encourages learning, transparency, feedback loops, and continuous improvement.

    If this sounds like your company already, then great! This talk is not for you.

    For everyone else, join me to explore how effective retrospectives can break a downward cycle of disillusionment and malcontent and transform you and your team into engines of learning and growth.

  • Added to My Schedule
    keyboard_arrow_down
    Ralf Westphal

    Ralf Westphal - How to Overcome the Addiction to so Called "Technical Debt"

    schedule  12:00 - 12:45 PM place Mysore Hall 3 people 2 Interested

    Why is the fight against technical debt such an uphill battle? Why is it so hard to nip technical debt in the bud or at least keep it much better under control? If after so many years of the metaphor circulating around in developer circles little has changed, there seems to be an underlying unresolved issue.

    This talk is dedicated to uncovering an inconvenient truth: There is no such thing as technical debt in the first place. Hence fighting it is like fighting against non-existing windmills.

    But what about the deficient code situation the term is referring to. Isn't that all too real and painful? Yes, it sure is. But it should not be called a debt, because it does not accumulate like a financial debt which the term technical debt is alluding to. Rather it's a mess, a mess like that created by any addict.

    Managers and developers thus don't need to learn to manage just another form of debt. Instead, they need to sober up. They need to get clean. They need to recognise what's happening in everyday software development under deadline pressure as what it is: the behavior of addicts.

    In my talk, I will contrast the signature aspects of debt and addiction. It will become clear and will be supported by the audience's own experience why debt is the wrong metaphor and addiction is a much more fitting notion. And then I'll talk about interventions. How to climb out of the bottomless hole of addiction and get on the track of longterm high productivity.

12:45

    Lunch - 60 mins

01:45
  • Added to My Schedule
    keyboard_arrow_down
    Karen Ferris

    Karen Ferris - Unleash The Resiliator Within!

    schedule  01:45 - 02:30 PM place Mysore Hall 1 people 2 Interested

    When organisations are truly agile and at an enterprise level, constant and rapid change becomes the norm.

    Successful organisations need everyone to be resilient in the face of constant change.

    When everyone is resilient, great things happen. True innovation, experimentation, creativity and exploration takes place and drives organisational performance.

    How do we Unleash the Resiliator within everyone? We equip them with the superpowers to do so.

    This audience interactive presentation introduces you to the superpowers of The Believer, The Revealer, The Futurist, The Empathiser, The Regulator and many more.

    These superpowers enable the agile mindset by providing resilience in a volatile, uncertainly, complex and ambiguous world.

  • Added to My Schedule
    keyboard_arrow_down
    Oana Juncu

    Oana Juncu - Ego, Power, Fear ... and Leadership

    schedule  01:45 - 02:30 PM place Mysore Hall 2 people 3 Interested

    Wether you are an Agile Coach, an Agile transformation facilitator or a Scrum Master, did it happen to you to feel frustrated because the change you wanted to see was nat the change that was taking place? Did you ever think that the values and principles you promoted had not the desired echo? Did you ever felt the pressure to succeed a transformation, while people had other operational priorities? If you are a manager, did you feel excited by a more collaborative way of working, then felt lost because your hierarchy hase the same "old ways" type of expectations form you?

    If you ever felt this way, this session invites you to explore another path toward leadership, a path that I believe helpful either for coaches, facilitators, and managers, the path of the servant leader, who I'd rather call "leader at service".

    The challenge of a "leader at service" posture is the letting go of our own fears, our ego and eventually, our own involvement in power games, therefore we will discover together, from a systemic point of view, how our own fears may reinforce our ego and may push us in group power dynamics. The "Human Element" model created by William Schulz will be used to explore the root causes of fears and how we can address them, and Robert Greenleaf's Servant Leadership principles will be also used as a support

  • Added to My Schedule
    keyboard_arrow_down
    Craig Brown

    Craig Brown - Collaboration Deep Dive

    schedule  01:45 - 02:30 PM place Mysore Hall 3 people 3 Interested

    For the last few years, I have been diving into what Collaboration really means. I have been collecting stories and examples and discovering patterns across our industry.

    In this session, I walk the room through a Collaboration workbook where participants think about Collaboration via a series of different lenses. We will ask ourselves what collaboration means to us, and share our stories of great collaborations we have been a part of.

    I will also share aggregated data from my research and share my own insights.

  • schedule  01:45 - 02:30 PM place Magnolia people 2 Interested

    What does agile have to do with psychotherapy? It turns out quite a lot. If you think about it, ultimately agile is about working closely with people and working closely with people requires our understanding of each other. That's where psychotherapy comes in. Psychotherapy is the science and art of working well with each other, of understanding ourselves and the other person at a deeper level. I hold a masters in clinical psychotherapy (MSW) from New York University and have worked with 5000+ clients to provide coaching/advisory. As a startup founder, I also have hands on experience of applying agile methodologies at my startup. I combine all of that knowledge and experience in this interactive session to cover concepts such as empathy, self limiting beliefs and cognitive biases and how it impacts us and our teams.

    Join me for a fun session that is designed by drawing from the latest brain science research to help you learn effectively through interactivity and activities.

    By the end of the session, you'll have a clear picture of the importance of concepts like empathy, self-limiting beliefs, systems thinking and cognitive biases and their significance in individual and team performance.

    And you won't just learn concepts, you'll take back concrete ideas to implement in your teams starting the next day!

02:45
  • Added to My Schedule
    keyboard_arrow_down
    Yasunobu Kawaguchi

    Yasunobu Kawaguchi - Fun! Done! Learn! - a positive retrospective born in Japan, is this work in your culture?

    schedule  02:45 - 03:05 PM place Mysore Hall 1 people 15 Interested

    In this talk, the speaker will present a brand new retrospective format quickly becoming popular in Japan. This method is heavily influenced by Japanese culture, but it may work great in other cultural contexts. We are looking for your feedback.

    Someone said Agile is not work in Asian Culture ( https://www.infoq.com/news/2016/06/agile-asia/ ).
    One of the difficulties is from retrospectives.

    We found a positive retrospective format better fit for our culture: Fun! Done! Learn!
    After we published the method in a blog in Japanese, many teams in Japan started using the method. We've not taught or facilitated directly; people just accepted and started using it.
    We'd like to share the method as well as how the teams accepted the technique in Japan.
    We are eager to hear from you whether this works for your team or not and why.

  • schedule  02:45 - 03:05 PM place Mysore Hall 2 people 3 Interested

    The story goes ...

    During the Agile Coach Camp at Agile India 2019, we had an interesting discussion driven by Woody Zuill around the concept of Organisational Inertia. This has been a topic of research since the early 80s with the newest research in 2000s as well. The research basically revolves around two aspects:

    1. An organisation's incapability to keep up with major shifts
    2. The resistance towards change

    These don't necessarily stop change from happening but considerably slows down the shift. With organisations struggling to survive in a VUCA world, Organisational Inertia becomes one of the critical factors for consideration. Enter, an Agile Coach! Our industries have heavily invested in them in the recent past and continue to do so in order to help them survive in this VUCA world. Shane Hastie addresses this as the Golden Age of Agile Coaching in which coaches can help the poor souls navigate themselves during a period of turmoil. I respect that.

    But my evil mind links the concepts of Organisational Inertia and the Golden Age of Agile Coaching differently; so during the Agile Coach Camp, I asked folks to run a Thought Experiment which I also mentioned in my talk during Agile India 2019.

    The hypothesis is: "We can deploy Agile Coaches in organisations and hopefully the organisations will overcome their inertia in 10 years to provide a better work experience to their employees. Contrarily, if Agile Coaches cease to exist, organisations may crumble under their inertia in 5 years and the ones left will be great places to work" ... from a Behavioural Economics standpoint, the second option seems better.

    Being a SLICE fundamentalist, I decided to run this hypothesis and began my experiment on 3rd June 2019, the day after I finished my last batch of ICAgile's Agile Coaching training. At the time of submitting this proposal, it hasn't been very long since I started the experiment, and it hasn't been easy to deliberately take a step back from coaching interventions. The observations have been interesting (if not amazing) so far and this is my experience report that I wish to share during Agile India 2020.

    My plan is to run a set of experiments until 31st December 2019 and then decide my way ahead. I mention below the observations so far that I wish to share in my talk but there may be other experiments that I'll share if provided a platform at Agile India 2020.

  • Added to My Schedule
    keyboard_arrow_down
    Teri Christian

    Teri Christian - Case Study: Transform 4500 people with 8 coaches - impossible?

    schedule  02:45 - 03:05 PM place Mysore Hall 3 people 4 Interested

    This is a case study discussion to share how we are transforming the 2nd largest bank in Australia with a core enterprise team of 3 people and an extended coaching team of 8 professional coaches. We not only transitioned ways of working but also helped with organizational design, transitioned job titles (from over 150 to 7) and workflow management. We are using a model that helps teams change incrementally with weekly measures and understood results. We have been able to have remarkable success using a distributed coaching model, introducing new ways of learning and developing a learning organization.

  • Added to My Schedule
    keyboard_arrow_down

    Experience Report

    schedule  02:45 - 03:05 PM place Magnolia
03:05

    Coffee/Tea Break - 25 mins

03:30
  • schedule  03:30 - 04:15 PM place Mysore Hall 1 people 4 Interested

    What is Mindful Agile Leadership?

    It’s the perfect balance of 3 essential elements:

    • The agile mindset : the heart of agile - our attitude and approach to work that is collaborative, adaptable, open to change, value focused with continuous learning and growth.
    • Mindfulness : the quality of awareness - non-judgmental, objective, deliberate observation and openness to whatever unfolds in the present.
    • Servant leadership : being of service to others - focused on the growth and development of others, empowering teams to be high performing.

    These 3 pillars of mindful agile leadership are equally important. Just like the legs of a stool, they provide a stable base encompassing the beneficial qualities of all 3 elements. This enables leaders to build a truly agile culture and positive team environment, and be a more effective and authentic agile leader. Mindfulness isn't just an optional extra; it is a necessary component without which the whole structure collapses. If you lose touch with what's happening in the moment, your emotions and habitual patterns of mind take over, and your ability to be open and authentic is diminished.

    In this session, you will hear why mindfulness is the secret ingredient to develop effective agile leadership. Beyond simple awareness, you will learn how mindfulness help leaders to show up as the very best versions of themselves. Mindfulness helps you improve your focus, think more clearly and make better decisions that lead to more successful outcomes. Mindfulness gives you the ability to stay present and connected despite the stresses and challenges that leadership brings. You will learn techniques to apply mindfulness in everyday activities that enable you to become a more inspirational agile leader.

  • Added to My Schedule
    keyboard_arrow_down
    Peter Maddison

    Peter Maddison - Applied Coaching Practices

    schedule  03:30 - 04:15 PM place Mysore Hall 2 people 5 Interested

    This talk is about my journey to become an ICF certified coach and how I apply those skills both to my role as a strategy consultant and business leader.

    Coaching is a powerful discipline that differs from mentoring, teaching and consulting. Applied correctly it can help you have better, more powerful conversations and allow you to overcome difficult challenges.

    I'll talk through the skills what I learned and where they align and differ from Agile coaching practices.I'll talk to the most powerful tools I learned that I now apply to all my work such as logical levels. Throughout this, I'll do a couple of simple exercises for the audience to take with them and use.

    These skills are valuable to people at every level of the organization and equally, can be applied to all aspects of your life.

  • Added to My Schedule
    keyboard_arrow_down
    Elijah Eilert

    Elijah Eilert - Planning and Recording your Learnings

    schedule  03:30 - 05:00 PM place Mysore Hall 3 people 1 Interested

    How do we learn the right thing at the right time and in the most cost-effective way? How do we organise the process, new insides and decision making at scale?

    Learning is the core activity in any environment of uncertainty - innovations natural companion and proven by many failed startups and projects. Most managers and teams agree on this but organising, storing and using what has been learned is often a challenge. We will be exploring the fundamentals of how to tackle this issue and make learning more manageable, transparent and shareable. We will explore what it means to gather relevant data in the most cost-effective and fastest way. With the goal to enable decision making in an information-poor environment.

    Report Cards are an essential tool for any innovation team that wants to take learning and innovation management seriously. As such many different report cards are in fluctuation. You will be leaving this workshop knowing what the essential parts of a report card are and why. You will use it on a problem yourself to maximise your learning.

    Elijah assisting organisations with their Innovation Practice, Management and Strategy.

  • Added to My Schedule
    keyboard_arrow_down
    Angie Doyle

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

    schedule  03:30 - 05:00 PM place Magnolia people 10 Interested

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

04:30
05:00
05:30
  • Added to My Schedule
    keyboard_arrow_down
    Todd Little

    Todd Little - Feedback Loops are the Key to the Learning Mindset

    schedule  05:30 - 06:15 PM place Mysore Hall 1 people 5 Interested

    At the core of the agile mindset is learning. Continuous learning is only possible through active feedback loops. Linear approaches do not support learning and are doomed to fail in a world of uncertainty. The key is maintaining healthy feedback loops which incorporate new knowledge which enables learning leading to success. An iterative approach with broken feedback loops is similarly doomed.

    From Todd’s background as a Chemical and Petroleum engineer the idea of feedback and control loops was natural and to a large extent how he got involved in the agile community. Todd will explain the basics of feedback loops and how they can enable agility and learning, or when broken they can destroy agility and enable other behaviors such as organizational politics.

  • Added to My Schedule
    keyboard_arrow_down
    Anjali D leon

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

    schedule  05:30 - 06:15 PM place Mysore Hall 2 people 2 Interested

    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 Age 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).

  • Added to My Schedule
    keyboard_arrow_down
    Abhigya Pokharel

    Abhigya Pokharel - Personal Agility - A framework beyond frameworks

    schedule  05:30 - 06:15 PM place Mysore Hall 3 people 2 Interested

    In today's busy world, you have more things to do, than time to get them done. Deciding upon the priorities is a big question. 'What is important to you, and what is urgent?'

    To be able to reflect upon what is important and discard the things that are of least value to you is an important aspect of being happy and efficient, be it at work or in your personal life. The talk, ‘Personal Agility- A Framework Beyond Frameworks’ will provide you an insight to ensure that you do the right thing at the time. It will help you to focus and rethink on the values to be adapted in everyday life.

    The talk will guide you through the ways to cultivate personal agility from my own experience, where I discovered my own personal agility when I got lost in a jungle in South Australia, few years back. What would you have done then, when you knew that you could not have failed in such an appalling situation?

    I would be mapping these experiences and stories into an Agile Model, with a tint of Tuckman's stages of group development.

  • Added to My Schedule
    keyboard_arrow_down

    Case Study 2

    schedule  05:30 - 06:15 PM place Magnolia
06:30

    Panel - 45 mins

07:15

    Reception Dinner - 135 mins

Design Innovation Day

Wed, Mar 18
08:30

    Registration - 30 mins

09:00
10:00

    Welcome Address & Design Innovation Day Overview - 30 mins

10:30

    Coffee/Tea Break - 30 mins

11:00
  • Added to My Schedule
    keyboard_arrow_down
    Kai Gilb

    Kai Gilb - Creating ValueFirst Product Organisations

    schedule  11:00 - 11:45 AM place Mysore Hall 1 people 8 Interested

    Creating a Product Development Organisation that Delivers On-Time and Under-Budget, every time.

    The Problem: Even when having an Agile organisation, projects tend to deliver late and over budget.

    The Solution: There is now a growing group of companies that do things differently. They have learned how to deliver on-time and under-budget, every time. Even more importantly, they have learned to deliver the expected improvements desired by their customers.

    Talk content: In this talk, Kai Gilb will present cases of what is possible to achieve and what these companies do differently to be able to deliver on-time and under-budget, every time.

  • Added to My Schedule
    keyboard_arrow_down
    Karen Ferris

    Karen Ferris - Creating a Culture for Innovation

    schedule  11:00 - 11:45 AM place Mysore Hall 2 people 3 Interested

    This presentation is about building a culture for innovation that enables the design and delivery of great products and experiences to customers.

    Innovation needs to be part of the entire organisational culture – not concentrated in a single person or hidden away in a dedicated office.

    Innovation needs to be everyone’s business.

    This happens when leadership gets out of the way and provides employees autonomy to do something different.

    This happens when failure whilst innovating is not subject to punishment or humiliation because there is an environment of psychological safety.

    Failure is celebrated as an opportunity to learning. Every failure is seen as a step closer to success.

    A culture for innovation is one in which there is recognition that constant change is the norm and embraced as the only way to remain relevant in the era of continual disruption.

  • Added to My Schedule
    keyboard_arrow_down
    Teri Christian

    Teri Christian - Digital Product Mastery - Optimize Your System

    schedule  11:00 AM - 12:30 PM place Mysore Hall 3 people 3 Interested

    The move away from traditional ways of working and thinking to digitization leads to change in the way we work, learn and measure. It is important to understand how the digital economy has shifted our ways of working in a digital organization from strategy to execution.

    Join us in game play where we will explore Digital Product Management and the Critical Success Factors, Events and Skills needed to create value flow to customers. We will look at the skills needed for a company to move from being descriptive to one that can respond to emergent needs. Applying this knowledge will help organisations transform their operating model have a competitive edge in a VUCA economy. Plan to Win!

  • Added to My Schedule
    keyboard_arrow_down
    Angie Doyle

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

    schedule  11:00 AM - 12:30 PM place Magnolia people 3 Interested
    • 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.

12:00
  • Added to My Schedule
    keyboard_arrow_down
    Anna Obukhova

    Anna Obukhova - Neuroscience for Product Owners

    schedule  12:00 - 12:45 PM place Mysore Hall 1 people 6 Interested

    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.

  • schedule  12:00 - 12:45 PM place Mysore Hall 2 people 5 Interested

    Traditional accounting methods measure and manage innovation efforts but this can in fact be one of its biggest disablers. Internal funding systems and the way performance and progress get measured, demand us to make up facts that can not possibly be predicted far into the future. In return, it all too often makes us build the wrong thing. How can Return on Investment (ROI) calculations, for example even be close to true when the product and even the market doesn't yet exist?

    The problem with innovation of course is that we have little to no historical data these approaches heavily rely on. Further, current systems don’t account and adjust for all the new learnings a team gathers. They simply don’t enable honest conversations between those that build products and those that make investment decisions. It leads many people to make up fiction and hide risky assumptions in order to get funding. Many times the best storytellers and politicians get funded, not necessarily those with the best ideas. As a result, organisations fall into the trap of not making corrections early enough before, all too often, the budget is used up before reaching success or ends up with a zombie product on life support.

    Innovation Accounting fundamentally ties learning and money together. It bridges the gap between product and finance. It allows for an honest and effective approach to creating, delivering and capturing value.

12:45

    Lunch - 60 mins

01:45
  • Added to My Schedule
    keyboard_arrow_down
    Jacob Singh

    Jacob Singh - Agile Data Governance: Balancing Freedom-to-measure-anything with Consistency and Reliability

    schedule  01:45 - 02:30 PM place Mysore Hall 1 people 5 Interested

    How do you allow teams the freedom to pollute the data lake, and protect the security, privacy, sanity and usability of data?

    Giving teams the power to choose what they measure means giving them the power to drive org-wide changes.

    Gatekeeping through Data engineering is too slow and centralized.

    Totally DIY, you can't control costs, privacy or integrity.

    This talk will cover both the organizational and technical structures we use at Grofers to enable agile data governance and analytics in a team of over 300 in tech and analytics.

  • Added to My Schedule
    keyboard_arrow_down
    Craig Brown

    Craig Brown - The Puzzle Game | Understanding Agile

    schedule  01:45 - 02:30 PM place Mysore Hall 2 people 4 Interested

    Product managers and software developers often have different ideas of what Agile is and can be. There is also a strong bias in the Agile industry to treading the known territories of the past over innovating and improving towards better.

    In today’s session we play a game that challenges us to think differently about what agile is and can be. We want to show you different ways of working and generate ideas that you can take back to your teams to drive further and better improvements.

    Things you will learn from this session;

    • Is Scrum a best Practice?
    • Are estimates waste?
    • Do we know what value looks like?
    • How does improvement happen on teams?

    We are going to play a game.

    In this game we are going to pitch Scrum teams against other non-scrum teams and see who can do a better job of delivering customer value early and often. Come along and learn something new about how systems and frameworks help or hinder people’s ability to delivery good outcomes.

    Come and join a team. Have fun. Learn something unexpected and be delighted.

    The #NoEstimates movement has been going since about 2011 and challenges us to think differently about planning and estimating, and how we organise teams. In 2013 Chris Chapman invested a game to play that investigates the value of estimates and how they can help or hinder us. This game’s pay-off is wider than estimates though and can teach through experience how systems and frameworks help and hinder us.

    This game dives into how we interact with systems and processes, as well as estimates, and enables us to think differently about how we act within the governing frameworks our workplaces provide us.

  • Added to My Schedule
    keyboard_arrow_down
    Renesh Moodley

    Renesh Moodley - Hacking the workforce of the future

    schedule  01:45 - 03:15 PM place Mysore Hall 3

    What characteristics does the ideal agile team member possess? How would the needs of the future workforce be addressed if those needs aren’t understood and solved for? My experience of integrating new talent into functioning agile teams has lead me to one, surprising, realisation: Most of the approaches and practices that were used to build organisational teams aren’t working anymore. The tried and tested approaches to team formation and leadership are showing little progress into understanding the mindset of the future workforce. We need radical thinking and action in order to reinvent the way we enable people to communicate, collaborate, and ultimately win as a team. It is up to leaders to mould the culture of organisations to ensure that the future workforce is primed and focused to deliver their best work.

    This session focuses on some of the challenges that present themselves when integrating the future workforce into an agile organisation or team. Ultimately, every organisation that is concerned with future proofing their existence must be focused on building teams of motivated individuals that can build the products and services of the future without the constraints we recognise today.

  • Added to My Schedule
    keyboard_arrow_down
    Jutta Eckstein

    Jutta Eckstein / John Buck - Don’t Fail Fast - Learn fast: Failing fast is an option. But innovating fast is a must

    schedule  01:45 - 03:15 PM place Magnolia people 5 Interested

    Often in agile working environments, people aim for failing fast. Yet failure is not the goal - learning is. Failure can lead to learning and so can other approaches. It can lead beyond continuous improvement to transformative learning: seeing your situation from a whole new framework in a way that lets you learn by leaps of insight.

    In this workshop we present specific ways to probe, using hypothesis, and experiments will help you and your team to learn fast. This approach provides a way to get into the mindset of learning and thus always developing.

    Usually a failure is to do nothing… or to do anything (blindly). The key even for big issues is to make small bets (hypothesis) and learn through experiments what's the impact. So, gain insights by (in)validating the bet. In summary it's about thinking big but acting small (and safely). Note, that every great idea, every innovation is at first a guess or rather a hypothesis and only experiments allow us to find out if our idea is really as great as we thought at first.

02:45
  • Added to My Schedule
    keyboard_arrow_down
    Anjali D leon

    Anjali D leon - Build the Right Thing with a Formalized Discovery Process

    schedule  02:45 - 03:30 PM place Mysore Hall 1 people 5 Interested

    Do you have a nagging feeling that you may not be investing in building the right thing?

    Do your products have features that are rarely or never used? Does it takes your organization the full investment of building and launching a product to validate an idea? Is your organization challenged with striking the right balance between the demands of a scalable, high-quality product and innovating on the most compelling problems and opportunities for your customers?

    At Pearson Online & Blended Learning, we met these challenges head-on by creating and implementing a framework that includes early collaboration within a multi-disciplinary team and a light-weight process. Based on Design Thinking principles and practices, the framework effectively balances discovery and delivery efforts. It ensures that, across the portfolio, our investments are focused on the right things, and the efforts of our delivery teams are aligned to solving the most important problems for our customers and addressing the most valuable opportunities for our business.

    In this interactive session, learn about this discovery framework, our implementation approach, and our triumphs and challenges. Each participant will have the opportunity to reflect on how a similar approach may help them address challenges within their own organizations.

  • Added to My Schedule
    keyboard_arrow_down
    RICARDO ABELLA

    RICARDO ABELLA - Don’t mix up our stuff!! Empathy Interviews --> Clean Language

    schedule  02:45 - 03:30 PM place Mysore Hall 2 people 4 Interested

    Design Thinking is one of the best tools available to create products and services with the potential to satisfy people’s needs. Since it is a human-centered process, empathy interviews are the most common technique for collecting data.

    If you want to obtain amazing results, pay full attention and focus on the quality of the information you collect! The more accurate and authentic it is, the more solid and mind-blowing insights you will obtain to guide your ideation phase.

    But be careful! 1) Specialized books and articles have plenty of examples of questionnaires and structured interviews full of leading questions. 2) As interviewers, we tend to contaminate our research with our own metaphors, interpretations, suggestions, mind-reading, references and/or unwarranted assumptions. 3) Interviewees unconsciously look for hidden cues on the questions about how to answer them –conformity, social influence, group pressure.

    Interviewer: “We know change is hard and transitions are always tough. What kind of impact has the new system had? How has this impacted your daily life?” Interviewee: “I thought the new system was awesome, but now that you mention it, it definitely has had a very large impact...”

    Do you want to obtain reliable information? Or more useful and accurate results? Or minimizing the chances of influencing and compromising data authenticity with your bias? CLEAN LANGUAGE is a great tool for this. It’s not a language and it’s not about language; it’s not even about speaking clearly, using fancy jargon or swearing.

    If you want to understand people, how they think and feel, their emotions, passions, frustrations, challenges and dreams, do not miss this workshop. You will have an opportunity to learn, practice and also have fun.

03:30

    Coffee/Tea Break - 30 mins

04:00
  • schedule  04:00 - 04:45 PM place Mysore Hall 1 people 6 Interested

    Any organization’s ability to focus on what matters most to their customers is directly related to their ability to get valuable feedback from them. While more and more organizations embrace agile practices during the development of their services, they often lack in how they collect feedback and therefor don’t get the benefits they are after. After all, what is the upside to investing in being able to pivot, if there is no information available to guide the direction of that pivot?

    The fact that many roadmaps leave little room for flexibility significantly contributes to this and building powerful roadmaps is a really hard task. How does one get feedback about a house without building it completely? How does one give feedback about a car without being able to drive it around the city for a couple of hours?

    This session will provide you with practical techniques on how to build a powerful roadmap for your product or service, one that allows any organization to get valuable feedback from their customers. The session is based on ideas from the draft book Powerful Roadmaps.

  • Added to My Schedule
    keyboard_arrow_down
    Umar Akhter

    Umar Akhter - Stop Selling Software and Start Selling Lehengas

    schedule  04:00 - 04:45 PM place Mysore Hall 2 people 1 Interested

    In 2016 I quit a very successful career in IT which spanned multiple countries including US, Canada, Europe, UK, Singapore & India. I stopped selling software & started selling lehengas! This lead to building Koskii, an ethnic occasion wear brand for women with the learning of an 18 year IT & business career with a global context, working with highly intellectual people and applying those learnings in a local Indian context with a team that was only semi-literate in a business that sold ethnic apparel for women. In this talk, I will be sharing our story and how eventually we managed to set the ball rolling to build a successful retail chain with a vision to scale the world.

  • schedule  04:00 - 05:30 PM place Mysore Hall 3 people 3 Interested

    This Workshop will help you understand why emotional culture matters to building a more high performing and connected team in a more human and empathetic way.

    One of the lesser known and least discussed parts of organisational culture is the emotional culture of an organisation. Research shows the way people feel at work (or the way they don’t feel) has a significant impact on the way they behave, motivation, commitment, creativity, satisfaction, decision making and collaboration.

    In this highly interactive workshop, we will provide you with a way to bring your teams together to talk about the emotional culture of your organisation. We will learn how we explore both those emotions that your employees want to feel to be successful and those that they don't want to feel. From here, you, as a leader but also as a team, can decide what behaviours you want to support and cultivate and what you need to avoid and manage to create the culture you want.

    So far we have run tens of emotional culture workshops, and the results have been stunning. We provide you with a facilitation framework, which can be used with leaders, teams and individuals to talk about emotions and culture in the workplace. It gives people the freedom to participate, be vulnerable and share what they feel and how they want to feel, allowing your people and leaders to take actions and genuinely start to shape the culture.

    Unfortunately, most companies pay little attention to how their people are or should be feeling at work. Many organisations don't support the expression and discussion of emotions at work. Showing emotion at work can be seen as "unprofessional". But emotion drives human behaviour. So come and learn about why emotion matters to your teams and how you can have conversations about emotions and their impact on your teams in a new, fun and engaging way.

  • Added to My Schedule
    keyboard_arrow_down
    Ralf Westphal

    Ralf Westphal - Slicing - Requirements Analysis with the Developer in Mind

    schedule  04:00 - 05:30 PM place Magnolia people 4 Interested

    Starting software development from use cases and user stories sounds great. You get a more structured view of requirements and you get a less pseudo-accurate deliverable to transform into code.

    Unfortunately neither requirements description was invented with developers in mind. Because neither comes with a mapping to code and its structures. Sure, it's just requirements, not designs. But still... How to move on towards code from a use case or a user story? The developer is pretty much left alone with that. Also requirements easily get dissolved in code like sugar in a cup of tea: the code's capabilities are increased, but there is hardly a link to the specific requirements. That leads to waste of all sorts and negative effects: meetings, overengineering, bugs, conflicts, false promises, overconfidence...

    What makes developers happy, on the other hand, are scenarios like they get presented in coding dojos: clear, focused, close to code.

    In my talk I'll present a lightweight, framework rooted in Agile thinking for processing requirements from broad/comprehensive to narrow/detailed in a way so that the subsequent creation of designs and code is well supported. You'll learn simple criteria for "good" requirements - and what to do when they are not "good" (yet). And you'll get acquainted with a "language" you can use with users/POs to drill down into requirements while getting hints for design and implementation. This is satisfying for both sides: developers feel valued with their background leading the process and produce tangible starting points for further development, users/POs feel understood and guided through a process of incremental refinement of their ideas.

    Requirements engineering is a vast subject. But in the end it all boils down to: Does a developer understand where to start implementation or where to change code? And maybe even, how is incremental software development possible?

    Use cases and user stories might be a good starting point, but their shortcomings in programmer guidance should be compensated. Users/POs and developers need to meet on eye-level.

04:55
05:30
06:30

    Panel - 45 mins

07:15

    Reception Dinner - 135 mins

DevEx and DevOps Day

Thu, Mar 19
08:30

    Registration - 30 mins

09:00
10:00

    Welcome Address & DevEx/DevOps Day Overview - 30 mins

10:30

    Coffee/Tea Break - 30 mins

11:00
  • Added to My Schedule
    keyboard_arrow_down
    Michael Nygard

    Michael Nygard - Grinding the Monolith

    schedule  11:00 - 11:45 AM place Mysore Hall 1 people 4 Interested

    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.

  • schedule  11:00 - 11:45 AM place Mysore Hall 2

    One of the main advantages of a Microservices Architecture is to allow teams to independently build and deploy microservices without having to bundle everything into one release and shipping them together.

    For this to really work, we need a mechanism which ensures that when each microservice is independently deployed, it does not break other dependent services. This is not just limited to microservices. Any two components that depend on each other, need to safeguard themselves against the changes does by dependent components. This could mean changes in the protocol, or response JSON structure or data type or message format or just about anything.

    The real question is how do you ensure this?

    This is one of the core problems contract testing tries to solve by making implicit behavioural and structural properties of a component (service) explicit in the form of an executable spec (contract).

    Come to this session to learn how you can do both Consumer and Producer driven contract tests, that prevent accidentally breaking dependency between 2 components.

  • Added to My Schedule
    keyboard_arrow_down
    Dana Pylayeva

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

    schedule  11:00 AM - 12:30 PM place Mysore Hall 3 people 2 Interested

    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.

  • Added to My Schedule
    keyboard_arrow_down
    Todd Little

    Todd Little - Beyond Estimates: Forecasting with Little’s Law

    schedule  11:00 AM - 12:30 PM place Magnolia people 4 Interested

    Little’s Law has been used in queuing theory for over half a century. It is an elegant explanation of the relationship between average throughput, Work in Progress (WIP), and cycle time. In a stable environment it gives us a good understanding of the performance of the system which can used for forecasting.

    But where are the story points and estimation? Certainly, size must matter. But does it? In this workshop we explore Little’s Law through theory and the experience of simulations. Each attendee will come away with a better understanding of Little’s Law and the core assumptions necessary for it to be applicable and useful in forecasting. Through the simulation you will experience why estimation of individual items is often not necessary in an environment where Little’s Law applies.

12:00
  • Added to My Schedule
    keyboard_arrow_down
    Adam Tornhill

    Adam Tornhill - A Crystal Ball to Prioritize Technical Debt

    schedule  12:00 - 12:45 PM place Mysore Hall 1 people 3 Interested

    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.

  • schedule  12:00 - 12:45 PM place Mysore Hall 2

    Digital Transformation is now the holy grail of IT organizations. However, most companies are still struggling with setting up a proper Continuous Delivery process, which shall help the transition into shorter release cycles and faster, more frequent deployments to production.

    Teams may already be familiar with Continuous Integration, Continuous Delivery and Continuous Deployment (the 3Cs) and the differences between them. However, to make these 3Cs possible, we need a fourth C, namely Continuous Testing (a.k.a Test Automation.) Continuous Testing is the fast feedback mechanism that assists the 3Cs and is one of the most difficult challenges for digital transition.

    In this talk, I'm aiming to cover the top continuous testing pitfalls and how companies are solving these problems. This talk is based on practical examples that include key pitfalls around:

    • Test Data management
    • Choosing the right tool/framework
    • Deciding on what to automate?
      • Is In-Sprint Automation possible?
      • Is automation part of Definition of Done?
    • Effective collaboration
    • Test Environments
    • Flaky tests

    It's time the testers took control! And use some of the modern tools that help address those problems. This talk will cover tech stack like Selenium, Appium, PlayWright, Taiko, Docker, Kubernetes, Grafana/Kibana, TestContainers.

12:45

    Lunch - 60 mins

01:45
02:45
  • Added to My Schedule
    keyboard_arrow_down
    Karthik Gaekwad

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

    schedule  02:45 - 03:05 PM place Mysore Hall 1 people 1 Interested

    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.

  • Added to My Schedule
    keyboard_arrow_down
    Naresha K .

    Naresha K . - Take Control of your Integration Testing with Testcontainers

    schedule  02:45 - 03:05 PM place Mysore Hall 2 people 7 Interested

    How easy is it to write and maintain integration tests when the system under test interacts with databases and message stores? It can be quite challenging. The lack of control over the setup of databases can increase the cost of integration testing. Sometimes we take the route of using an in-memory database instead of the one we employ in the production environment, making the tests less effective. With docker containers, you can simplify this to some extent by running the setup before invoking your tests. Imagine if you get to control the database environment right from within the test code. TestContainers bring in this convenience.

    Testcontainers is a Java library that you can invoke from your test code. It provides lightweight, throwaway instances of common databases, web browsers(Selenium tests), or anything else that can run in a Docker container.
  • Added to My Schedule
    keyboard_arrow_down
    Shripad Agashe

    Shripad Agashe - The myth of perfect abstractions

    schedule  02:45 - 03:05 PM place Mysore Hall 3 people 1 Interested

    Deriving abstractions for a given problem description is always challenging. No matter what your experience level is, a new scenario will always be challenging to model. At the core of the problem is something known as "Inverse Problem" i.e. it is often easy to observe abstractions in hindsight than in foresight.

    The modeling that we do,deals with IT systems and people operating those systems. What transpires from it is that the observed behaviour of a system is always a reflection of interference of multiple responsibilities of that system. To give an example, a lock is a lock because of the key. Should we lose the key, the lock is just another dead weight. So when we verbalize lock, certain properties come to our mind and weight is not one of them. But the properties that we perceive as properties of a lock are indeed interactions between a lock and a key.

    It is very easy to extrapolate the lock example for unknown scenarios. In such cases we struggle because we have no clear idea about the underlying components and their interactions. So our best attempts are guess work. And if it works for scenarios at hand, we should stop generalizing. By extension of this argument, we can see that we should not strive for universal abstraction but try and model based on certain heuristics and create a workable domain and leave our abstractions incomplete. At the same time, we should have the humility to accept that our abstractions may be wrong but we should be ready to change them if such a need arises.

    To conclude, in the session, I want to highlight difficulties faced in creating abstractions and how to cope with such difficulties. This is useful from developers to system architects and even CTOs to some extent.

  • Added to My Schedule
    keyboard_arrow_down

    Experience Report 2

    schedule  02:45 - 03:05 PM place Magnolia
03:05

    Coffee/Tea Break - 25 mins

03:30
  • schedule  03:30 - 04:15 PM place Mysore Hall 1 people 1 Interested

    Branch By Abstraction is the lesser-known development practice for software development organizations doing Trunk-Based Development. It is the key technique with feature-flags that allows such teams to implement larger and longer-to-change pieces of work that would otherwise be done on a separate branch. Paul introduced the world to this in 2007 (with materals that made it into the famous Contiuous Delivery book) and talks attendees through the practice.

  • Added to My Schedule
    keyboard_arrow_down
    Saurabh Nanda

    Saurabh Nanda - Property-Based Testing - Examples of Properties from Business Applications

    schedule  03:30 - 04:15 PM place Mysore Hall 2 people 8 Interested

    I got excited about property-based testing after hearing John Hughes talk at Functional Conf 2016. I tried it that year with QuickCheck, but failed miserably (it almost derailed the entire project delivery). I cribbed about it in my talk at Functional Conf 2017. In 2018, Srihari's talk got me excited again. This time, I tried with Hedgehog, and got it to work!

    This talk is about this journey and its learnings. We'll talk about how Hedgehog was used to test [1]:

    • A Postgres backed task/job queue
    • A small Wai/Servant based webapp

    And no, we will not talk about the most common (and completely useless) example of reversing a list!

    [1] Both of these are part of an open-sourced task/job queue library.

  • Added to My Schedule
    keyboard_arrow_down
    Renesh Moodley

    Renesh Moodley - Devops = Culture + Ownership + Empowerment

    schedule  03:30 - 05:00 PM place Mysore Hall 3 people 9 Interested

    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.

  • Added to My Schedule
    keyboard_arrow_down
    Ralf Westphal

    Ralf Westphal - TDD 2.0 - Situation-Aware Programming

    schedule  03:30 - 05:00 PM place Magnolia

    Are you "doing it" the TDD way? Really? Are you getting the results from TDD as you expected? Yes? Great, check out one of the other exciting sessions at this conference.

    No? Then: How come? Isn't TDD supposed to be easy? Just do the red-green-refactor dance and all code's gonna be functional plus clean.

    Sorry, but I beg to differ. It's not that simple. And there are many reasons for that as I'll show you in this talk.

    My main objection is, that TDD as it's commonly explained and demoed, is ignoring the plain and simple reality of problems being of very, very different difficulty. Or have you ever seen a TDD demo beyond the usual code kata exercises like "Fizz Buzz" or "Game of Life"?

    Hence in this talk I want to present a bigger picture. I'll classify programming situations according to the Cynefin framework and put TDD in perspective. It will become clear where TDD might be a good fit and why - but also, where TDD is overtaxed.

    And since TDD is only a fit for a small subset of problems, of course alternative approaches to test-first programming will be presented.

04:25
05:00
  • Added to My Schedule
    keyboard_arrow_down
    Subbu Allamaraju

    Subbu Allamaraju - Finding Your Middle

    schedule  05:00 - 05:45 PM place Mysore Hall 1 people 8 Interested

    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.

  • Added to My Schedule
    keyboard_arrow_down
    Shama Ugale

    Shama Ugale - Testing Conversational AI - Strategy to Automation

    schedule  05:00 - 05:45 PM place Mysore Hall 2 people 2 Interested

    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 toolset 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?
  • Added to My Schedule
    keyboard_arrow_down
    Peter Maddison

    Peter Maddison - Securing your pipes with a TACO

    schedule  05:00 - 05:45 PM place Mysore Hall 3 people 2 Interested

    TACO is an acronym I use with clients to help them map controls from their software delivery pipelines to the organizational controls.

    TACO stands for Traceability, Access, Compliance, and Operations.

    The approach consists of a base list of 25 automatable controls that are documented and the control activity, artifacts and SOR identified. After mapping how these controls are handed we map them to the organizational controls and identify any gaps.

    This model allows for the creation of opinionated pipelines and helps create a common understanding across teams as to what is required in order to be secure.

    Taking a TACO approach can be considered a part of implementing a DevSecOps program and I’ve used this approach at multiple banks. I’ve given the base talk at three conferences and multiple times to internal teams. It helps build organizational confidence in the automation of software delivery.

    During the talk, I’ll run through the different categories of controls, how they are implemented, what the purpose of them is, how to create robust feedback loops for controls such as SAST and how to handle long-running processes such as DAST.

    Content is fairly high level but I can dig into specifics of each given area as questions arise.

  • Added to My Schedule
    keyboard_arrow_down
    Devdas Bhagat

    Devdas Bhagat - How Spilgames migrated to the cloud

    schedule  05:00 - 05:45 PM place Magnolia

    Spilgames went all in to public cloud in 2018. At that point, there were no example of actual migrations, just a number of business studies showing the benefits of public cloud. This talk covers the business reasons of why we went into public cloud, the IT side of the migration including business continuity, refactoring infrastructure, and the state of the systems today

06:00
  • Added to My Schedule
    keyboard_arrow_down
    Dan North

    Dan North - SWARMing: Scaling Without a Religious Methodology

    schedule  06:00 - 06:45 PM place Mysore Hall people 2 Interested

    Daniel Terhorst-North has spent the last few years showing all kinds of organisations how they can deliver faster, achieve better results with less effort, and have fun doing it. He has a wealth of experience and stories of alignment at scale, and not a formal scaling methodology in sight. This is not a coincidence. He has realised, and can demonstrate, why structured scaling methods simply can’t work for very long. Context is king: It constantly changes and we must continually adapt to it.

    Come and learn how to sort the wheat from the chaff, the effective from the dogmatic, of scaling delivery, and find out why Daniel is Scaling Without A Religious Methodology.

06:45

    Panel - 30 mins

07:15

    Reception Dinner - 135 mins

Chaos Engineering Day

Fri, Mar 20
08:30

    Registration - 30 mins

09:00
10:00
10:30
11:00
12:00
12:45
01:45
02:45
  • Added to My Schedule
    keyboard_arrow_down
    Naresha K .

    Naresha K . - Implementing Resilience with Micronaut

    schedule  02:45 - 03:05 PM place Mysore Hall 1

    Micronaut is a framework for developing microservices-based applications on JVM. Micronaut supports Java, Groovy and Kotlin languages. When your application is composed of several microservices, resilience becomes an important design consideration. Since Micronaut is designed from the ground up, keeping microservices in mind, it comes with all the bells and whistles required for expressing your resilience techniques.

    In this demonstration, I present several established patterns for managing resilience, including timeouts, retries, circuit breaker. I demonstrate how to implement these patterns using Micronaut. I also highlight the benefits of doing them in the Micronaut way. Combining the concepts with the implementation makes it easy for the participants to grasp the ideas.

  • Added to My Schedule
    keyboard_arrow_down
    Ashish Kumar

    Ashish Kumar - Confused Tester in Chaotic World #ChaosTesting

    schedule  02:45 - 03:05 PM place Mysore Hall 2

    "You can’t legislate against failure, focus on fast detection and response."

    You can think this as a fairy tale story -

    As once upon a time, in theory, if everything works perfectly, we have a plan to survive the disasters we thought of in advance.

    But big Question is How Did That Work Out ?

    We are here to answer that Big question with our session.

    While it is possible to sit down and anticipate some of the issues you can expect when a system fails it, knowing what actually happens is another thing.

    This really depends on what your tolerances for failure are and based on the likelihood of them happening.

    The result of this is you are forced to design and build highly fault tolerant systems and to withstand massive outages with minimal downtime.

    The prevailing wisdom is that you will see failures in production; the only question is whether you'll be surprised by them or inflict them intentionally to test system resilience and learn from the experience. The latter approach is chaos engineering.

    The important aspect of Chaos Engineering is Chaos Testing.

    Historically, the emphasis has always been on mean time to failure (MTTF); working hard to extend the time between system failures, with little emphasis on how fast a failure could be corrected.

    In today's world, the emphasis needs to shift to mean time to recover (MTTR), minimizing the time it takes to recover from a failure.

    At a high level, chaotic testing is simply creating the capability to continuously, but randomly, cause failures in your production system. This practice is meant to test the resiliency of the systems and the environment, as well as determine MTTR.

    Adopting chaotic testing will help improve your MTTR, improve organizational confidence in the resiliency of your production environment, and it will also keep you out of tomorrow's headlines.

    A case study to showcase the real world how can we handle our failures By testing proactively instead of waiting for an outage.

    The product understudy over here is one of the key products serving the major contact center industries across the globe.

    The impact of outage in an contact center with 40K+ agents specially during peak seasons is huge. Contact center are considered as backbone of industries like e-commerce, telecom, travel etc. and dealing directly with people.

    How we ensured a seamless takeover between contact centers across the globes even if an entire high availability contact center goes down. The established calls in an scales of multiple thousand also recovers in fraction of milli seconds. And how this all was achieved by testing all the unknowns in an controlled environments continuously.

  • schedule  02:45 - 03:05 PM place Mysore Hall 3 people 2 Interested

    Chaos Engineering is the discipline of experimenting in a distributed system to identify the weakness in the Architecture and Design of a system which helps in building the resiliency to attain High Availability. Kubernetes being a de facto standard for container deployments and orchestration the applications running on Kubernetes platform should be highly available and resilient to failures.

    In this talk will walk through a real-time use case of how we encountered an issue with Kubernetes platform that impacted applications running on it and we built resiliency for it. With Nodes and Pods being ephemeral in Kubernetes there are high chances for application users/clients to get network connection errors, such as 5xx in case of HTTP requests, when a node restarts or a pod gets terminated and how we resolved it.

    There are many tools available that create chaos in Kubernetes. This talk covers about the need to do chaos engineering in Kubernetes based on the use case discussed and how it can be done.

03:05
03:30
  • Added to My Schedule
    keyboard_arrow_down
    Lyndsay Prewer

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

    schedule  03:30 - 04:15 PM place Mysore Hall 1 people 1 Interested

    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.

  • Added to My Schedule
    keyboard_arrow_down
    Nikhil Barthwal

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

    schedule  03:30 - 04:15 PM place Mysore Hall 2 people 1 Interested

    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.

  • Added to My Schedule
    keyboard_arrow_down

    Hands-On Workshop 2

    schedule  03:30 - 05:00 PM place Mysore Hall 3 people 1 Interested
04:30
05:30

Post-Conf Workshop Day 1

Sat, Mar 21
09:30

    Registration - 30 mins

10:00
  • Added to My Schedule
    keyboard_arrow_down
    Jeff Patton

    Jeff Patton - Passionate Product Ownership: A Certified Scrum Product Ownership Workshop

    schedule  10:00 AM - 06:00 PM place Magnolia people 30 Interested

    Product Ownership is hard! If you're working as a product owner in an Agile team, you already know this is the toughest and most critical role in a successful product organization. If you're a UX practitioner, senior engineer, or marketing professional in your organization, it may seem like adopting Scrum or Agile development has stripped away your ability to contribute as a product decision-maker.

    If you're adopting an Agile approach, your organization may be struggling with bloated backlogs that aren't well understood, stressful planning meetings that last too long and fail to get at details needed to deliver predictably, a nagging feeling that you're building the wrong thing, a lack of time to work with customers and users, chronically late delivery, and frustrated business stakeholders...There's hope!

    The Passionate Product Ownership workshop takes on the bad assumptions and bad practices that often emerge from overly simplistic approaches to agile development and Scrum. Jeff Patton will leverage his past product leadership experience, and years of coaching product teams to teach an effective product ownership strategy.

  • Added to My Schedule
    keyboard_arrow_down
    Dana Pylayeva

    Dana Pylayeva - DevOps Culture Certified Trainer

    schedule  10:00 AM - 06:00 PM place Plumeria people 27 Interested

    Unique opportunity to get trained by the author of one of the most effective DevOps Culture simulation, prepare for DevOps Culture Certified Trainer exam (DCCT) from CertiProf© and gain competitive advantage in DevOps training marketplace.

    First time in India! The latest 2020 version of this popular simulation (ran at 45 conferences in 15 countries).

    This train-the-trainer workshop will prepare you for many successful facilitations of DevOps Culture simulation and give you access to the licensed training material (PowerPoint slides, handouts, flipcharts design etc). You will learn to run effective debriefing with your groups and help them connect learning from the simulation with solutions to the real-life challenges in their organization.

    The simulation is designed for a broad audience, enabling participants to gain the insights into the “Why” and the “What” of the DevOps before jumping into the “How”. Through this powerful role-based simulation, participants experience the benefits of cross-training, learn to eliminate silos, "shift left" on security, adopt systems thinking and practice optimizing the flow of value from business to development and to IT operations.

    Become one of the DCCT holders - DevOps change agents who are able to create the DevOps Culture simulation experience, providing participants with additional insights into taking the next steps to embracing DevOps mindset and leading organizational change. Guide your workshop participants through the experiential discovery of the following practices: optimizing flow, amplifying feedback loop and growing safety culture. Deliver real-life examples from medium to large size organizations, latest findings from the State of DevOps report and key ideas from “The Phoenix Project” by Gene Kim.

    This unique simulation uses cognitive neuroscience principles, game design theory and elements of “Training from the Back of the Room” framework.

    Learn from the game creator, prepare for DCCT exam from CertiProf© (included in your registration) and help make DevOps culture experience accessible to all – business stakeholders, C-level executives, IT management, techies and non-techies alike.

  • schedule  10:00 AM - 06:00 PM place Jacaranda people 12 Interested

    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.

  • Added to My Schedule
    keyboard_arrow_down
    Nikhil Barthwal

    Nikhil Barthwal - Implementing Serverless Applications on Kubernetes

    schedule  10:00 AM - 06:00 PM place Cassia people 7 Interested

    This workshop covers Knative, Kubernetes-based open-source platform to 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 that can run anywhere: on-premises, in the cloud, or even in a third-party data center. Knative components are built on Kubernetes and codify the best practices shared by successful real-world Kubernetes-based frameworks.

    Each of the components under the Knative project attempts to identify common patterns and codify the best practices shared by successful real-world Kubernetes-based frameworks and applications. Knative components focus on solving many mundane but difficult tasks such as deploying a container, orchestrating source-to-URL workflows on Kubernetes, routing and managing traffic with blue/green deployment, automatic scaling and sizing workloads based on demand, and binding running services to eventing ecosystems.

    The workshop goes into details of how Knative enables you to focus just on writing interesting code without worrying about the boring but difficult parts of building, deploying, and managing an application. It shows how developers can even use familiar idioms, languages, and frameworks to deploy any workload: functions, applications, or containers. We also touch upon Cloud Run (a managed Knative offering) and software architecture patterns for modern serverless applications.

    2