Dag 1 erbjuder ett parallellt spår med föredrag, och dag 2 består av fyra workshopspår under förmiddagen. Deltagande i dessa spår kräver tilläggsregistrering, som är kostnadsfri och görs på plats. Observera att ingen tilläggsregistrering krävs för att delta i huvudprogrammet.
Day 1 features a parallel track of presentations, and Day 2 includes four workshop tracks in the morning. Participation in these tracks requires additional registration, which is free of charge and completed on site. Please note that no additional registration is required for the main program.
- Day 1
- Day 2
- Track 1 main programme
Årets programansvariga, Thijmen De Goojier och Matti Kinnunen, hälsar välkomna tillsammans med en representant från Dataföreningen Kompetens.
Att kunna arbeta med domänexperter på ett sätt som leder till bra effekter är en viktig kompetens. Inte minst om du vill ha framgång i initiativ inom programvaruutveckling. Detta är dock inget som vi studerar särskilt mycket trots att vi verkar kämpa med det om och om igen. Det är också en färdighet som du aldrig till fullo kommer bemästra, det finns alltid mer att lära.
I den här presentationen kommer Jimmy dela några av sina insikter som han samlat på sig under 35+ år som konsult inom programvaruutveckling. För att göra presentationen levande så kommer han ta hjälp av frivilliga deltagare för att demonstrera och testa tipsen live. På så sätt blir det en delad läro-erfarenhet snarare än en envägspresentation.
Samarbetar du redan *för bra* med dina domänexperter? Om inte, kom till denna presentationen! Du kommer gå härifrån med en verktygslåda med praktiska tips som du kan börja använda redan imorgon. Det kommer leda till ökad tydlighet, tillit och resultat i ditt nästa samarbete.
Mer information kommer inom kort
Samspelet mellan människor som kan och vill tänka själva får ytterligare dimensioner när de även skall förhålla sig till maskininlärning och AI som ser ut att tänka. Det kräver att ledarskap på den tekniska nivån också anpassas till nya situationer, när gränssnittet mellan IT-arkitektur och att leda människor har kvar alla tidigare utmaningar men även får en del nya. Det är som att valla katter, men inte enbart katter.
Här erbjuds en föreläsning om varför det är roligt att få tänkande människor att arbeta tillsammans just för att det är svårt, om att bygga upp och bygga om, men även om varför IT-arkitekten får lägga tid på att tänka på tänkande medarbetare och vad Pippi Långstrump kan ha med saken att göra.
Mer information kommer snart
Lunch serveras i Clarion Signs lokaler. I samband med detta ges även möjlighet att registrera sig till tisdagens workshops.
A common challenge in modern software architecture is how to empower people to make architectural decisions while keeping them aligned with the overall goals and priorities of the system. Architectural principles are a deceptively simple idea which helps us to achieve this. Principles provide actionable goals, constraints and priorities, with clear rationale, that allow their applicability and importance to be quickly understood. This gives people the context they need to make good, aligned decisions.
In this talk I will introduce the idea of an architecture principle, discuss what makes a good principle and how to capture it clearly, and show how they relate to architectural decisions to help teams make good decisions that solve their immediate problem but also preserve the technical integrity of the system.
The focus of this talk will be to explore how, as organizations continue to automate and modernize, the risk of designing systems that outperform or constrain human capacity grows. In complex socio-technical environments, performance of an organization behaves less like a machine you can optimize part-by-part and more like a quantum system: outcomes emerge from interdependence, context and observation. The authors of this talk proposal that sustainable organizations arise not from maximizing technology alone, but from cultivating a culture and practice of kinship between humans, their processes and their technological systems. That organizations need to focus on optimization that is not additive, but relational – changing one element of an organization changes the whole, and what we choose to measure and automate shapes what is possible.
The traditional view of software architecture typically places humans outside the system and in the system’s environment. In this talk I argue that there are benefits in shifting this view by bringing humans into an architectural design as first-class entities. The resulting architectural designs can then much better exploit human-system synergies that are required by today’s increasingly autonomous, self-adaptative, and AI-driven systems. We will illustrate the ideas by examining case studies in which this approach has been used to provide formal human-system architectural models that attempt to maximize the respective strengths of both humans and systems. We also highlight some of the key challenges and potential directions for research in maturing these ideas.
- Day 2
Mer information kommer inom kort
My father was operations manager at a gold mine in the inland of northern Sweden. During a visit to the mine, he didn’t just explain the process—he paused at something that stuck with me: it takes as little as 3 grams of gold per 1 ton of rock for mining to be worthwhile. Three grams. Out of a million grams of grey stone. That ratio has stayed with me ever since.
In the AI era, it feels more relevant than ever. We are drowning in data, models, prompts, agents, and possibilities—but real value is still extremely concentrated. What if just 3 KB of insight in 1 TB of data is enough to make data mining worthwhile? Or 0.25 seconds in a 24-hour day for a reflection to be worth writing down? Even when the work feels grey, repetitive, and seemingly uninteresting, there is gold beneath the surface. The question is whether we have the right tools, the right pickaxe—the right framework, process, and architecture—to distinguish the gold.
This talk takes its starting point in Pickaxe Principles – Thriving in the AI Gold Rush, but goes beyond the book by, among other things, using the journey of writing, launching, and scaling the book as a concrete case. The audience will follow how AI, workflows, agents, and automation are used in practice to move from experiments to coherent systems—with the goal of creating 2×, and in some areas 10×, real impact.
The focus is not on individual tools or models, but on the architecture that enables consistent value creation over time. We explore why many AI initiatives get stuck in short-term productivity, while few succeed in building systems where small insights accumulate, are refined, and grow in value. Often, it’s not the technology that fails, but the context: accountability, incentives, human judgment, and discipline in everyday work.
Using the gold rush metaphor as a framework—prospecting, mining, refining, and value creation—we discuss how architects can design socio-technical systems where people, AI, and organizations collaborate in a sustainable way.
After the talk, participants will leave not only with inspiration, but with concrete and directly applicable tools for how they can:
identify the “3 grams of gold” that create real value in their data, systems, and AI initiatives
discover and unlock potential in themselves and in people around them
design architecture, ways of working, and incentives that ensure small insights are actually captured, refined, and reused
build structures where consistency compounds—so that value grows over time, even when everyday work feels grey
The goal is for participants to return to their organizations with a shared language, a clear framework, and a practical starting point for gathering gold—in themselves, in others, and in the systems they are responsible for.
Many systems are well-architected on paper—structured, scalable, and aligned with best practices. Yet, when they meet everyday work, something happens. Workarounds emerge, informal practices take shape, and the system is adapted in ways that were never intended
This talk explores the gap between design and real work from a socio-technical perspective. Drawing on research and empirical examples from digitalisation in organizational practice, it highlights how systems, people, and organizational contexts interact in ways that challenge assumptions made during design.
Rather than offering prescriptive guidelines, the talk invites reflection on what everyday work can teach us about architecture. What becomes visible when we shift focus from systems as designed to systems as used? And how can these insights help us better understand what it means to build systems that actually work in practice?
In large-scale agile development, many important problems are not technical in themselves, yet they have major technical consequences. Unclear roles, weak coordination, poor communication, and inherited ways of working can create non-technical debt: hidden human and organizational conditions that slow teams down, complicate decisions, and undermine system development over time.
This presentation shows why non-technical debt matters for IT architects and other practitioners working with socio-technical systems. Based on empirical studies of large-scale agile development, it introduces process, social, and people debt as practical concepts for understanding how human context affects architecture and delivery. The session will highlight how to identify these issues, why they matter even more in an AI-supported development environment, and what practitioners can do to improve collaboration, decision-making, and system design.
Mer information kommer inom kort
