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.

DateTime: This workshop is scheduled on Oct 12th and 13th from 1 PM to 5 PM IST (4 hours each day)

Direct URL:

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.

DateTime: This workshop is scheduled on Oct 12th and 13th from 2 PM to 6 PM IST (4 hours each day)

Direct URL:

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.

DateTime: This workshop is scheduled on Oct 12th and 13th from 2 PM to 6 PM IST (4 hours each day)

Direct URL:

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.

Direct URL:

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.

Direct URL:

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

Direct URL:

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.

Direct URL:

Are you born as an Agile leader or can you develop or pivot your leadership style to be one? This talk will uncover ten Agile leadership attributes in a fun and engaging way, gives participants an opportunity to reflect on their own capabilities and then self focus areas for further development of their leadership capability

Direct URL:

Unlike typical operating models, the DigOps model focuses on organizational mindset, mechanics, maturity and market share. The model helps change culture and creates a team of team environment using Diverse Collaboration techniques that develop diversity, equity and inclusion across the organization as they deliver a predictable flow of value to their customers. 

As organizations learn, they develop this same relationship with their customers by creating opportunities for Diverse Collaboration where every voice can be heard.  This helps them relate to their customers, potential customers and provide the best experience possible. 

Join me in exploring this DigOps model and how to implement a team of teams approach in your organization that will promote diversity, equity and inclusion that results in business results. 

Direct URL:

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.

Direct URL:

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.

Direct URL:

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

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

Direct URL:

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.

Direct URL:

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.

Direct URL:

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.

Direct URL:

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.

Direct URL:

Direct URL:

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.

Direct URL:

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

Direct URL:

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.

Direct URL:

Direct URL:

The shift from industrial to product thinking is profound. Digital product thinking is not an evolution of industrial thinking, it is a different thing altogether. Tools and structures that support industrial efficiency work against digital product efficiency, and vice versa. Great industrial leadership doesn't transfer to great product leadership.

Industrial thinking built a 400-million customer, India-wide 4G network from scratch in less than 8 years. Now they are pivoting into a digital platform company. They still need great industrial thinkers and leaders, but they will be sharing the stage with a new generation of great digital product leaders.

This talk contrasts these two mindsets and explores why they are so different, and offers some suggestions for thriving in a hybrid industrial-product world.

Direct URL:

Direct URL:

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

Direct URL:

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.

Direct URL:

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

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

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

Direct URL:

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.

Direct URL:

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.

Direct URL:

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!

Direct URL:

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.

Direct URL:

Direct URL:

Aren’t we fascinated looking at a gymnast performing a routine? A trapeze artist swinging from one side to the other? An acrobat doing his/her amazing balancing act? But, we know little of the mechanics behind such feats of balance. All this is controlled by the ear and the brain. The semicircular canals of the ear act as a gyroscope and accelerometer to control angular acceleration and to help you decide which plane the head is moving. Unfortunately, millions suffer from various balance disorders.

NeuroEquilibrium™ is a pioneer in the field of vertigo and balance disorders aiming to provide advanced and economical medical assistance to people suffering from these conditions. We are making groundbreaking innovations in this field by developing indigenous vertigo diagnostic systems which operate on cutting-edge technology like 3D Printing, Cloud Computing, VR, AI, etc.

In this talk, we'll share our experience building NeuroEquilibrium.

Direct URL:

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.

Direct URL:

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!

Direct URL:

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.

Direct URL:

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.

Direct URL:

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.

Direct URL:

A crisis is a great motivator and organisations have adapted remarkably well to remote work. Many leaders have been surprised at the smoothness of the transition but there are some emergent challenges. The line between safety in the workplace and safety in the home has become blurred, leaders who relied on command and control to get results are struggling with the paradigm shift, and while some teams (particularly agile teams) are demonstrating productivity gains, the increased risk of alignment gaps means senior staff are increasingly overburdened with virtual collaboration. Meanwhile, several tools have jumped the chasm into mainstream existence and capital is flowing towards a remote future.

In this talk, Andrew will talk about how remote:af, the world's first framework for effective remote working, is helping organisations to navigate the remote now, and the hybrid next. He will focus on patterns that organisations are currently using to support remote leadership teams, to design operating models that are optimised for remote and hybrid working, and to take strategy into execution.

Direct URL:

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.

Direct URL:

How keeping things simple can help build better products. There are simple, pragmatic and powerful ways that can help us to reduce the risk of starting new initiatives and get real feedback quickly. I will share experiences where simple techniques of using a pen and a paper to create a paper prototypes helped us answer complex problems and validate business ideas, quickly.

This approach helped in building an innovative and world-class product called Springer Nature Experiments, allowing researchers across life sciences to quickly find and evaluate protocols and methods across life sciences. Springer Nature Experiments combines portfolios across the Springer Nature resources which is the largest in the life sciences, to make searching for experiments easy and effective.

Direct URL:

1. How do I motivate my developers when I cannot show them the financial value of the features they build?

2. How do I prioritize which production defect to fix first?

3. How do I choose the right solution for the customer when I have multiple solutions to solve the problem?

4. How do I decide which feature to enhance first, using real data instead of personal intuition?

If any of these questions keep you awake at night, this session is for you.

In this interactive session, I will share practical lessons from great product development teams. You can hear from me about how simply creating an intentional product usage metric strategy can help in avoiding many conflicts.

Direct URL:

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.

Direct URL:

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.

Direct URL:

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.

Direct URL:

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.

Direct URL:

We all know what a product is. We buy and use them all the time. But, what does it mean where you work? Are the things you build or make really products or not? Are you creating a successful product, or just doing a job? We’ll talk about what product thinking really means and why you and your company may not actually be using it. And, if you’d like to be more product-centric, some specific principles for doing that.

Direct URL:

Because when the pandemic hit, we saw dramatically rapid shifts in strategies, supply chains, and processes designed to accommodate a completely different world than existed in February. The most important one, I think, is that urgent need for technology changes drive just about everything, but the technology change has nothing to do with software and everything to do with supporting some new situation that requires a change in the underlying technology – NOW!

In this new normal there is a clear goal for everyone on a team – we must suddenly shift production from fresh salmon to frozen salmon, or from commercial packages of flour to consumer packages of flour – with specialists in all relevant fields applying their expertise to accomplish that goal. Or we have to shift all teaching to online in a week, accommodating teachers who have never taught online and students who have questionable internet access. The list goes on -but the underlying message is the same – it's not about software, it’s about providing the technology infrastructure to accomplish something urgent and important that is much bigger than software. It never was about software, but never has that been so clear as it is now.

Direct URL:

Whether you are a manager, scrum master or engineer, you need to know why and how the technical practices of test-driven development, refactoring, continuous design, clean code and automated testing can help you and your organization be great.

Technical excellence is more than two-week sprints, a burn-down chart and a daily stand-up meeting. The basic rules of Agile or Scrum are not an end in themselves, but a starting point based upon principles and practices that allow and encourage teams to adopt, adapt, and refine their craft. Unfortunately, it may seem to the technical people that agile is just another micro-management approach.

Extreme Programming with its provocative name, got people’s attention in 1999. It is based on sound technical practices. Why do so few agile teams employ engineering practices that support the tight iterative cycles of Agile and Scrum? The creators of Scrum expected the continuous improvement cycle to pull engineering practices into teams once the cycle revealed the problems of poor product quality, hard to change code, wasted time debugging, long stabilization efforts and the ever-growing burden of manual test. This talk will cut through the mystery and show why we should all strive for Technical Excellence.

Direct URL:

In a complex, interdependent eco-system, where each service is evolving rapidly, we typically end up with an Integration Hell .i.e. the myriad problems that occur when API integrations break down

• Provider and consumer integrations break when their understanding of the API endpoints are out of sync
• Working integrations break when the API developer makes a change without informing the consumer
• Development and testing slow down when the consumer depends on the provider API running in a staging environment:
  • The network may be down
  • The environment hosting the API may be down
  • The staging API may crash, or may not even be started
  • Development can be delayed if the staging API is not kept up-to-date
  • API changes can come in at the last minute, resulting in breakage on the consumer side
  • The provider API may break backward compatibility, resulting in breakage on the consumer

Instead, what if we could make the dependencies between the provider and consumers explicit in the form of executable contracts. These executable contracts provide a common, clear definition of their API endpoints. They give instantaneous feedback about accidental breakage to the teams so that they can work independently. These executable contracts are:

1. Kept up-to-date and acts as a single source of truth
2. Used for service virtualisation, keeping consumers in sync with the contract
3. Run as tests against the provider API to validate it's request and response type definitions
4. Tightly integrated with CI
5. Capable of pinpointing any backwards-incompatible changes to the contract

This is Contract Driven Development, and it heralds the Death of Integration Hell.

Here's a sample contract:

This session will demonstrate all the key points of Contract Driven Development as implemented by the teams using an open-source tool called Specmatic.

Direct URL:

Effective organizational security is a shared responsibility and yet, a big number of organizations suffer from testing security issues at the last minute or not at all. In this talk, we discuss secure best coding practices for developers to improve an organization’s security posture.

Direct URL:

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?

Direct URL:

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.

Direct URL:

The Test Automation Pyramid is not a new concept.

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

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

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

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

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

Direct URL:

Serverless applications are usually made up of functions interacting with fully-managed services, so you can develop applications without having to think about servers. This enables us to build applications that scale quickly and reliably based on incoming requests, often in the form of events that go well beyond API requests and scheduled cron job type rules. In the event-driven model, the components communicate with events and that helps you adopt some of the best practices for distributed systems by default. In this talk, we’ll explore what events are, the different types of events available to your serverless applications, where they come from and how to utilize them to build applications that can provide more value to your customers. All of this with a lot of architectural pattern examples.

Direct URL:

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.

Direct URL:

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.

Direct URL:

Direct URL:

Direct URL:

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.

Direct URL:

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.

Direct URL:

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.

Direct URL:

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.

Direct URL:

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.

Direct URL:

Kubernetes is a force to be reckoned with for enterprises, and there’s been a major shift to move their infrastructure to use Kubernetes. This session covers best practices you’ll want to keep in mind when making a shift from deploying applications to web servers and moving to a microservices model and Kubernetes. You’ll learn about topics you should consider while moving to Kubernetes and principles you should follow when building out your Kubernetes-based applications or infrastructure. The ideas presented are from war stories and experiences of working in the trenches with Kubernetes for the managed service for Oracle Cloud.

Direct URL:

Networks pervade nearly everything we do in software development. Our code runs on networks but it is also a network of relationships among its parts. Our teams are networks too. Our organizations are as well. In this keynote, Michael Feathers will outline several principles of network science that underlie the structuring of workflow, organizations, teams, and code. This common frame can help us make better decisions as we tackle problems in our work.

Direct URL:

Perfection is unattainable yet we live in a world where we are encouraged to compare ourselves and our work to an impossible standard. Come here to understand why chasing this goal will destroy the systems, companies, and lives you're supposed to make better and how injecting a little imperfection into your day will help make everything better.

Direct URL:

Chaos Engineering is an up and coming method used by SREs for autonomously introducing random failures into a system and measuring whether the service degrades or fails. This talk discusses how security teams can use Chaos Engineering principles to develop, test, and maintain resilient log pipelines.

Direct URL:

Shrinking Production Incidents details an organized approach for reducing the overall time of production outages.

Reliability is a key feature of a service that keeps users happy. Users do not stick with services that have frequent outages.

In this session, you will get to know an organized approach that will help your team to manage production incidents so your service will have fewer, shorter and smaller outages, enabling increased release velocity for your developers.

Direct URL:

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.

Direct URL:

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.

Direct URL:

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

Direct URL:

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.

Direct URL:

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

Direct URL:

In this talk, we utilise the tools of Functional Programming to provide robust and resilient software components. We start off by defining Functional Programming and investigate how this itself can improve the quality of software. Once we have committed to programming in this style, we explore some of the tools that naturally arise. These tools will be explored using a variety of programming languages, since these techniques are available in many popular programming environments. Some examples will also introduce Haskell syntax.

1. Using static types to provide a reliable indication of the behaviour of software, including up to proof of correctness. We will use the technique of parametricity to demonstrate this reliability[^1].
2. Using property-based testing for high coverage testing with minimal programmer effort.
3. We will also have a look at the trade-offs that are made between types and tests and discuss a reasoning framework on making optimal decisions on when to use each.

[^1]: Wadler, Philip. "Theorems for free!." FPCA. Vol. 89. No. 4. 1989

Direct URL:

Mangle is an open-source project that enables you to run chaos engineering experiments seamlessly against applications and infrastructure components to assess resiliency and fault tolerance. It is designed to introduce faults with very little pre-configuration and can support any infrastructure that you might have including K8S, Docker, vCenter or any Remote Machine with ssh enabled. With its powerful plugin model, you can define a custom fault of your choice based on a template and run it without building your code from scratch.

In this workshop, you will learn how to inject faults on infrastructure and on a running Java application.

Direct URL:

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

Direct URL:

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.

Direct URL:

Servirtium == Service Virtualized HTTP (for Java and other languages) in a record/playback style, making plain Markdown recordings that suits source-control.

Utilization of "Service Virtualization" is best practice towards fast and consistent test automation. This tech should be used in conjunction with JUnit/TestNG (or your language's test framework), etc. Versus alternate technologies, Servirtium utilizes Markdown for recorded HTTP conversations, which aids readability allows for diffing to quickly determine if contracts are broken. That last is an important aspect when Service Virtualization is part of a Technology Compatibility Kit (TCK). All will be revealed in this presentation

Direct URL:

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

Direct URL:

Direct URL:

We are all here for the same purpose: to ensure the systems we build operate reliably. This is a difficult task, one that must balance people, process and technology during difficult conditions. We operate with incomplete information, assessing risks and dealing with emerging issues. We have found Chaos Engineering to be a valuable tool in addressing these concerns. Learn from real-world examples of what works, what doesn’t, and what the future holds.

Direct URL: