Day 1

Exciting times for IT architects: agile practices and domain-driven design, cloud nativity and Web APIs, generative AI and DevOps automation and many other trending topics keep on changing the context of our work. The main responsibilities and essence of our role remain, though: serving as advocates of development teams, coaches and communicators, technical risk managers, and, last but certainly not least, decision makers.

This talk introduces old and new Architectural Decision (AD) making practices such as AD Records (ADRs), AD definitions of ready and done, and Most Responsible Moment (MRM). It also identifies criteria for architectural significance and ADR (anti-)patterns.
The talk concludes with a proposal of a maturity model for AD management and a first look on ongoing research to position ethical values such as sustainability as special types of non-functional requirements.

Take aways:
– Find out when to best make which type of decision (MRM).
– Learn how to make and document ADs effectively, efficiently, and responsibly.
– Identify opportunities to improve existing architecture practices

The COVID-19 pandemic dramatically altered the landscape of work, pushing knowledge workers into a predominantly remote environment and establishing a new, enduring hybrid work model. This shift has transformed workplace flexibility from a privilege to an essential right, greatly influencing personal well-being and productivity. However, the transition to hybrid work rhythm is not without its challenges. Increased remote working can potentially disrupt workflows, reduce overall efficiency, complicate onboarding processes, and fragment knowledge networks and awareness of what is going on across work units. Based on the insights from studying multiple organisations in Sweden and Norway, this talk will critically examine the dual nature of remote working—highlighting both the increased autonomy for individuals and the resultant challenges faced by software architects. Special attention will be given to effective strategies that reconcile individual flexibility with the need for team cohesion and understanding ”the big picture”. Join us to learn how to create a well-functioning hybrid rhythm that supports both personal well-being and robust group orientation

*More information coming soon.

Once upon a time, there were architecture and architects. Then, Agile arrived: architecture and architects needed to find their place in the new world. Together with three companies in the Nordics, we explored the role of architecture and the architects in Agile. We created and evaluated, in practice, a framework, CAFFEA, clarifying responsibilities and roles for agile architects. And now, AI is taking the world by storm: are architecture and architects going through another revolution?

Few IT disciplines are associated to so many questions about its value as Enterprise Architecture; yet, almost every mid- to large-size company has an EA practice. But no matter how many times you start an ”Enterprise Architecture 2.0” project to change the focus, people or organization to improve your EA practice, the end result is often the same: stakeholders do not feel that they’re getting as much out of the practice as they wish they did. But what exactlydo they wish for, and what are the most common reasons for discontent? And, even more importantly, what can we do about it?

In this session, we walk through the building blocks of an EA operating model and discuss 7 universal dilemmas that we all face when setting up or restructuring an EA practice. Making conscious choices for each dilemma creates far better conditions to meet stakeholder expectations that otherwise often stay implicit throughout the design. We’ll go through the ifs and buts of each dilemma, how to quickly position oneself on each dilemma spectrum, and how these dilemmas can inform the design of a more successful EA practice.