Software-Architecture Revolution is the process of making profound, large-scale changes to the fundamental structures of software systems to improve its attributes, such as availability, scalability, and maintainability, or to enable new requirements that are incompatible with the current capabilities. Architectural revolution demands substantial effort from the organization and needs effective leadership to be successful. This talk draws from practical experiences (patterns) to improve the effectiveness of architectural revolution initiatives.

Target Audience: Architects, Managers, Project Leaders, Coaches, Developers, Product Owners, Decision Makers
Prerequisites: Leadership, Architecture, Project Management, Working with Teams, Agile mindset
Level: Advanced

Extended Abstract:
Pressure to adapt to and shape the market requires agile organizations to add new features, accommodate new interactions, and have new teams work on adapting the software. Sometimes a straightforward software architecture that starts out small when communication is easy can support guided, incremental architectural changes and can gradually evolve with its environment, remaining fit for its purposes. Other times it is not so simple: the initial software architecture can be poorly suited for supporting required changes, or the accumulation of suboptimal architectural decisions (also known as architectural technical debt) can be too severe; in either case, the architecture needs an extensive revision; especially for the organization to remain agile and adapt to the changing market.
Software architecture revolution can be defined as the process of making profound, large-scale changes to the fundamental structures of a software system to improve its attributes, such as availability, scalability, and maintainability, or to enable new requirements that are incompatible with the current capabilities. Architectural revolution usually demands substantial effort from the organization and thus depends on effective leadership to be successful. However, while there is plenty of research on the technical aspects of any architectural transformation, not much is available from the leadership perspective. The role of managers and other leaders include championing the revolution initiative, prioritizing activities, negotiating the allocation of people and resources, evaluating results, taking corrective actions, and reporting achievements. This talk draws from practical experiences to describe patterns to improve the effectiveness of architectural revolution initiatives.

Test coverage: 100% - Check!
And why do we still have bugs?
OK, tests don't prove the absence of errors.
And at the end of the day, they are just code which could contain bugs as well.
And perhaps they give us a false sense of security.
But how do I know, that my test are good?
One way to find out is using Mutation Testing.
In this talk I want to explain, what Mutation Testing is, how to do it and when it is helpful.

Target Audience: Developers, Achitects, Testers
Prerequisites: Basic knowledge in Programming, some experience in writing tests
Level: Basic

Extended Abstract:
More and more teams are writing tests for their production code, be it by applying concepts like TDD or BDD or by just writing them "after the fact". Sometimes there is also a test coverage metric that needs to be met. The positive effect is definitely that there are tests. Be it for my future self or a future colleague or as a form of documentation.
Tests are a means of telling something about the quality of production code. Mutation testing can help tell something about the quality of tests. It helps to find missing tests and potential bugs.
The concept of mutation testing is already more than 50 years old, but its application has not yet become widespread.
This talk should encourage you to take a closer look at mutation testing to find out what possibilities it offers in your own project, but also to see what disadvantages or pitfalls there are.

How often have you heard that ‘Yes this is important, but we don’t have the capacity right now’ or ‘sure let’s put it in the backlog’?
This is something we should not brush off or take lightly. Accessibility testing is vital especially when your product is a user facing application.
We need to be socially aware as a team and build quality towards our product with making it more accessible.

Target Audience: Everyone as Accessibility is for social awareness
Prerequisites: None
Level: Basic

Extended Abstract:
At least 1 in 5 people in the UK have a long term illness, impairment or disability. Many more have a temporary disability. A recent study found that 4 in 10 local council homepages failed basic tests for accessibility.
This is quite vital and the sooner we as testers can advocate this into our teams, we make our product more accessible, reduce the risk of bad product reviews, reputation and also be more socially aware. Let's shift left and make accessibility testing built-in our teams.

1. Understand why accessibility testing is important?
2. How I adapted accessibility mindset?
3. How to coach team and bring accessibility into your teams?
4. Demonstrate various tools available to perform accessibility testing (with demo)

How can a deterministic function possibly give random results? We will find out and learn how to use various random number distributions.
Random numbers haven't changed much since C++11, though new features can make these easier to use. Card games and similar need randomness to be fun and make good teaching examples. We will also discover a way to code ourselves (or blobs at least) out of a paper bag in the process.

Target Audience: intermediate. There will be some code and simulations of blobs escaping paper bags
Prerequisites: None but there will be some algorithms and C++
Level: Advanced

Extended Abstract:
Most of us need a random number at some point if we write code. We will discover how they are generated. We will see how to ensure simulating a dice roll makes the numbers 1 to 6 equally likely, and note some pitfalls to be aware of in some programming languages.
We will have a brief aside into stochastic outcomes from deterministic models, also known as chaos. Applying a function iteratively can’t possibly give non-deterministic results, right? We shall see.
After this aside, we will return to using random numbers. We will consider common mistakes and how to think clearly about "random" code. To round off, we will think about how to test code which uses random numbers.
By the end we’ll be familiar with terms like pseudorandom number generator (PRNG), linear congruential generator and random distribution. Finally, we’ll use various distributions to race some blobs out of a paper bag. Seeing a visual demonstration will solidify some the learning outcomes.

In this session we will walk through various techniques to significantly reduce the resource consumption of regular Spring Boot applications, including using Spring AOT for regular Spring apps, compiling Spring Boot apps to native images (using GraalVM), and using CRaC for instant startup (for scale-to-zero scenarios). We will compare the different approaches, discuss pros and cons for each technology, and share concrete numbers from real-world applications to give the audience an idea of what can be achieved using these technologies.

Target Audience: Developers, Architects
Prerequisites: Basic Spring Boot knowledge required
Level: Advanced

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/martin.lippert

User-centred design is one of the default modes of teams working with software, but the consequences are often unsustainable in a densely networked world as we privilege users over all other stakeholders and systems. How might teams approach building products, services and organisations from a more sustainable standpoint than 'user-centricity'? This talk looks at how the techniques of game design, community development, platform operations and security practices can support a practice focused on hyperobjects for multi-centric design.

Target Audience: Leaders, Builders, Architects, Designers, Community Members
Prerequisites: No previous knowledge, only enthusiasm for systems, building things and design
Level: Advanced

Extended Abstract:
The key feature of a 'tragedy' is when everybody does the right thing but it goes wrong anyway. The aim of this session will be to look at why user-centred design goes wrong even if everyone's intentions are pure. This talk (gently!) brings in ideas from feminism, design thinkers, political science and anthropology to focus on very practical, grounded approaches to sustainable design in software teams. We'll look at how building things and designing organisations that have increased levels of friction can improve users' experience and how 'seamless' design can lead to disempowerment. And we'll also draw on the speaker's practical experience of building products used by millions of citizens as part of the UK's digital transformation. By the end of the session we'll have a sense of what might replace the shallow seamlessness of 'user-centred' design — a multi-centric, transcendental design aimed at manufacturing enthusiastic consent.

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.

Come and hear the story of a company that is on the journey from the old monolithic, on-premise, waterfall world to the new modular, agile, domain-driven, multi-tenant, cloud-based microservices world. The challenges come from different directions: both technical and organizational aspects have to be mastered. The domain has to be understood, so that the system can be structured right. The big bang has to be avoided.
In this talk we will look at how our “fictional” company has struggled with and finally overcome those challenges.

Target Audience: Architects, Developers, Project Leaders, Managers
Prerequisites: Programming Experience
Level: Advanced

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/henning.schwentner

Reducing the gender gap in technology companies is a critical goal for fostering diversity, promoting equality, and unlocking the industry's full potential. Despite significant progress in recent years, women remain underrepresented in technical roles and leadership positions. Diverse teams bring different perspectives, creativity, and innovation, leading to better problem-solving and successful businesses. By working together, we can create a future where women are equally represented and empowered in all aspects of the technology sector.

Target Audience: Leaders, C-Levels, Technical Leaders, Managers
Prerequisites: None
Level: Advanced

Extended Abstract:
The technology industry, a rapidly growing and influential sector, has made significant strides in innovation and progress. However, the underrepresentation of women in technical and leadership roles still needs to be addressed. This gender gap has far-reaching consequences, including limiting diversity in problem-solving and innovation, fostering a hostile work environment for women, and missing out on the untapped potential of the entire tech workforce.
A multifaceted approach is necessary to address this issue and build a more inclusive tech industry. For this, some actions can be performed, for example: Mentorship Programs: Establishing mentorship programs specifically for women in tech can be immensely beneficial. Having experienced mentors who understand the challenges and opportunities in the industry can help women navigate their careers, build confidence, and foster a sense of belonging. Addressing Unconscious Bias: Conducting unconscious bias training for all employees can lead to a more inclusive workplace. Tech companies can create a culture of equality and fairness by raising awareness of implicit biases and providing tools to challenge them. Retention and Support: Implementing retention programs focused on supporting women in tech careers is essential. Companies should prioritize creating an environment where women feel valued and respected and have equal opportunities for growth and advancement.
By collaborating and investing in these strategies, we can work towards a future where women are equally represented and empowered in all aspects of the technology sector. Embracing diversity and gender equality is the right thing to do and a crucial step toward driving innovation and progress in the technology sector. During this lecture, we discuss the global panorama, show some actions that have shown promising results, discuss the benefits of reducing the gap, and define joint actions that can be promptly implemented in their companies and teams.

As more organizations are moving to the cloud, cloud architectures are getting more sophisticated by having a kind of technology diversity. This includes for example container orchestrators, database services, networking components & virtual machines.
When it comes to security, observability on this diversity is paramount. The main question here is, do you really perceive when your app landscape is under attack?
In this session, you'll have the opportunity to see various attack vectors & ways to mitigate them using different technologies.

Target Audience: Architects, Developers, Software Engineers
Prerequisites: Basic cloud & security knowledge
Level: Advanced

Extended Abstract:
Come and watch a live attack on a real-world based cloud architecture and see the attacker scan web applications and start lateral movement with the goal of exfiltrating data. Furthermore, become a part of the blue-team, defending and securing the architecture with modern open source tools.

-Intel AI everywhere – what Intel can offer you to start your AI journey 

-Intel – Intro to Intel LiftOff AI program for startups 

-live demo

-Unlock the Full Potential of Your Code and Data with GenAI with demo

-Running your own LLM in the Intel Developer Cloud - Best Practices 

-Q&A

Microfrontends are a popular concept for development in an enterprise project, where a large number of teams want to work independently.
But what is the cost achieving run-time integration and independent framework versions?
JS frameworks intended to build SPAs have solved many problems like deep-linking between pages without reloading the application.
This talk will give you some real life experience which challenges are to be considered using different integration patterns, using webcomponents, module federation and "classic" libraries.

Target Audience: Architects, Developers, Project Managers
Prerequisites: Basic knowledge of Angular or other JS SPA Frameworks
Level: Advanced

Extended Abstract:
How often do project managers wish for a microfrontend architecture? Contrary to microservices in the backend, microfrontends are not always the recommended future choice.
You might have to solve a lot of problems, that have already been solved in frameworks like Angular or React.
If we start separating UI elements in encapsulated webcomponents, we risk a lot of effort re-creating capabilities like deeplinking (routing) or event handling across components.
Or: we need to add additional frameworks that solve the challenges of navigation, context transfer and layouting.
The talk provides an overview, what default architecture patterns Angular provides and how to mitigate problems that might come with classical architectures or a monorepo.
The talk will mention use cases, when the usage of microfrontends is feasible and recommended. It will also provide workarounds if a microfrontend architecture is needed.

A successful start-up was acquired and needed to scale to at least three times its size. Leadership, processes, tools and mindsets were not ready, nor aligned on how to make that transition. Through our work supporting them, the company changed, scaled and grew. The company did so well, that the leadership team eventually had the choice to leave, knowing their creation would thrive.

Target Audience: Leaders, Managers, Coaches, Decision Makers, CTO, Engineering Managers
Prerequisites: Basic Leadership experience
Level: Advanced

Extended Abstract:
As the company was still on the brink of scaling up and the CTO was very hands on and in control, our primary mission was to take him out of the process.
Because as good as he was, he was only one person. Which doesn’t scale and he set himself up to be THE bottleneck in the system.
So how could we leverage his skills and know-how, without making him an even bigger bottleneck and at the same time empower the team?
The company was fast paced, releasing software several times per day. They were extremely customer focused and gaining traction in the market at a high speed.
When we joined, we also became part of the rave party, building, testing and shipping so quickly. It was exhilarating
The problem was that the CTO acted as a final safety check. We got hired to make this scaleable: How?

• We identified the current situation, next steps and goals.
• We made strategic hires.
• We removed waste that kept us from our goal.
• We showed progress through useful data.

We like to call this ”Overcoming The End Boss”. Together, we learned his weapons, his moves, his strategies and devised ways to master them.
Step-by-step, the team grew in numbers and so did the quality of their work. So much so that the CTO at some point told us ‘It’s the first time in the 4 years since creating this start-up, I had time to mow my lawn.’
That’s when we knew our job was done.
In this talk we’ll take you on our journey from Quality Audit to making ourselves redundant. Our wins, our failures & our learnings.

This technical session aims to unravel the unique facets of Rust's memory management, including Ownership/Borrowing, Stack/Heap allocation, Reference Counting, and Lifetimes. Rainer Stropek aims to provide an in-depth understanding of these core elements and their interplay in providing memory safety, concurrency, and abstraction in Rust. This session, designed for developers with a strong programming background, will provide insight into the mechanisms that help Rust minimize common runtime errors.

Target Audience: Developers
Prerequisites: Strong development background
Level: Expert

Extended Abstract:
In the arena of systems programming, memory management is a fundamental concern. How a language approaches memory safety, concurrency, and performance has substantial implications for the efficacy of the programs it produces. Rust's unique approach to these concerns through its intricate yet robust memory management system is the focus of this technical session.
We will explore Rust's ownership rules which hinge on three key concepts: ownership, borrowing, and lifetimes. Rust's Ownership system is unique in its way of maintaining a clear distinction between mutable and immutable references and strictly enforces a single ownership policy to ensure safe memory access. We'll delve into the 'borrow checker' system, which keeps track of scopes to enforce these rules at compile-time, effectively minimizing runtime errors.
Next, we'll look at how Rust deals with memory allocation on the Stack and Heap, providing a safer and more explicit interface to these lower-level details. A clear understanding of these processes allows developers to write efficient, error-free code.
The session also takes an in-depth look at Reference Counting (Rc and Arc), Rust's form of memory management for data that has multiple owners. This approach ensures the automatic cleanup of resources, contributing to Rust's promise of memory safety.
Lastly, we'll dissect Lifetimes, a powerful concept Rust introduces to ensure references are always valid. By defining and enforcing Lifetimes, Rust ensures that memory safety is guaranteed without any cost to runtime performance.
This session is tailored for developers who already have a strong programming background and are considering delving deeper into Rust or are interested in the unique aspects of its memory management.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/rainer.stropek

"Which programming language is the fastest" usually is everyone's first thought when green software is mentioned! It's a common deduction that the fastest code is, therefore, the most efficient, which then, of course, can save us from this climate disaster. However, code efficiency is not even half of the story! In this talk, Sarah will review the three approaches that make software green. She will also introduce efficiency-achieving practices that can take us closer to fighting this pesky climate change.

Target Audience: Architects, Developers, SRE/DevOps
Prerequisites: Basic knowledge of any Programming Language, Introductory Familiarity with DevOps Space
Level: Basic

Extended Abstract:
In this talk, I will go over the following:

1. My journey so far with green software emphasizes how I don't need to leave my climate enthusiasm at home every day when I go to work
2. Brief facts about WHY we need to take action now in the tech industry
3. 3 approaches that make software green
4. Why code efficiency is not the answer to most green software problems with an example
5. Going over why DevOps practices are much more effective in achieving greenness in software with a couple of examples
6. Wrapping up with fruit for thoughts, especially highlighting the close connection between DevOps practices and Green Software practices
7. Encourage the audience to look at their software engineering problems through a green software lense

While AI systems differ in some points from "traditional" systems, testing them does not have to be more difficult - knowing the right questions to ask will go a long way. In this talk we will:

• Arm you with a checklist of questions to ask when preparing to test an AI system
• Show you that testers and data scientist have common ground when testing AI systems

Keep calm and test on - AI systems are not that different from "normal" systems.

Target Audience: Testers, Data Scientists, Developers, Product Owners, Architects
Prerequisites: Basic knowledge of software testing
Level: Advanced

Extended Abstract:
If you're a tester about to test your first AI system, or wanting to move into that area, you're probably wondering how you can prepare for the role. While we usually do not deal with complexity in the magnitude of Large Language models like chatGPT, AI systems still seemingly offer different challenges than "traditional" systems.
You're not the first person to deal with these questions. In fact, a group of us got together to explore it in more detail. Is there a general framework of questions that testers can use to help develop a quality strategy for systems that use AI? We wanted to see if we could design one. To this end, we got together a group with diverse roles: tester, test architect, data scientist, project lead and CEO.
Join us in this talk to hear how we approached the task and what our results are, including an example of using our checklist of questions to analyse a system that uses AI. Along the way we also addressed questions like "What is the role of a tester in such projects?" and "How much math do I need?" - we'll talk about those discussions, too. We encourage participants to use our checklist and give us feedback on it!

Expanding Horizons, the motto of OOP 2024, invites exciting thoughts about the future of software engineering. What will a developer's working day look like in 2034? What environments, tools, and practices will they use to create, test, deploy, and operate software? What will our daily lives look like in a digitalized world in 2034? What types of software systems will be everywhere? What systems will we use at work? What architectures and technologies do these systems rely on? Frank and Kevlin look into the future.

Target Audience: Anyone curious about the future of software engineering
Prerequisites: Interest and sound knowledge in software engineering, architecture and development
Level: Advanced

Extended Abstract:
Expanding Horizons, the motto of OOP 2024, invites exciting thoughts about the future of software engineering. What will a developer's working day look like in 2034? What environments, tools, and practices will they use to create, test, deploy, and operate software? What will our daily lives look like in a digitalized world in 2034? What types of software systems will be everywhere? What systems will we use at work? What architectures and technologies do these systems rely on?
The view is not always clear, but we can look at past and present trends to ask questions and make some forecasts. How will AI affect the daily work of developers, but also everyone else's work? Digitalization is affecting everyone from government to individual — how far will it have taken us by 2034? The last couple of years have seen a lot of media around cryptocurrency, Web3 and the Metaverse, but to what extent will these hopes and hypes actually have affected software development and software usage? What new trends can we expect to see in software architecture, programming languages and workplace culture?
Join Frank and Kevlin as they look into the future, a decade from now.

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

Data, the way that we process it and store it, is one of many important aspects of IT. Data is the lifeblood of our organizations, supporting real-time business processes and decision-making. For our DevOps strategy to be truly effective we must be able to safely and quickly evolve production databases, just as we safely and quickly evolve production code. Yet for many organizations their data sources prove to be less than trustworthy and their data-oriented development efforts little more than productivity sinkholes.

Target Audience: Developers, Data Engineers, DevOps Engineers
Prerequisites: Understanding of DevOps
Level: Advanced

Extended Abstract:
This presentation begins with a collection of agile principles for data professionals and of data principles for agile developers - the first step in working together is to understand and appreciate the priorities and strengths of the people that we work with. Our focus is on a collection of practices that enable development teams to easily and safely evolve and deploy databases. These techniques include agile data modeling, database refactoring, database regression testing, continuous database integration, and continuous database deployment. We also work through operational strategies required of production databases to support your DevOps strategy. If data sources aren’t an explicit part of your DevOps strategy then you’re not really doing DevOps, are you?

Security engineering from TARA and security requirements to security testing demand mechanisms to generate, verify, and connect the resulting work products. Traditional methods need lots of manual work and yet show inconsistencies and imbalanced tests. Generative AI allows novel methods with semi-automatic cyber security requirements engineering, traceability, and testing. In this industry presentation, we show two promising approaches with NLP and transformers and how to embed them into an industry-scale security pipeline from TARA to test.

Target Audience: Test Engineers, QA Experts, Security Experts, Requirements and Systems Engineers
Prerequisites: Some background on security and testing. We will hands-on introduce the AI methods.
Level: Advanced

Extended Abstract:
Security engineering from TARA and security requirements to security testing demand mechanisms to generate, verify, and connect the resulting work products. Traditional methods need lots of manual work such as for traceability and yet show little impact when looking at the many inconsistencies and imbalanced tests. NLP especially transformers allow novel methods with semi-automatic cyber security requirements engineering, traceability, and testing.
We focus here on using generative AI with NLP because they can support the methods described in the standard while there is no need to change the form of representation from what is required by cybersecurity standards and respective stakeholders. Especially the use of Large Language Models (LLM) for text generation, aggregation, and classification has recently proven promising to improve the efficiency and effectiveness of security analysis and tests.
Grey Box Penetration Testing is an approach where only publicly available information is used to perform an attack on the SUT. This often requires massive research effort. Threat catalogs were known and often used threats are recorded can increase the performance while testing. To provide additional aid we are currently working towards building an AI-supported threat catalogue. Therefore, we use a special transformer model which is specialized in searching and summarizing information. When fed with known information about the SUT this model searches all available databases like CVE or CAPEC, previously recorded attack patterns, and other contextual information available and gives the penetration test engineer an initial idea of how to approach an attack on the SUT.
Using the AI to generate both grey and white box attack paths is an approach to check how much information about the system or components such as libraries and dependencies which are used in the SUT are available. Having introduced these methods to the security life-cycle, we will in the next step better integrate the tools. This will facilitate a swift turn-around upon changes in an agile delivery pipeline and thus achieve consistency from TARA to security requirements and (regression) test cases.
Vector together with the University of Stuttgart has developed transformers and generative AI-based methodologies for the specification and validation of cybersecurity requirements with the goal to increase productivity and quality.
In this industry presentation, we practically show how generative AI can scale into an industry-scale security pipeline.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/christof.ebert

Die ideale Gelegenheit zum Netzwerken und Austauschen bietet die Welcome Reception. Lassen Sie den Konferenztag mit anderen Teilnehmern, Referenten, Ausstellern und Sponsoren bei Fingerfood und Getränken in der Expo ausklingen.

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.

The introduction of ChatGPT, CoPilot X brings in a lot of hype over developer experiences, especially documentation. But are we ready to chat with our documentation, instead of reading, using these tools? How can we, as maintainers, leverage these tools to offer a better experience in documentation for developers as our users? Join my talk and let's find out.

Target Audience: Engineers, Developers
Prerequisites: Programming
Level: Advanced

Discover the transformative power of GenAI in software testing. This lecture showcases a powerful GenAI-powered test framework that enhances testing efficiency. Learn how GenAI analyzes applications to generate automated test cases, uncover hidden defects with generative AI's random exploratory tests. Experience AI-powered peer reviewers for code analysis and quality evaluations. Explore Smart Report AI, providing comprehensive analysis and insights into test execution, results, and defects. Join us to revolutionize your software testing with GenAI.

Target Audience: Quality Engineers, Architects, Developers, Project Leader, Managers
Prerequisites: Basic knowledge on modern software development
Level: Advanced

Extended Abstract:
In the rapidly evolving landscape of software development Generative AI holds immense potential to revolutionize the field of software testing. This lecture aims to explore the transformative capabilities of GenAI in software testing by showcasing the powerful GenAI powered test framework and its key components.
The lecture begins by introducing the main framework, which combines the power of GenAI and automation to enhance the efficiency and effectiveness of software testing. Attendees will learn how GenAI can analyze the application under test and generate automated test cases based on a predefined test framework. These test cases can be executed locally or seamlessly integrated into DevOps processes, allowing for efficient and comprehensive testing of applications.
Furthermore, the lecture delves into the utilization of generative AI for the generation of random exploratory tests. By leveraging the capabilities of GenAI, testers can uncover hidden defects and vulnerabilities that may go unnoticed with traditional testing approaches. This demonstration highlights the innovative potential of GenAI in driving comprehensive test coverage.
Additionally, the lecture showcases the Smart Peer AI component of the framework. Attendees will discover how AI-powered peer reviewers can anticipate functional and non-functional issues, providing insightful code analysis and quality evaluations. By incorporating specific coding best practices, architectural standards, and non-standard attributes, Smart Peer AI enhances code quality and accelerates the development process.
Finally, the lecture concludes by presenting the Smart Report AI, an AI-powered solution that analyzes test reports generated from automated testing processes. This component provides a comprehensive analysis of test execution, environment configuration, test results, defect severity automated analysis, reproducibility steps, and suggestions for fixes. Smart Report AI empowers testers with valuable insights and facilitates effective decision-making in the testing and development lifecycle.

The Product Owner role in Scrum is vital, but lacks comprehensive guidance. This talk presents the SMIQ Method (Single Most Important Question), derived from the "48 hour book method," empowering Product Owners and Managers to translate customer needs into software requirements. It simplifies complex techniques into user-friendly steps for effective requirements engineering. The speaker's success in using this method for writing books, organizing conferences, and developing software highlights its simplicity and effectiveness.

Target Audience: Product Owners, Product Managers, Requirements Engineers, UX, Project Managers
Prerequisites: Scrum, Product Owner role in Scrum, beginner level knowledge of User-centered design
Level: Basic

Extended Abstract:
Product Owner is one of the most critical roles in the Scrum Framework. However, beyond “the backlog” and “prioritization”, there’s very little guidance as to what that role entails. This talk presents a method (The SMIQ or Single Most Important Question Method, discussed in the “48 hour book method”) that guides Product Owners, and Product Managers in their discovery work, and helps them translate customer needs into Software requirements. It’s a simple method, but it offers the opportunity for in-depth understanding and effective requirements management. The method achieves it’s simple format by codifying some complex techniques into a simple set of steps that anyone can use, and this speaker has used to write books, create conferences, and develop software.
Key Learnings

1. The challenge of understanding the customer, and what is required to succeed
2. How to translate real life into software requirements, reliably, and quickly
3. Concrete practices and techniques to implement the method suggested
4. Practical application of the SMIQ method in the conference room, with the participants
5. How to bring the SMIQ method to our work as Product Owners and Product Managers

Stoic practitioners know they cannot control circumstances, other people or rather... they know they cannot control anything outside of the realm of their own choices. So as a Stoic Product Leader you should stop focussing on outcome (!). Outcome is always outside of your control. However the CHOICES you need to make the product vision and goals ARE within your power, within your control. So the best thing you can do as a (product) leader is improving the quality of your decisions and teach your teams how to do that too.

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

Extended Abstract:
Stoic practitioners know they cannot control circumstances, other people, behaviour of other people in their teams, or simply: they know they cannot control anything outside of their own mind, the realm of their own choices.
So as a Stoic Product Leader you should stop focussing on outcome. Outcome is outside of your control as a leader. Your own choices are within your control. The choices you need to make in the long run (product vision) and the ones you need to make that are right in front of you (iteration goal).
So the best thing you can do as a (product) leader is improving the quality of your decisions and teach your teams how to improve their ability to make better choices.
(Sustainable) product leadership is far more like poker (with uncontrollable circumstances and emerging events that influence possible outcomes) than like chess (if you think long and hard you could predict what is the next best move).
* Learning goals

1. know how to move from outcome focus to focus on improving decision quality
2. know how to implement habits that will improve your decision making as a product leader

This session will help you make better, more sustainable product choices

This Special Day must be booked separately.
» Register now for free

In diesem Vortrag stellen wir eine agile DataGrid-Architektur vor, die Datenproblematik und typische Abhängigkeitsprobleme in der Welt der Microservices vermeidet.
Wir zeigen, wie wir zu einer etwas anderen Architektur kommen, die die Vorteile der Agilität mit den Anforderungen an Datenqualität und Konsistenz vereint.

Organizations are drawn to migrate their systems into the cloud, but in practice, cloud transformations do not always succeed in achieving the advantages often promised by cloud providers, such as scalability, availability, and cost effectiveness.
We give an overview over Kevin Hoffmann's fifteen factors for cloud-native applications and how they help us achieve success in our cloud migrations.

Target Audience: Architects, Developers, Operations, DevOps
Prerequisites: Basic understanding of web services
Level: Basic

Extended Abstract:
You think you are already reaping the cloud's harvest by lifting and shifting your apps to some cloud-provided VM or container infrastructure?
You've already read about Heroku's (original) twelve factors, maybe even skimmed though Kevin Hoffmann's book, and think your app is good enough, because you are using Git, have a CI pipeline, and someone in the team once ran the app in a Docker container?
Or you think your team isn't going to the cloud any time soon and this advice does not apply to you anyway?
Maybe you're right. Chances are, you are in for a surprise, though.
The original twelve factors for cloud-native application development are (reasonably) well established and widely agreed upon. Yet, in practice, there appear to be some misunderstandings regarding their meaning, and we see cloud migrations fail precisely due to reasons that could be avoided by following these factors correctly. The extension to fifteen factors by Kevin Hoffmann is less widely known, but no less important for modern, cloud-native application landscapes, especially since this extension also revisits and updates the original twelve factors.
The goal of this talk is to disseminate and discuss the fifteen factors, as well as to emphasize their interrelations and embed them in the greater context of modern application development, in order to help reduce pain for many teams tasked with bringing their software to the cloud.

Leaders should be passionate, think strategically and influence their people (a.k.a. followers).
How is that possible without empathy, self-consciousness & resiliency?
How is that possible without emotional literacy?
Spoiler: It isn’t!
But - god forbid - nobody wants to be labelled as “being emotional” at work, right?
Join me to leverage your emotional data as the true assets they are. Expand your horizon with serious psychological background and get some of my real-life rants on top for free (some of them I wish would better be fiction).

Target Audience: Developers, Architects, Managers of all flavours, Leaders of all kinds, curious human beings
Prerequisites: Curiosity and some work/project experience is beneficial
Level: Advanced

Extended Abstract:
I have to confess, the "true rants" will only be a side dish in this session.
You also will be learning - mainly about R.A.N.T.-based leadership, of course:
RA - I’ll showcase why Relation & Acceptance is the core of sustainable leadership.
N - You will learn why 'the Now' matters that much - and how to leverage your presence as a (seasoned) leader.
T - Because in the end, we all want to get the things that matter done. Together! Don’t we?

In today's economy, creating intelligent customer experiences is a key differentiator for organizations looking to compete and gain a competitive advantage. Use of AI and especially Generative AI became more prevalent in the business world. We will discuss some of the work we did on creating an AI-Driven CX Platform that offers data management, Customer360 views, personalization and chatbots infused with Generative AI, and advanced security features. We will also discuss practical use cases and outcomes of our approach.

Target Audience: Managers, Decision Makers, Leaders
Prerequisites: None
Level: Advanced

Many developers evoke technical debt to explain the misfortunes and troubles of their codebase and delivery. While unmanaged technical debt weighs down an architecture and exerts drag on its schedule, it is more often an effect than a cause. In this talk, we will look at what is and is not meant by technical debt with a view to properly attributing the root and recurring cause as technical neglect than technical debt. Without seeing technical neglect for what it is, we will continue to misattribute our problems to an effect rather than a cause.

Target Audience: Developers, Architects, Technical Managers
Prerequisites: Responsibility for software development, whether implementing it, guiding it or managing it
Level: Advanced

Extended Abstract:
Many developers evoke the mischievous spirit and day-to-day burden of technical debt to explain the misfortunes and troubles of their codebase and delivery. While unmanaged technical debt weighs down an architecture and exerts drag on its schedule, it is more often an effect than a cause. In this talk, we will look at what is and is not meant by technical debt — and other metaphors — with a view to properly attributing the root and recurring cause as technical neglect than technical debt. Without seeing technical neglect for what it is, we will continue to misattribute our problems to an effect rather than a cause.

This Special Day must be booked separately.
» Register now for free

Discover how to modernize legacy applications using Business API facades and hybrid architectures, leveraging the API-first approach and the Kong Gateway.

In this session, you’ll learn the benefits of Business API facades as an intermediary layer and the flexibility of hybrid architectures in transitioning from monolithic to microservices-based systems. You’ll also gain practical insights into successful modernization strategies, ensuring your organization's adaptability and competitiveness.

Although the term "Cloud Native" in the context of Java has been repeated ad nauseam for years, the JVM as a platform has only recently entered a phase where everything truly aligns with how cloud-native architectures are designed. Let's trace the path Java has already taken in recent years and take a look at what lies ahead in the future. During this presentation, you will learn about projects such as Leyden, CRaC, and GraalVM, and how they can realistically influence the way applications are developed.

Target Audience: Cloud Java Architectural Leads
Prerequisites: Basic Knowledge od Java, Cloud Challenges Experience
Level: Advanced

Extended Abstract:
The goal of the presentation is to provide a comprehensive overview of the evolution of Java in relation to cloud-native architectures. The presentation aims to educate the audience about the progress Java has made in recent years and shed light on the future prospects of the language.
By discussing key projects like Leyden, CRaC, Microprofile and GraalVM, the presentation intends to demonstrate their relevance and potential impact on application development. Ultimately, the goal is to inspire the audience to embrace cloud-native principles in their Java projects and adapt their development practices accordingly.

The voyage from transactional to transformational management often appears as intricate as navigating the intermingling of rivers and the sea. In estuaries' shifting currents, represent challenges, especially at the management level, entrenched in orthodox practices.
A fusion of two perspectives was our compass. It allowed us to interpret the undercurrents of change, discern the underlying constraints and constructors, and evolve a smaller, productive team from a larger non-functional gathering of agile coaches.

Target Audience: Architects, Developers, Project Leader, Manager, Decision Makers
Prerequisites: Openness towards lean-agile paradigms and new ideas
Level: Advanced

Extended Abstract:
In a world where business complexity is the new norm, the voyage from transactional to transformational management often appears as intricate as navigating the intermingling of rivers and the sea. This presentation offers a candid account of such a journey, steered by two diverse captains - an external 'hired gun' and an internal female coach - each lending a unique perspective to the transformational odyssey.
Diving into the deep waters of a highly customized SAFe transformation led by novices, our narrative begins in a domain adrift in a broader orthodox landscape. Bereft of an actionable vision and understanding of value streams, the task seemed daunting. Yet, armed with the principles of a 'learning organization' and lean-agile practices, we made headway at the team level.
But, like estuaries' shifting currents, our path was strewn with challenges, especially at the management level, entrenched in orthodox practices. The success we found came in surprising ways - liberating structures, team self-selection - hinting at a transformational undercurrent within the transactional tide.
Our unique pairing, a fusion of two perspectives, the male business-value-oriented external contractor view and the female internal Agile Coach with tons of experience from other companies, was our compass. It allowed us to interpret the undercurrents of change, discern the underlying constraints and constructors, and evolve a smaller, productive team from a larger non-functional gathering of agile coaches. Our distinct lenses, enriched by gender, background, and role diversity, empowered us to chart a path toward winning over the leadership.
Join us as we share this insightful journey, filled with lessons on harnessing the power of diversity in transforming orthodox management cultures into agile, learning organizations. Our narrative transcends our specific enterprise context to offer universal insights into the crucial paradigm shift to transformational management in digital transformations. Discover how you, too, can navigate the estuarine landscape of enterprise transformation, guided by the beacon of diversity, agile leadership, and a shared commitment to deliver business value.
In today's digital age, traditional management frameworks are increasingly insufficient to navigate the complexities of enterprise transformations. Agile leadership, combined with an understanding of transactional and transformational management, is not just beneficial - it's a necessity.
Our session, "Embracing Diversity in Enterprise Transformation: Navigating Change Through Estuarine Mapping and Agile Leadership", isn't just another tech talk or a repetition of known frameworks. It's a riveting journey through uncharted waters, guided by two different captains.
In a sea of sessions, ours stands out for its unique storytelling approach, applying the concept of Estuarine Mapping to understand the journey of transformation. We dissect a highly customized SAFe transformation, revealing the currents that steer the course of change and the guiding beacon that leads the way.
Our presentation is also an exploration of diversity - diversity in gender, roles, and experiences. Attendees get an intimate view of how different perspectives and skills converge and diverge, shaping the landscape of transformation and opening new channels of thought.
What You'll Take Away?
Attending our session will leave you with much more than just theoretical knowledge:
A New Lens: The application of Estuarine Mapping and Cynefin Framework in an enterprise context will provide a fresh perspective to view and understand organizational structures and transformations.
Diverse Insights: From the viewpoints of a male external consultant and a female internal coach, you'll gain unique insights into the challenges and triumphs of enterprise transformation.
Practical Strategies: Learn practical strategies to implement Agile Leadership and shift from transactional to transformational management, all backed by real-life examples.
Interactive Learning: Our presentation isn't a one-way street - you'll engage in discussions, exploring how these concepts can apply to your own use cases.
Inspiration: Hear a real-life success story highlighting the power of perseverance, innovation, and diversity in overcoming obstacles to change.
In a sea of options, choose a session that doesn't just teach - it inspires, challenges, and equips you to drive change in your organization. Choose a journey that ventures beyond the horizon of known waters into the uncharted depths of enterprise transformation.

Keeping up is the ultimate challenge for employees and companies within fields of massively fast-emerging trends shaping how to work and deliver. Learning and spreading expertise is also key to success while householding the knowledge of older technologies to maintain systems efficiently. The classic learning approach needs too much time to scale understanding and to adopt new technologies, especially remotely. It needed to be extended to a more self-defining and community-driven model with the ambition of being highly interactive and hands-on.

Target Audience: Engineering Manager, Agile Coaches, Employee Engagement, Senior & Executive Leaders
Prerequisites: None
Level: Advanced

Extended Abstract:
In our talk, we examine a case study on a three-year journey of creating, establishing and organically scaling a continuous learning community within GFK SE. The community started with two people and an idea – and is now an online event with hundreds of participants, from all over the globe!
But the talk doesn’t start with the solution! The story we would like to show you started in the darkness of two COVID-19 home offices occupying an MS Teams call. As was for many other people, the rash switch from mostly in-person, physically-centred collaboration to an environment that eradicated the physical elements of collaboration and made us all equally miserable, exposed a lot of practices that were not so visible before. So was the reality of learning in our company – people learned a lot from each other, but very localized, on a very small scale. Knowledge-sharing, workshops were done in groups of ca 5-10 people at most and were happening completely ad-hoc, all over the place, and as a result, topics would often be done multiple times even in the same physical location, with varying contents, recommendations and quality. With two words – it was all fragmented and invisible. On the other hand, as we went remote, it became really hard to do the same thing, so people, especially trainers, started complaining that it was so complex and time-consuming to do all this now via MS Teams. This is where the recognition started, that behind training content itself, there is so much more that impacts a successful or awful training experience.
Over the course of a few months, we gathered data, started a trainer community and came up with a lofty idea and a vision of what we wished to achieve.
When we started, we had three goals in mind:

1. Spread knowledge and skills efficiently to avoid reinventing the wheel
2. Contextualise learning – make not just the topic relevant, but take the examples, case studies and context for the sessions from our own “GFK kitchen”
3. Grow even more trainers and leaders – we ask trainers to come with a less experienced co-trainer who can in this way easily learn and practice how to be a trainer, gaining leadership skills

In addition to that, we also envisioned some benefits that would come from the unique synergies of the format – building trust, expanding people’s networks into other locations and work contexts through participating in a safe, learning-centred environment; breaking down functional silos more and more through continuous exposure into different areas and problem spaces; employee retention through an opportunity to recognize, grow and engage employees that were very interested in being trainers or mentors.
We were two people, and immediately everyone around us said it can’t be done. As we are in a talk about our success story, obviously we faced mountains of issues and our enthusiasm and idea almost died at one point, but we did it and are here to share with you all the nitty and gritty details, drama and recipes on how to make this happen!

This session will introduce embedding vectors and their use in artificial intelligence. It will illustrate how these constructs can be effectively utilized in enterprise AI solutions, specifically in conjunction with prompt engineering. Rainer Stropek will present practical demonstrations using Microsoft's Azure Cloud and OpenAI's ChatGPT 4 model, showcasing real-world application scenarios and potential business benefits. Attendees will gain insights into emerging AI trends and practices in enterprise contexts.

Target Audience: Architects, Developers, Data Scientists
Prerequisites: Basic knowledge about LLMs, ability to read source code
Level: Advanced

Extended Abstract:
This session aims to demystify the technical concepts of embedding vectors and their integration into the Artificial Intelligence (AI) world, with a specific focus on enterprise applications.
We provide an accessible introduction to embedding vectors – the mathematical constructs that translate complex data types into a format that machine learning algorithms can comprehend. Attendees will grasp the foundational principles of embeddings and their pivotal role in enhancing the capabilities of AI algorithms.
Next, we delve into the realm of prompt engineering. Here, we explore how the strategic crafting of prompts can steer AI models, such as OpenAI's ChatGPT 4, toward generating more precise and contextually accurate responses. We'll explain the process and strategies involved in prompt engineering, offering a roadmap for businesses to adopt these practices effectively.
Rainer Stropek will demonstrate these principles in a practical setting using Microsoft's Azure Cloud. We will walk through real-life scenarios, showing how enterprises can implement such technologies.
The session targets AI enthusiasts, software architects, developers, and data scientists. By the end of this session, participants will have gained a better understanding of these AI concepts, and how they can be harnessed.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/rainer.stropek

Xin has lived and breathed DDD for more than a decade. Drawing on her experiences, Xin makes a case for DDD’s rising relevance in a post-modern world, where aging companies struggle with aging software, while adding new software and complexity to their IT portfolio. With good attractor effect DDD is evolving from a software-centric design discipline to a multi-dimensional toolbox. Join Xin to reflect together on, how DDD can help us sustain meaning and productivity in a reality of vast sociotechnical complexity and constant change.

Target Audience: Software Professionals, Architects, Leaders, Agile Practitioners, Change Agents, Facilitators
Prerequisites: Basic DDD understanding; Prior DDD experience is not a must but helps understand the deeper message
Level: Advanced

Extended Abstract:
What is the first thing that comes to mind when you hear the word DDD – Domain-Driven Design? The geeky technical patterns (Value object, Entity, Aggregate, etc.)? Walls decorated with colorful event storming stickies? A miracle cure to rescue change initiatives in large companies? Or are you thinking of a software development method born in the pre-cloud and pre-microservice era, which after 20 years is still struggling to gain traction?
Xin has lived and breathed DDD for more than a decade. In this talk, Xin makes a case for DDD’s rising relevance in a post-modern world, where aging companies struggle with aging software, while adding new software and complexity to their IT portfolio. The reflections will be grounded in solid DDD experiences and observations from the battlefield. With good attractor effect DDD can evolve from a software-centric design discipline to a multi-dimensional toolbox of thinking, modeling and collaboration techniques. You will be invited to explore DDD's value proposition and reflect upon how to leverage DDD’s strategic and tactical design approaches in your own context.
Globally, there is an increasing interest in DDD. Hope is evergreen for DDD to become a key ingredient in the magic potion for tackling the increasing complexity, not only at the heart of software, but also at the heart of sociotechnical organizations. How can DDD help us create meaning and productivity in a reality of multi-dimensional complexity and constant change? What’s in it for me? What’s in it for us?

In the evolving AI landscape, the EU AI Act introduces new standards for assuring high-risk AI systems. This presentation will explore the tester's role in navigating these standards, drawing from the latest research and from our experiences with an Automatic Employment Decision System, a high-risk AI. We'll discuss emerging methodologies, conformity assessments, and post-deployment monitoring, offering insights and practical guidance for aligning AI systems with the Act's requirements.

Target Audience: QA Professionals, AI Engineers/Architects, Business Leaders, POs/PMs, Policy Makers
Prerequisites: Basic Understanding of AI, Familiar with Testing, Awareness of EU AI Act, Interest in AI Asurance
Level: Advanced

Extended Abstract:
As the landscape of Artificial Intelligence (AI) rapidly evolves, the upcoming EU AI Act is set to introduce a new paradigm for assuring high-risk AI systems. This session will allow participants to delve into the pivotal role of testers in this context. We will decode the complexities of the Act and get to see how fostering the Act will ensure robust, transparent, and ethically aligned AI systems.
Drawing on recent research and my own experience in testing high-risk AI systems, I will discuss the emerging methodologies for testing high-risk AI, including explainability methods, robustness testing, and fairness testing. Together, we will also explore the Act's emphasis on conformity assessments and post-deployment monitoring, highlighting the tester's role in these processes. Participants will gain a unique behind-the-scenes look at how we have gone from chaos to order in testing an Automatic Employment Decision System, a high-risk AI.
Joining this session will equip participants with valuable insights and practical guidance on aligning AI systems with the EU AI Act. This is a must-attend for testers, AI developers, and business leaders alike who are navigating this new frontier, exploring the challenges, opportunities, and future directions in the assurance of high-risk AI systems. By the end of the session, participants will be better prepared to face the challenges posed by the EU AI Act and will have a clear understanding of the future directions in the assurance of high-risk AI systems.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/andrei.nutas

While AI-assisted programming tools like GitHub Copilot have gained popularity and acceptance within the developer community, they represent just the tip of the iceberg when it comes to the potential of AI in software development. In this keynote, Daniel will shed light on why the present moment is the perfect time for developers to immerse themselves in creating AI applications. Furthermore, he will provide insights into the next steps developers should take to stay ahead in this rapidly evolving field.

A main theme in modern architectures is around fine-grained, isolated, reactive components, that are managed by autonomous teams (think microservices). This is considered key to decoupling, which, in turn, leads to business agility. Unfortunately, this often goes wrong and people end up with more tightly coupled systems, that are hard to understand and change - the opposite of agility. In this talk, I will explore why this happens and provide my view on how process orchestration can improve the situation without harming any good architecture.

Target Audience: Architects, Lead Engineers, IT Decision Makers
Prerequisites: Basic knowledge in Microservice architecture
Level: Basic

Extended Abstract:
I will walk you through the challenges around event-driven systems and microservices, talking about orchestration and choreography, also showing you how to balance both architectural approaches.
I will further discuss the importance of looking at end-to-end processes before going into local automations, as local optimizations can actually harm the global result.
I will further compare different approaches to automate end-to-end processes, from batches over streaming to workflow engines. You will understand the impact on agility and get guidance on decision criteria, backed by examples collected in various real-life projects.
I will sketch what influence those architecture decisions have on the governance and enterprise architecture of organizations.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/bernd.ruecker

Architecture work has to balance providing clear guidance for important decisions with empowering people to build their aspects of the system without interference. In this session we'll explore how security principles can help achieve this for application security. The talk explains how principles can guide design decisions without being too prescriptive and explains a set of ten proven principles for designing secure systems, distilled from security engineering practice but presented in accessible language for the working software architect.

Target Audience: Architects, Developers, Testers, Project Managers
Prerequisites: Some experience in developing large scale systems
Level: Advanced

Extended Abstract:
Security is an ever more important topic for system designers. As our world becomes digital, today’s safely-hidden back office system is tomorrow’s public API, open to anyone on the Internet with a hacking tool and time on their hands. So the days of hoping that security is someone else’s problem are over.
The security community has developed a well understood set of principles used to build systems that are secure (or at least securable) by design, but this topic often isn’t included in the training of software developers, assuming that it’s only relevant to security specialists. Then when principles are explained, they are often shrouded in the jargon of the security engineering community and so mainstream developers struggle to understand and apply them.
In this talk, we will introduce a set of ten key, proven, principles for designing secure systems, distilled from the wisdom of the security engineering community. We’ll explain each principle the context of mainstream system design, rather than in the specialised language of security engineering, explaining how it is applied in practice to improve security.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/Eoin.Woods

"Σπεύδε βραδέως" in ancient Greek, or "festina lente" in Latin translates as "hurry slowly" an oxymoron saying to indicate the need for balancing deliberation and urgency.
In this talk we comment on the prevailing perceptions relating to speed of software development and how in a DevOps context what sometimes is perceived as fast from an individual's perspective has a deleterious effect on team performance while practices traditionally viewed by developers as cumbersome have in fact a positive effect on team performance and effectiveness.

Target Audience: Software Engineers and DevOps Practitioners
Prerequisites: None
Level: Advanced

Extended Abstract:
The talk draws on the experience of multiple projects but uses the team setup and 2020/2021 data of the NHS Covid19 app's backend services teams as a showcase for a team that managed to avoid neglecting subjects like peer reviews, documentation, testing etc. in a high pressure, high pace environment.

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.

One of the fundamental challenges for machine learning (ML) teams is data quality, or more accurately the lack of data quality. Your ML solution is only as good as the data that you train it on, and therein lies the rub: Is your data of sufficient quality to train a trustworthy system? If not, can you improve your data so that it is? You need a collection of data quality “best practices”, but what is “best” depends on the context of the problem that you face. Which of the myriad of strategies are the best ones for you?

Target Audience: Developers, Data Engineers, Managers, Decision Makers
Prerequisites: None
Level: Advanced

Extended Abstract:
This presentation compares over a dozen traditional and agile data quality techniques on five factors: timeliness of action, level of automation, directness, timeliness of benefit, and difficulty to implement. The data quality techniques explored include: data cleansing, automated regression testing, data guidance, synthetic training data, database refactoring, data stewards, manual regression testing, data transformation, data masking, data labeling, and more. When you understand what data quality techniques are available to you, and understand the context in which they’re applicable, you will be able to identify the collection of data quality techniques that are best for you.

Frauen verändern die Technik. Wir bestärken Frauen in der IT-Branche darin, sich zu beteiligen und ihrer Stimme Gehör zu verschaffen. Nehmen Sie am Mittwoch, 31.01. ab 18:30 Uhr, an unserem Treffen teil, um Ihre Erfahrungen in einem geschützten Raum zu teilen und Ihre technische Stärke mit uns auszubauen.

Women are changing technology. We encourage women in the IT industry to participate and make their voices heard. Join our meeting on Wednesday, 31 January from 6.30 p.m. to share your experiences in a safe space and build your technical strength with us.

We are looking forward to hear your inspiring stories! Maybe you would like to tell us how you apply technology towards sustainability, or to prevent and find resilience in front of environmental disasters, or maybe you just want to inspire and encourage others by telling us about your career progression in IT!

(This meetup will be held in mainly in English, of course networking can be in both German and English.)

• Hype Women! — F/X-sisterhood for a socially sustainable IT-community (Maryse Meinen)
• The impossible dreams! (Graziela Simone Tonin)
• Passkeys — the Swiss army knife for web authentication? (Sonja Scheungrab)
• Breaking the Silence: Inspiring women in tech to shine on stage! (Mirna Alaisami)

Henning (OO to the core) and Mike (ferociously FP) agree on all the fundamentals of software architecture, but when it comes to designing models, they can't seem to find common ground.
OO and FP folks like to congratulate themselves on how well they go together - and how OO languages are accreting one feature after another from the FP world.
Henning and Mike will highlight how OO and FP approaches to design differ, and offer possible approaches to unifying both for mutual gain and insight.

Target Audience: Architects, Developers
Prerequisites: Experience in OO or FP
Level: Advanced

Extended Abstract:
Much work remains to unify these two worlds:

1. OO folks are weary of premature abstractions, whereas FP folks tend to abstract early.
2. While both camps prefer operation-rich models, the approaches to designing these operations are incompatible. Specifically, the BDD and TDD approaches favored by the OO folks are incompatible with the design recipes approach preferred by the functional camp.
3. Paradoxically, OO - which is supposed to be about objects - espouses BDD which is about functions, whereas FP has a rich tradition in data design, i.e. objects.
4. In OO, objects populate the domain, and they are encapsulated and thus isolated, whereas in FP this encapsulation is an emergent (or not emergent) phenomenon.
5. OO is inherently stateful, and FP is inherently stateless. This naturally leads to very different approaches to interface design, and more importantly, to the use of types.

Mehr Inhalte dieser Speaker? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/michael.sperber; https://www.sigs.de/autor/henning.schwentner

Expanding horizons has many facets. It means taking advantage of new opportunities that arise from technical progress, such as Large Language Models, or societal challenges like Sustainability. Expanding horizons also means taking responsibility. AI and data analytics have a direct impact on our future life, good and bad. Expanding horizons also means reflection on existing practice. We have perhaps forgotten the benefits of structured monoliths, or have sometimes overdone it with agility, which suggests a critical and learning retrospective.

Moderation: Frank Buschmann
Panelists: Isabel Bär, Zoe Lopez-Latorre, Carola Lilienthal, Xin Yao

Target Audience: Software Practitioners
Prerequisites: None
Level: Advanced

Extended Abstract:
The motto of OOP 2024 has many facets. Expanding horizons means understanding and taking advantage of new opportunities that arise from technological progress or societal challenges. For example, on Large Language Models, Sustainability, and the Metaverse. Expanding horizons also means taking responsibility and not blindly applying new technologies. For example, AI and data analytics have a direct impact on our future life and social interaction. With all the consequences, good and bad. But broadening horizons also means reflecting on existing technologies and practices. In the course of the euphoria about microservices, for example, we have perhaps forgotten the advantages of the structured monolith too much, or have sometimes overdone it with agility. A critical and learning retrospective seems appropriate.
In this panel, we will examine the various aspects of the motto of OOP 2024 to give us all meaningful guiding thoughts for the exciting journey to expanding our horizons.

Most engineers know that improving their presentation skills would be good for their career but feel naturally uncomfortable on stage. So how do you improve this skill? As a former opera singer turned software engineer, Anna McDougall runs regular public speaking workshops for her colleagues. In this session, she explains how to encourage your team (or yourself!), provides a demo coaching session with Software Engineer Ellina Nurmukhametova (who will present an AI quiz feature), and demonstrates how to get comfortable on a stage.

Target Audience: Developers, Project Leaders, Managers, Architects
Prerequisites: None
Level: Advanced

Designing good applications has become more demanding than ever: Extremely flexibility. Super-fast to change. Never down. Increasing user demands. Sustainability. Fewer developers. More AI. The list appears to be endless.
Many demands have not existed 10 or 15 years ago. Some have changed dramatically. Still, the discussions regarding architecture barely reflect that. In this session, we will take a look at how the architectural demands have changed and how to tackle the challenges of today best.

Target Audience: Architects, Senior Developers, Decision Makers
Prerequisites: Sound architectural knowledge makes the ideas presented easier to grasp
Level: Advanced

Extended Abstract:
Designing good applications has become more demanding than ever: Extremely flexibility. Super-fast to change. Never down. Demand-based scaling. Increasing user demands. Sustainability. APIs as first class citizens. Secure like a fortress. Fewer developers. More AI. The list appears to be endless.
Many of today's architecture demands have not existed 10 or 15 years ago. Some have changed dramatically. Still, most discussions regarding architecture seem to be stuck in the early 2000s.
In this session, we will take a look at how our application design demands have changed, what it means today to design good applications and how to tackle the challenges best.
Let us catch up together and learn what architectural work today means!

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/uwe.friedrichsen

Continuous Software Architecture is an approach to software architecture that tries to move architecture from a set of up-front blueprints to a continually developed set of architectural knowledge and decisions. While a simple idea, actually putting it into practice can be difficult. In this talk we will briefly recap the idea of Continuous Software Architecture and then explore the key practices that are usually needed to achieve it, as well as the common problems and how to address them.

Target Audience: Architects, Developers, Technical Project Managers
Prerequisites: Some familiarity with agile development and modern architecture practice
Level: Advanced

Extended Abstract:
Continuous Software Architecture is a philosophy and approach to software architecture that embraces the fact that doing most of the design before the implementation does not work very well, and perhaps never did. The approach tries to move architecture to a continually developed set of architectural knowledge and decisions, stressing collective ownership of the resulting architecture. This talk will provide attendees with practical and actionable advice on implementing the five key practices of Continuous Architecture: Technical Leadership, Achieving Quality Attributes, Driving Design Decisions, Managing Technical Debt and Implementing Feedback Loops.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/Eoin.Woods

Most current UI libraries provide great user experience with a vast of components. But when it comes to heavy customization and non-standard scenarios, especially for E-Commerce, they become hard to manage, scale or even slow down performance. How to create a UI library that provides users the most possible freedom in customizing components, while keeping our performance and scalability to the fullest? How much customization freedom is enough? That's what my talk is about.

Target Audience: Developers, Architects, Project Leader
Prerequisites: JavaScript
Level: Advanced

Last year in open source, we saw the compliance threat shift from license violation to contract violation, we saw the rise of the bill of material as a purchasing requirement, and we saw the continued growth of source-available licenses. If you don't know what I'm talking about, you really need to attend, because your business is at risk if you don't understand these changes. In this annual talk, I will review the last year and speculate about what the future may bring.

Target Audience: Product Leaders, Engineering Leaders, Architects, Developers, Enthusiasts
Prerequisites: Basic understanding of open-source software development
Level: Advanced

During the talk, we'll dive into the historical context of Generative AI and examine their challenges. From legal compliance to fairness, transparency, security, and accountability, we'll discuss strategies for implementing Responsible AI principles.
It's important to note that the landscape for AI-driven products is still evolving, and there are no established best practices. The legislative framework surrounding these models remains uncertain, making it even more vital to engage in discussions that shape responsible AI practices.

Target Audience: Decision Makers, Developers, Managers, Everyone - AI-driven products require cross-functional teams
Prerequisites: None
Level: Basic

Extended Abstract:
Foundation models like GPT-4, BERT, or DALL-E 2 are remarkable in their versatility, trained on vast datasets using self-supervised learning. However, the adaptability of these models brings forth ethical, socio-technical, and legal questions that demand responsible development and deployment.
During the talk, we'll delve into the history of AI to better understand the evolution of generative models. We'll explore strategies for implementing Responsible AI principles, tackling issues such as legal compliance, fairness, transparency, security, accountability and their broader impact on society.
It's important to note that there are currently no established best practices for AI-driven products, and the legislative landscape surrounding them remains unclear. This underscores the significance of our discussion as we collectively navigate this emerging field.

Are Large Language Models (LLMs) sophisticated pattern matchers ('parrots') without understanding or potential prodigies that eventually surpass human intelligence? Drawing insights from both camps, we attempt to reconcile these perspectives, examines the current state of LLMs, their potential trajectories, and the profound impact these developments have on how we engineer software in the years to come.

Target Audience: Developers and Architects
Prerequisites: A basic understanding of Large Language Models is helpful but not required
Level: Basic

Extended Abstract:
Large Language Models (LLMs) are complex 'black box' systems. Their capabilities remain largely mysterious, only beginning to be understood through interaction and experimentation. While these models occasionally yield surprisingly accurate responses, they also exhibit shocking, elementary mistakes and limitations, creating more confusion than clarity.
When seeking expert insights, we find two diverging perspectives. On one side, we have thinkers like Noam Chomsky and AI experts such as Yann LeCun, who view LLMs as stochastic 'parrots' — sophisticated pattern matchers without true comprehension.
In contrast, AI pioneers like Geoffrey Hinton and Ilya Sutskever see LLMs as potential 'prodigies' — AI systems capable of eventually surpassing human intelligence and visionaries like Yuval Noah Harari that view LLMs as substantial societal threats.
Regardless of whether we see LLMs as 'parrots' or 'prodigies', they undeniable are catalyzing a paradigm shift in software engineering, broadening horizons, and pushing the boundaries of the field.
What are the theories underpinning these experts' views? Can their perspectives be reconciled, and what can we learn for the future of software engineering?
To answer these questions, we examine the current capabilities and developments of LLMs and explore their potential trajectories.

In a microservices architecture, services shall be as loosely coupled as possible. Still, they need to communicate with each other in order to fulfill business requirements. Now there are so many questions around this communication (synchronous vs asynchronous, event-driven? what is the influence on the coupling of your services? ...?). This talk will help you answer these questions for your project. You will better understand not only the architectural implications but also the effect on the productivity of your teams.

Target Audience: Architects, Engineers, Developers
Prerequisites: Basic experience with distributed systems
Level: Basic

Extended Abstract:
In a microservices architecture, services shall be as loosely coupled as possible. Still, they need to communicate with each other in order to fulfill business requirements. Now there are so many questions around this communication:

1. What are the general possibilities to communicate? For example synchronous, asynchronous, or event-driven communication. What are the tradeoffs and which communication style should you prefer?
2. What is the influence on the coupling of your services? For example, asynchronous communication reduces temporal coupling between services.
3. What do I have to consider when selecting a certain communication style? For example, you need to apply certain resilience patterns if you want to use synchronous communication.

This talk will help you answer these questions for your project. You will better understand not only the architectural implications but also the effect on the productivity of your teams.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/bernd.ruecker

Are you lost when folks talk about "quality" in the context of software? Just when you thought "high quality" means "good" and "QA" means "assure it's good", somebody hits you over the head with ISO 25010, where "quality" is just a neutral property of a software system. It's all a big happy pile of terminology quicksand where you sink faster the more you struggle for unambiguous and clear definitions. But we're here to help you out. We'll be looking at what's relevant about quality from a software architecture perspective.

Target Audience: Architects, Developers
Prerequisites: None
Level: Basic

Extended Abstract:
Among the prominent confusions is "quality requirements" vs. "functional requirements" - someone is sure to tell you that the first one is something not entirely unlike “non-functional” requirements. But if that distinction even is a thing, what's that "functional suitability" category of the ISO 25010 quality model? And where exactly do requirements even enter the picture? Once they do, how do we tell whether they are satisfied or not? And if they're not, how does all this terminology help with devising tactics for making things better? We'll separate out the taxonomy from the metrology, the metrology from the requirements, the functional from the non-functional (as far as this makes sense) and everything in between. We'll survey different ways of looking at quality and identify the murky areas where you need to be explicit about what you mean.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/michael.sperber

This talk is about my journey as a Scrum Master towards creating sustainable DevOps teams. I will share my learnings and inspire the audience to raise awareness on sustainability in their own teams and organizations.
We will have a look at IT (and our own work) through the generational lens, to discover how long-term thinking can reshape the way we look at our daily work and help us find strategies for making IT sustainable.

Target Audience: Architects, Developers, IT Managers, Agile Professionals
Prerequisites: None
Level: Basic

Extended Abstract:
Climate change is a significant threat to the future of life on earth and as I was looking for ways to become more sustainable, the idea started to grow that at work, in my own DevOps teams, we could also take the sustainability perspective. I dove into the subject of sustainable IT and started with a ‘Planet as a Stakeholder Retrospective’ for my Scrum Team in which we went over the Principles of Green Software Engineering. We discussed what steps our team could take to reduce the carbon footprint of our services.
Taking the sustainability perspective was a new approach for the team, but everyone agreed on its importance. During that session, the team estimated that optimizing our landscape and decommissioning legacy components could reduce our footprint by a significant percentage!
Just imagine: what if all DevOps teams would do that? I started to give workshops about ‘the Planet as a Stakeholder’, in which I help teams to look at their IT services through the sustainability lens and let them define the first steps forward.
In this talk I will share my experiences: failures, challenges, successes, and examples of practical steps that teams have already taken to reduce their carbon footprint.

Managers and leaders worldwide struggle to decide between projects A, B, or both. Traditional estimation techniques fail because humans can't predict the future. This talk proposes a simulation-based approach inspired by investment strategies, industrial management, and poker playing. By leveraging AI, forecasting, and computing power, simulations offer a reliable and adaptable portfolio planning strategy. Rather than relying on human estimation, simulations streamline decision-making and provide reassurance.

Target Audience: Portfolio Managers, Product Leaders, CPO, CEO, CTO, Product Managers, Product Owners
Prerequisites: Beginner level probabilistic forecasting, familiarity with portfolio level decisions
Level: Basic

Extended Abstract:
Right now, around the world, managers and leaders are scratching their heads to try and answer the question “Should we take project A, B, or both?”. The techniques they are using, are woefully inadequate to answer their question because they rely on a skill humans don’t possess: predicting the future!
Estimation as a portfolio and risk management strategy relies on our ability to predict the future. But we don’t have that skill! What can we use instead then?
In this talk, we explore how we can learn from the world of investment (risk management), industrial management (process control), and poker playing (thinking in bets) to create a powerful simulation strategy that will streamline and reassure your portfolio planning team. Unlike humans, simulation can take as many ideas as you can throw at it, and can come up with the most likely winning scenarios quickly, repeatably, and is infinitely adaptable to future surprises.
Why rely on estimation when we can rely on AI, Forecasting, and the near-infinite computing power we have in even the most humble of spreadsheet programs?
Key Learnings

• Basics of simulating portfolio decisions
• Comparing simulation vs estimation for portfolio level decisions
• Examples of simulation use in complex scenario assessment, with N >> 1 options for decision
• How to effectively support decision making with simulation.

I think differently. Why? I have a combination of ADHD and autism incl. high sensitivity - also known as "neurodivergent". I want to share my personal story which strategies and characteristics are helping me finding my career path. I hope to inspire some of my fellow testers, especially those who also sometimes feel different. I'd like to make a stand that some typical qualities make neurodivergent people especially valuable in testing. I want to widen the horizon for colleagues and companys on what they can do to appreciate them and others.

Target Audience: Tester, Test Manager, Developer, Team Leads, HR
Prerequisites: None
Level: Basic

Extended Abstract:
Ever felt different or worked with someone who you couldn’t understand? Who seemed to think somehow unlike than you? Maybe they did indeed. Are you aware that there are two main categories of human thinking: neurotypical and neurodivergent? Whereas neurotypical thinking is often described as “linear thinking” neurodivergent thinking is more “cross-linked”. And even within these categories we have a broad spectrum of diversity. I am fascinated by the differences in behavior and perception of the world that results out of this important detail.
I think differently. But that's not all. I behave differently and I have different needs. Why? I recently discovered that I have a combination of ADHD, autism incl. high sensitivity. But I adapted to the world as it is and blended in. That makes me a perfect fit for an agile environment where adapting to changing circumstances is key. I blame this part on my ADHD brain that loves discovering new things. My autistic brain on the other hand hates changes. So, I consider myself lucky that I have both of them. I developed a lot of implicit strategies to cope with it. To give an example: My family was always wondering why I used check lists so extensively, even as a child. Now I know: That was my autistic side bringing my chaotic ADHD brain under control.
I would like to share my personal story which strategies, characteristics and external enabler are helping me finding my career path. For instance, how I got from the awkward little girl that hid in the bushes to being voted “the most ‘daydreamer’” in school to me giving speeches in front of hundreds of people and taking leading roles in an international consulting company. It is a story on how I get to shine in a branch of extroverts. I hope to inspire some of my fellow testers, especially those who also sometimes feel different. I'd like to make a stand that some typical qualities make neurodivergent people especially valuable in the testing world.
Perhaps it is time to say goodbye to "linear thinking" and premature judgments. Especially in IT we can benefit a lot if we widen our view and enable change by looking beyond the horizon. That starts with acceptance - even for different ways of thinking.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/Viviane.Hennecke

Artificial Intelligence (AI) has become integral to software development, automating complex tasks and shaping this field's future. However, it also comes with challenges. In this talk, we explore how AI impacts current software development and possibilities for the future. We'll delve into AI language models in programming, discussing pros, cons and challenges. This talk, tailored to both supporters and skeptics of AI in software development, doesn't shy away from discussing the ethical obligations tied to this technology.

Target Audience: Software Engineers, Architects and Project Leaders in an enterprise environment
Prerequisites: Basic Understanding of Software Development
Level: Advanced

Extended Abstract:
The integration of Artificial Intelligence (AI), especially AI language models, is fundamentally reshaping the landscape of software development. This transformative technology offers exciting possibilities, from enhancing developer productivity to simplifying complex tasks. However, it is crucial to acknowledge and address the inherent challenges that accompany these advancements.
In this session, we delve into AI's role in software development, emphasizing both the potential benefits and potential drawbacks of AI. We will also examine the ethical implications of this technology.
By the end of the session, attendees will have a comprehensive understanding of AI's role in software development, reinforced by practical demonstrations. Participants will gain insight and skills for their daily roles as well as strategies for adopting and applying AI within their software development context.
As AI continues to permeate software development, understanding its potential and preparing for its challenges has become vital. My session, directly tied to the conference theme of "Expanding Horizons", provides unique, practical insights to help attendees navigate an AI-integrated future. Join me in encouraging the responsible and effective use of this transformative technology.

**TL, DR;** Embrace no-code to explore more models and throw most of those models away. You will quickly discover what works, and what matters, in the business process that you are automating. If it matters enough, you can extract it into a high-fidelity design in code.

Target Audience: Everyone with a stake in the software production process
Prerequisites: None
Level: Basic

Extended Abstract:
Many software projects still consume considerable resources, and take a long time before anything material is put in the hands of the end-user. At a smaller scale this happens with teams that have the ambition to adopt Domain-Driven Design principles but that lack the expertise and experience in how to approach the design process. There is a spectrum of mistakes. On one hand there is the lack of producing a meaningful and shared model that is able to unify the conflicts and handle the complexity that the messy world will serve the system. On the other end of that spectrum there is analysis paralysis: a model that never sees the light of day, because there is always a new case it cannot handle. If the team doesn't produce a meaningful model, or if it fails to put that model in front of experts early on, then the team robs itself of precious feedback. "Judge models by their usefulness" is a mantra that is difficult to live by, if the model isn't being used...
Despite warnings, teams design big architectures early on, to support even bigger ambitions of the organization they work for, but they forget that it's not the architecture that the end-user cares about. With every bit of structure that is added early on, the team reduces the degrees of freedom to evolve the system at a later point in time. In order to support long-lasting design that is attuned to the environment, teams should set architectural principles that allow for a helpful structure to emerge, regardless of the platform.
> **No code** has entered the chat...
For a while now, no-code vendors have been telling organizations that they shouldn't be limited by expensive software engineers to build systems that are useful. No-code aims to commoditize the software production process. Commodification of technology leads to value if it removes a limitation, but successful adoption only works if the rules and policies that initially helped us overcome the limitation are replaced as well. Practices such as DevOps have to be adopted in order to reap the benefits of the commodification of compute and storage in the cloud. In order to benefit from serverless, system components need to be decoupled through message-driven designs. In order to benefit from no-code, people have to organize around the software production process in a different way.
Within software engineering communities no-code has been dismissed as a fad, saying the need for writing code will never go away because the needs of most software systems are too complex to capture in a visual design environment. This viewpoint ignores the argument that software engineers act as a gatekeeper, a limitation for the stakeholder to get what they want. It is reductionist to say that no-code means no-code. No-code is as much about no-code, as wireless is about the absence of wires, or serverless is about the absence of servers. No-code means less boilerplate. And no-code does NOT mean no-model.
The inability to deliver meaningful results in a reasonable amount of time is never out of bad intent, it's the consequence of rigidity in the system of work. If there is no room for experiments, for error, for trying again, then we shouldn't be surprised if people attempt moonshots. But if we can reduce the cost of experiments, then we should be able to iterate more, learn faster, and as a consequence produce more value.
Let's explore how no-code is able to remove the time to market of our ideas to explore new models. Join this session to uncover which rules, policies, and practices around modeling and design need to be replaced in order to reap the benefits that no-code has to offer.

I’m an architect, and I think a lot about architecture. Mostly I think about how irrelevant architecture is if it doesn’t get shipped to production. I worry a lot too. I worry about how to help all the teams I’m supposed to be helping, without slowing them down, getting in their way, or making their lives harder rather than easier.

Traditional (i.e. hands-off, blessed-few) approaches to architecture rarely (if ever) work. But in the world of microservices, autonomous teams, and continuous delivery, architecture is more important than ever. Is there an alternative?

This keynote will introduce you to a method and an associated set of practices which do away with the traditional idea of “Architects” while bringing the practice of “Architecture” to the fore. I’ll explain how everyone can become an architect, without things reducing to chaos (though there might well be a healthy dose of anarchy).

The world is constantly changing. As IT professionals, we are aware of the intrinsic changeability of projects, contexts and our business, but the events of the last years have put this into sharper focus. How will external changes shape our teams and our work?
Alex looks at what factors are at work now, and what kinds of effects will they have on how we work, and the roles of testers and software professionals. She will also look at activities on an individual and company level, to best prepare ourselves for a nebulous future.

Target Audience: Everyone
Prerequisites: None
Level: Advanced

Extended Abstract:
The world is constantly changing, and everything is impermanent. As IT professionals, we are aware of the intrinsic changeability of projects, contexts and our business, but the events of the last years have put this into sharper focus. How will external changes shape our teams and our work?
How can we shape ourselves proactively in order to be able to respond to changes, make changes or our own and even thrive? Alex looks at what factors are at work now, and what kinds of effects will they have on how we work, and the roles of testers and software professionals. She will also look at concrete activities on an individual and company level, to best prepare ourselves for a nebulous future.

As Agile product people we are in a unique position to influence a sustainable value chain for the development of our products. What we do matters, how we build things and what we build, matters. Or what we don’t build. In this talk we will dive into some principles of circular economy and the (radical) economic theory of Degrowth and how to apply these principles and ideas in our daily work as product people. Principles like refuse (to build something new), reuse and recycle in our whole product value chain will be discussed. You will walk away with concrete suggestions to start working at work the very next day.

At Tchibo we wanted to reduce our server and energy consumption with our product development teams. But why would we care? We all like fast snappy development and test systems. And our shop needs to survive Black Friday’s shopping traffic. Annual Google Cloud consumption forecasts do not trigger us to consume less. But when we started to show teams their related carbon dioxide footprint, we created a feedback loop that will help us to become better CO₂-developers.
As developers, we have an impact - to program CO₂ reduction.

Target Audience: Everyone, Developers, DevOps People
Prerequisites: None
Level: Advanced

Extended Abstract:
We will present the idea and first measurements on the server side. The planned client side measurements are still work in progress and very difficult to perform. Nevertheless is the client side induced CO₂ consumption at large websites probably a large lever for reduction.

Mehr Inhalte dieses Speakers? Schaut doch mal bei sigs.de vorbei: https://www.sigs.de/autor/johannes.mainusch

In 2011, realizing it desperately needed to offer a competitive product to Airbus’ A320neo, Boeing embarked on a project to upgrade its legendary 737 aircraft to match the A320neo’s efficiency. Limited by the constraints of the 737’s original design and their desire to minimize training needed by pilots to fly the new aircraft, Boeing made multiple critical compromises in the aircraft’s design. 346 deaths and $87 billion later, we have all been reminded of the importance of rigorous design processes and the need to engineer systems for the realities of the end users and their environment. This talk dives into the motivations for the design compromises, the human factors considerations that were disregarded, and how a Fortune 100 company’s prioritization of profit over good design practice led to its stunning fall from grace.

High traffic during business hours, no traffic at night, weekends and vacations, multiple teams, and several staging environments - these characteristics of a typical enterprise application. Pay-as-you-go, "scale-to-zero" and managed services make serverless architectures appealing for enterprise applications.
On-premise, on the other hand, you get the maximum flexibility and full access to machines with less automation and so more plumbing.
I will compare both approaches with focus on architecture and answer your questions in real time.

Target Audience: Developers, Architects
Prerequisites: Basic Cloud and Java Knowledge
Level: Advanced

Great engineers often use back-of-the-envelope calculations to estimate resources and costs. This practice is equally beneficial in Machine Learning Engineering, aiding in confirming the feasibility and value of an ML project. In my talk, I'll introduce a collaborative design toolkit for ML projects. It includes Machine Learning Canvas and MLOps Stack Canvas to identify ML use cases and perform initial prototyping, thus ensuring a business problem can be effectively solved within reasonable cost and resource parameters.

Target Audience: Architects, Developers, Project Leader, Data Scientist
Prerequisites: Basic knowledge in machine learning
Level: Advanced

DevOps isn't dead yet and it will not die in the future. Platform engineering comes to leverage DevOps practices horizontally to support developers, operations and those in between. In this session, I will give you a perspective on how to move on from DevOps to Platform Engineering, how to design and shape your internal platform and build a vibrant community sharing best practices and enabling each other to overcome faster issues. In the end you will understand how we can reduce the cognitive load for dev teams to focus on features.

Target Audience: DevOps, Developer, Manager
Prerequisites: Experience in DevOps and an understanding of the pain of silos
Level: Advanced

Extended Abstract:
Platform Engineering is often seen as the evolution of DevOps. However, it is yet a new discipline using DevOps practices but focusing on the entire chain and breaking silos. I will show details from my experience on my job as well as 3 years of release engineering at Kubernetes where it wouldn't be possible to release without a proper platform.

In this session, we focus on the topic of software product management (PdM) and how PdM practices are rapidly changing. Together we explore and define how to do PdM for digital products as well as software-, data- and AI-intensive systems. Some questions we explore include:

1. How to change current PdM practices to work with digital technologies and digital offerings?
2. What is the future of PdM practices and what are the key characteristics of digital product management?

Target Audience: Product Managers, Software-Architects, Software Engineers, R&D Management
Prerequisites: No specific technology expertise required.
Level: Advanced

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.

Pecha Kucha erlaubt Sprecher:innen gerade mal 6 Minuten und 40 Sekunden. In dieser Zeit können sie mit exakt 20 Bildern, die genau 20 Sekunden eingeblendet werden, ihre Ideen - im wahrsten Sinne des Wortes - auf den Punkt bringen. Für die Zuhörer bedeutet dies: Kein zeitraubendes "Gelaber", dafür aber knackige und unterhaltsame Informationen. Freuen Sie sich auf eine bunte und unterhaltsame Auswahl von Vorträgen mit vielen inspirierenden Inhalten und Bildern!

• Energie! (Johannes Mainusch)
• Die fabelhafte Welt der KI: zwischen genial und grotesk (Eldar Sultanow)
• Story of Lockheed Martin (Skunkworks) and Stanford University (Benjamin Igna)
• Just get leaner – using lean concepts to enable change (Michael Mahlberg)
• Per Anhalter durch die Amiga-Disk Galaxie (Thomas Ronzon)
• Altersweisheit? 25 Jahre agil und kein bisschen schlauer? (Stefan Roock)
• Parrots or Prodigies: All you have to know about AI! (Steve Haupt)
• "Don't Be A Serf Domain" (Michael Sperber)
• Tales of a Women Wonderland (Vera Hofheinz)
• 80 days: your major contribution to peace (Christine Neidhardt)

Zielpublikum: Alle, die sich für Kurzvorträge begeistern können oder darauf neugierig sind
Voraussetzungen: Keine
Schwierigkeitsgrad: Anfänger

**TL,DR**; In this course you will learn to map your business and technological landscape in such a way that a common language emerges to discuss strategic thinking and decision-making.
Max. number of participants: 13

Target Audience: Architects, Developers, Project Leaders, Decision Makers
Prerequisites: Basic theoretical knowledge of DDD
Level: Advanced

Extended Abstract:
Organizations face more and more complexity these days as a result of a mesh of products, services, technology and the people that work to build, operate and maintain them.
Domain-Driven Design helps us with solving problems the right way. But what helps us solve the right problem? How can we continuously validate our progress with people in "non-tech" roles? And what should we do when the world around us changes, which it always ends up doing? Is the plan we had still valid?

Imagine...
- Imagine having a map that helps you understand the ecosystem your organization is embedded in. A map that makes sense from both a technical and business perspective. With patterns that provide guidance about effective actions regardless of the specific domain you are working in. Wardley Mapping is that: it is a ubiquitous language around strategy and execution that helps you solve the right problem.

The course
- In this course you will learn to map your business and technological landscape in such a way that a common language emerges to discuss strategic thinking and decision making. It allows for scenario building, it teaches about bias and assumptions, and it comes packaged with a long list of ideas that may help in your situation.
The map can hint us what practices from DDD are beneficial in our situation. And it can serve as a context map too, except this one has meaning to businesspeople as well.
Using visualizations, strategies can be challenged and implementation options debated and weighed. As such, mapping is about the act and not merely the artifact. That is why this training is hands-on from the very start.

What to expect
- This class will emphasize practice over theory. Mapping with imperfect knowledge today is better than mapping with perfect knowledge next year. The course will teach you the basics and provides hooks into the theoretical aspects behind exercises.

Who should attend
- Anyone that wants to challenge the status quo of decision making under uncertainty in technology and business. No prior knowledge is required and your open attitude to learn new things will be an asset during the workshop.

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.