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.

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.

Around sunset, a building architect was walking among workmen. Many were cutting stones. But one person caught his attention as he whistling and doing his job. It wasn't much time before he understood that he is breaking stones since morning. Out of curiosity, he went closer and asked him "what are you doing?". without blinking he said "Can't you see that I am cutting stones that is will build a great citadel. It isn't difficult to see that if we can help our team members to see the larger goals, mindset can be influenced.

Story telling is powerful. Why? It works holistically on the brain. Across age groups, people respond to stories. For a well told story, recipients empathetically respond. From a developer to a leader, stories help them communicate effectively. When one carefully see, all stories follow the same pattern "Selection, Connection & Relation" This talk will demystify the art of storytelling, its impact on mind of hearers and how could one can construct and practice story telling for driving change

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

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