This is not about what an "Agile Architecture" could be. It is about the view from the opposite direction:
How can architecture work look like in order to act as an enabler to work in the spirit of the Manifesto for Agile Software Development?
There are answers to questions like.
•    Why is architecture documentation so rarely read?
•    How much technology focus is helpful and why?
•    What knowledge needs to be built by yourself in the first place?
•    What does programming have to do with architecture?
And above all: what does it mean in practice?

Target Audience: (Senior) Software Developers, Architects, Knowledge-Managers
Prerequisites: Curiosity for why architecture work is still so difficult.
Level: Advanced

Extended Abstract:
This is not about the question "How does a good architecture emerge in an 'Agile environment'". Nor is it about whether hexagonal, clean or onion architectures are good for ‘agile projects’.
Rather, it is about the view from the opposite direction:
What should architecture work look like in practice to act as an enabler for working in the way of the Manifesto for Agile Software Development?
Covering (at least) these points:

• Being read is more important than writing or: The worm must taste good to the fish, not to the angler.
• Concepts are more important than technologies or: Kafka is not a business interface
• Parnas and Dijksta are more important than reddit/r/docker or: "Have we reinvented the wheel yet this year?"
• Software crafting is an architecture issue or: Riding a bike is only easy if you've learned how to do it

We look at what is actually meant by this in detail, and how we can arrive at "good practices" for the daily work.

This session will provide you with insights into the core skill of slicing work and how it is crucial to business agility. Using real-life scenarios, we'll explore the different dimensions of how slicing affects work, including ease of delegation, adapting scope, quality control, measuring and assessing progress, and improving using feedback.
This session will give you inspiration and practical tips for how to slice your projects differently.

Target Audience: Decision Makers, Managers, Project Leaders, Product Owners
Prerequisites: None
Level: Basic

Extended Abstract:
If you love to see and hear lots of real life examples that help you understand and communicate what agility in business is about, this session is for you.
Using real-life scenarios, we'll explore the different dimensions of slicing work, including delegation, scope, quality control, and feedback, and provide practical tips for how to do it effectively. We'll also examine how unpredictability can affect measuring progress and provide strategies to help you adapt. By the end of the session, you'll have a clear understanding of the art of slicing work and be able to apply it to your work for improved business agility.

Your Key Take-Aways:

• Understanding how slicing work affects adaptability, delegation, quality control, responsibility, effectiveness, and tracking of progress
• Learning several strategies to slice work that you can apply at your workplace
• Inspiration from several real-life examples

In this session, two co-creators of Org Topologies™, Alexey Krivitsky and Roland Flemm, will share a method to design, assess and improve your organizational ecosystem.
They will do that by familiarizing you with a set of organizational archetypes that are easy to spot. Hopefully, you will have much better clarity on which organization ecosystem you want to build and which behaviors you expect it to exhibit.
You shall be able to take this tool home and use it as a map in your ongoing, never-ending transformation journey toward agility.

Target Audience: Decision Makers, Transformation Team Members, Coaches, Leadership
Prerequisites: Challenges with scaling agility
Level: Advanced

Extended Abstract:
The legacy of the original lightweight barely sufficient Agile ideas (namely XP and Scrum) has been impeded by the difficulties of applying them beyond a single team without losing the key principles and the promised gains.
Over the last decade, that challenge has led to a rose in heavy-weight methods, especially SAFe™, which has become a go-to place for "everything agile". It provides the user with a profound variety of specific tools and techniques for "scaling agile". Many enterprises are on the path of "rolling out" these ideas by the book with the help of trained coaches. But will we eventually get the promised gains of agility once we fulfill the requirements of the framework in our enterprise? Is such a prescriptive approach agile itself? And more importantly: will we own the change and know how to keep improving beyond the rule book?
In recent years, we have seen the emergence of other methods: framework-agnostic org design DIY toolboxes. In this family of modern ideas, Team Topologies™ and unFix™ stand out from the crowd. Their approach is to offer us a "lunch buffet" to pick structures and processes that suit our situation. It is a flexible approach with a lot of freedom of choice. It offers a fresh path for some of us trying to avoid the burden of frameworks. But the freedom of freely picking org elements implies that we possess a clear bigger picture and won't get lost in the night-gritty details of the puzzle pieces. As leaders, managers, and coaches, how fluent are we in org design, queuing theory, and systems thinking? How can we be confident that we won't lose the plot by trying to put together those puzzle pieces? And more importantly: will we get long-term gains, or will we inflict more unforeseen problems by focusing too much on the small building blocks rather than the whole system?
Difficult questions. Org Topologies™ doesn't have all of them answered for us. But being a framework-agnostic approach for designing agile ecosystems where business and technology would work as one, it can provide us with a solid basis on which all other decisions can be grounded. Essentially, Org Topologies™ moves us from the dualism of frameworks vs. DIY methods into the realm of ecosystems - a unity of interdependent organizational parts that together exhibit well-recognized behaviors.
In this session, two co-creators of Org Topologies™, Alexey Krivitsky and Roland Flemm, will share a method to design, assess and improve your organizational ecosystem. They will do that by familiarizing you with a set of organizational archetypes that are easy to spot in any organization. Hopefully, by the end of the talk, you will have much better clarity on which organization ecosystem you want to build and which behaviors you expect it to exhibit. Eventually, you shall be able to take this tool home and use it with your leadership group as a map in your ongoing, never-ending transformation journey toward agility.

After years of contributions, there is still a disconnection at the boundary between the leadership development world and agility. On one side, there are proposals on the role of the leader. On the other side, “frameworks for scaling”.
Especially at scale, agile leadership is the art of integrating modern collaborative leadership concepts and sound emergent strategies for organisational development.
In this interactive session, we will discuss the overarching structure of agile leadership and how to apply it to your organisation effectively.

Target Audience: Leaders, Scrum Masters, Coaches
Prerequisites: Generic understanding of agility and leadership. Ideally experience in a leadership position
Level: Advanced

Extended Abstract:
Agility and Leadership development: two parallel worlds that address one part of the problem each, but neither provides a holistic approach.
As part of our work on ScaleAgility, a framework-free set of principles for agile at scale, the authors have also developed a way to integrate the two disciplines: what does leadership do in practice? How can they combine the ideas proposed by leadership model X [add your preferred model here] and the need for an organisation to evolve healthy agile and collaborative structures?
In this interactive presentation, we will propose our concept for agile leadership at scale, indicating a concrete implementation path agnostic to a specific leadership development model or scaling framework. Yet, it gives pragmatic structural elements that will allow you to effectively implement a sound agile leadership concept or use it to “plug in” your preferred models.

Sustainable success for agile in the large needs leaders to shift their focus from managing people to managing the system so that people can thrive.
This session builds on our successful OOP 2023 session ("Pragmatic Scaling to Business Agility: Crafting Organisations for Innovation where People can Thrive") by:

1. Focussing on how leadership should be different in an agile organisation.
2. Sharing experiences of applying the model with real clients.

Participants will assess their own leadership and identify "nudges" for developing further.

Target Audience: Leaders, Agile Coaches, Product Owners, Scrum Masters, Managers
Prerequisites: Practical experience with one or more agile frameworks
Level: Advanced

Extended Abstract:
This interactive workshop presents a pragmatic approach for scaling agile. The approach is based on five shifts needed in typical organisations to get agile to work well at scale. It guides how to find the right balance for each shift, using the current context of the organisation. In this way it not only presents the end state, but also the possible steps to implement each shift.
At OOP 2023, we facilitated a successful interactive 90-minute session entitled "Pragmatic Scaling to Business Agility: Crafting Organisations for Innovation where People can Thrive".
This introduced 5-shifts that organisations can make to help agile to thrive. Participants assessed their organisations against the shifts and identified "nudges" to develop their agile approach.
This proposal builds on that session by:

1. Zooming in on how leadership should be different in an agile organisation.
2. Sharing experiences and stories of applying the model with real clients.

The workshop will provide participants with insights into the future of leadership and leadership in a scaled agile environment.
They will also apply the model to their own context or a context they are familiar with and identify options for their future growth as agile leaders.

In this interactive training session, we will dive into the fascinating world of exploratory testing. Exploratory testing is a mindset and approach that empowers testers to uncover hidden defects, explore the boundaries of software systems, and provide valuable feedback to improve overall quality.
Through a combination of theory, practical examples, and hands-on exercises, participants will gain a solid understanding of exploratory testing principles and techniques, and learn how to apply them effectively in their testing efforts.

Max. number of participants: 12

Target Audience: Developers, Testers, Business Analysts, Scrum Masters, Project Manager
Prerequisites: None
Level: Basic

Extended Abstract:
In this interactive and engaging 3-hour training session, we will dive into the fascinating world of exploratory testing. Exploratory testing is a mindset and approach that empowers testers to uncover hidden defects, explore the boundaries of software systems, and provide valuable feedback to improve overall quality.
Through a combination of theory, practical examples, and hands-on exercises (with a E-Commerce Platform), participants will gain a solid understanding of exploratory testing principles and techniques, and learn how to apply them effectively in their testing efforts.
Whether you are a beginner or an experienced tester, this training will equip you with the skills and knowledge to become a more effective and efficient explorer of software.
Learning Outcomes:

1. Understand the fundamentals of exploratory testing and its importance in software development.
2. Learn various techniques and strategies for conducting exploratory testing.
3. Develop the ability to identify high-risk areas and prioritize testing efforts during exploration.
4. Acquire practical tips for documenting and communicating exploratory testing findings.
5. Gain hands-on experience through interactive exercises to apply exploratory testing techniques.
6. Enhance critical thinking and problem-solving skills to uncover hidden defects.
7. Improve overall testing efficiency and effectiveness by incorporating exploratory testing into your testing process.
8. Learn how to collaborate effectively with developers, product owners, and other stakeholders during exploratory testing.
9. Gain insights into tools and technologies that can support and enhance exploratory testing activities.
10. Leave with a comprehensive understanding of exploratory testing and the confidence to apply it in real-world scenarios.

Join us for this immersive training session, and unlock the potential of exploratory testing to uncover valuable insights and improve the quality of your software products.