“Agile Organization” Track (16:15) – Heldin Rikk and Kaspar Eding 

With topic:

“Stop believing magic and face your fears – change your organization”

Short introduction about speaker:

Heldin and Kaspar have more than a decade of experience in adopting agile methodologies in finance, banking, logistics, hardware manufacturing and communication industries. They have taken several organisations through an agile transition, built new agile organisations and most importantly delivered several successful products on the way.

In search for know-how on implementation challenges, Heldin and Kaspar have found themselves in organizing management trainings and presenting the challenges in conferences. They claim to have found a cultural offset that holds organisations back from harnessing the benefits of agile. Their story is based on engineering success, but they talk about why organisations often still consider agile frameworks to be not suitable for them.

Topic abstract:

Evolution in technology is changing the game in every industry – this is not news to any business. Predicting market demand and satisfying customer expectation is becoming gradually more and more complex task. To improve strategy execution capabilities – to be faster and more adaptive – companies adopt agile frameworks. These transitions are often painful and in many cases lack the desired business impact. This talk is about the “Elephant in the room” – how we pick the methods that are convenient to adopt and dismiss the change that is really needed to move the needle.

“Workshop” Track (15:15) – Ari Tanninen  (Zulia Oy)

With workshop:

“Take ownership of your life”

Ari Tanninen

Short introduction about speaker:

Ari is a trainer at Zulia Oy, a product development consultant at Lempea Oy, and a Recognized Practitioner in The Leadership Gift. He spends his days helping companies develop software that fit customer and user needs, and enjoys lighting the spark in people’s eyes by training them in self-knowledge and responsibility.

Workshop Abstract:

Are you stuck or facing problems in life?
Would you like to learn to lead yourself and others better?
Are you wondering how to get your sub-ordinates to take more responsibility?
Would you like to live a life of freedom?

Then join this workshop, and learn about Christopher Avery’s Responsibility Process. It is a psychological process, that explains how we all naturally react to problems, and how our brains create obstacles for us in taking responsibility. And thus living a life of freedom, power, and choice.
Understanding and practicing Responsibility may help in:
– Leading yourself and others
– Building teams
– Understanding organizations
– Breaking through problems
– Understanding behaviors such as blaming and shaming
– Living a life of freedom, power, and choice

This is an interactive 2-3 hour workshop with exercises and discussions, and no slides. You will learn about the responsibility process, learn to recognize it, and get tools for practicing and taking responsibility in your life.

“Agile Organization” Track (15:15) – Dmitri Lebedev (Citadele Bank)

With topic:

“Conway’s Law or How Your Agile Organization Supports Your Agile Architecture”

Dmitri Lebedev

Short introduction about speaker:

Dmitri started his job as a software engineer more than 20 years ago, has delivered many software projects, failed a few, learned a lot of things from other people and now he is willing to share his stories of success and failures with broader audience. The ultimate goal of his activities is that software could be developed pragmatically, based on an engineering approach and mutual respect between all involved parts.

Topic Abstract:

According to Melvin Conway the organizational structures manifest themselves in org’s software product structure. In other words, dysfunctional organization would produce dysfunctional software architecture. Let’s try to reverse engineer organizational structures from a robust and agile modern architectural principles, and see how agile org should look like. I am going to review modern architectural and devops practices like micro-services, feature toggling, continuous delivery and etc and examine which org structures support that kind of architecture and which structures are making this nearly impossible to work. Talk is based on my personal experience and on some good known examples like Spotify.