Agenda

Marc Lankhorst, BiZZdesign

Agile methods have become the norm in software development. But true business agility requires more than having a bunch of agile teams. Moreover, if you only focus on the agility of your development processes, you might miss the forest for the trees: why do you want to be agile as an enterprise, and what does that require?

In smaller organizations, a few agile/DevOps teams can coordinate change amongst themselves, and the lines to management are short enough that strategic direction can be conveyed to teams directly. In large organizations, however, there may be hundreds of agile teams, each working on a part of the big ‘enterprise machine,’ and more coordination is needed. If you have agile teams building agile silos that disregard their environment, you will still not have an adaptive and flexible end result. In addition, future change may become even more difficult, which is why good architecture is essential.

And there is more to an enterprise than software. This is where the ‘big picture’ view offered by EA adds value, as it also encompasses other stakeholders than software users and considers desired (and unwanted!) business outcomes, capabilities to be developed or improved, resources required, business processes, IT and physical infrastructure to be realized, and more.

Marc Lankhorst will address how agility in both methods and products is required to create true business agility. He will address several use cases for the combination of EA, Agile and DevOps and show how an agile approach such as the Scaled Agile Framework can fruitfully be combined with an EA method like TOGAF. Finally, he will discuss how the tools of architects and developers can be integrated to provide end-to-end visibility and collaboration.

Peter Filip, Tatra banka

Sumář praktických zkušeností a pozorování o tom, jak EA podporuje a přispívá k transformaci celé organizace – banky z vyladěného, fungujícího vodopádového modelu na agilní. Pozornost bude soustředěna na dvě oblasti:

• Proces plánování
• Návrh struktury týmů

Změny v těchto oblastech budou popsané z pohledu architektů, jejich chování a zapojení do změny i z pohledu využití dat o architektuře při realizaci změny.