This is an intermediate version of the program. Expect changes until the final version will be published.
|08:45 – 09:15||Registration & Welcome Coffee|
|09:15 – 09:30||Opening words|
|09:30 – 10:30||Andrea Provaglio: The Beating Heart of Agile|
|10:30 – 10:50||Introducing the Open Space and Lightning Talks|
|10:50 – 11:05||Coffee break|
|11:05 – 12:05||Jurgen de Smet & Erik Talboom: Perfect Problem Breakthrough!|
|12:05 – 12:35||Arpad Zsolt Bodo: What happens with leaders and their responsibilities when the org. becomes agile and flat?|
|12:35 – 13:35||Lunch Break|
|13:35 – 15:35||Open Space|
|15:35 – 16:20||Flavius Ștef: The Scrum Master’s toolbox|
|16:20 – 16:50||Ionel Condor: I am a Senior Developer, so now what?|
|16:50 – 17:05||Coffee Break|
|17:05 – 17:20||Lightning Talks|
|17:20 – 18:05||Arie van Bennekum: Get them involved|
|18:05 – 18:20||Closing Words|
|18:20 – 19:30||Happy Hour Networking
(If we find a sponsor. Want to sponsor it?)
The Beating Heart of Agile
What is it that makes an Agile team or an Agile organization run like a clockwork, deliver and succeed? Is Agile just a set of useful practices and tools, or is there more to it than meets the eye? Yes, we also have values and principles, but are those what really makes the difference between a team that delivers and one that doesn’t?
More than anything else: could it be that effective teamwork and social/relational proficiency, custom-fit for an Agile cultural environment, are the ultimate – and largely untapped – source of real competitive advantage?
In this session, based on the speaker’s experience, we’ll explore topics such as:
- challenging mental models
- collective intelligence
- organizational learning
Among other things, we’ll get insights on how all of the above are required (and can be fostered) to create a culture and an ecosystem where your organization and people can reap the benefits of an Agile approach – which include quality, fast feedback, constant improvement, learning and, of course, wealth.
In this session you’ll get insights on how to use Christopher Avery’s Responsibility Process in the context of handling problems and thus change. We will explain you the 3 key’s to responsibility and how to gain control/power of the situations at hand. We will use learning from the Leadership Gift program we are following with Christopher Avery and provide insights related to the Responsibility Process and Keys to Responsibility. We will give you some very powerful tools and techniques that will change your world.
Arpad Zsolt Bodo
What happens with leaders and their responsibilities when the organization becomes agile and flat?
In most organizations, one of the biggest challenges in going Agile is to figure out how a flat hierarchy could work; what happens with people in different leading or management roles; how their experience and skills can be utilized in a flat hierarchy, with self-managing teams, what happens with these responsibilities. There is a considerable risk that such people leave after most of their responsibilities are dissolved into the Scrum teams.
I’ll present you how we encountered these issues, the structure we developed to address them.
All conference participants
During the Open Space sessions, all participants will be able to propose topics they would like to discuss. Also, they will be able to attend one or more sessions they find useful.
The sessions are informal parallel ‘gatherings’ governed by the Law of Two Feet: If at any time during our time together you find yourself in any situation where you are neither learning nor contributing, use your two feet, go someplace else.
The Scrum Master’s toolbox
There is more to the Scrum Master role than booking meeting rooms and moving stickies on the whiteboard. During his talk Flavius will try to clarify this often misunderstood Scrum role.
Come learn what seasoned Scrum Masters should do in order to bring management, development and product together to create a motivating workplace and build valuable products that delight their customers.
I am a Senior Developer, so now what?
I found it useful to collect some observations from the trenches, looking around at senior developers and the traps some of them fall in.
So during this presentation we will put ourselves in the shoes of a Senior Developer and look at some issues he needs to deal with.
Here are some examples:
- generation gaps and how to lead generation Z
- various types of developer’s behaviors and patterns in project delivery
- what is healthy productivity
- how to blend creativity with discipline and the culture of competitiveness
- how shall I understand delegation
- how to deal with people that are smarter than me and hungry to grow
- what are some toughs questions I shall put myself as a Senior
- how my career will look like in 10 years
- tools and techniques to identify the traps and solutions I found useful along the way
- what really makes a senior senior
All conference participants
This time slot is dedicated to everyone from the audience that has something to share with the rest of the attendees. You can prepare slides for your talk, or you can have a small speech without visual aids — it’s your choice.
You can talk about your ideas, experiences, successes or failures in the context of Agile. Maybe you know of a cool new tool and you want to share that with us, or maybe there’s an old idea that you stumbled upon and everyone seems to have missed it.
Be it any of the above choices, you’ll have 5 minutes to share it with us.
Arie van Bennekum
Get them involved
Agile is not new. Agile is not a trend. Agile is established. This year we celebrate that the Agile Manifesto has been written 11 years ago. Arie is co-author of the Manifesto and still very active in the field of Agile Solution Development. He still does it for the same reason as when he started doing it 18 years ago.
His definition of Agile is “Serving the business by being adaptive”. To be able to do this he does need (and therefore involve them in his projects) the end-users. Not a representative but really from every end-user group of the solution, a real participant. The people who will really work with the solution when it is live. And this is the part Arie likes most, working with the end-user community to converge to the matching solution. You can call it testing, reviewing, whatever but it is the input and check of that real end-user that is essential.
The last year, during all his presentations and meetings Arie did hear the same problem over and over again. How do you get them in and how do you make them participate the right way. They are the one and only people who really know what they need. On the other hand they are not IT-professionals and do not always know what to do in a project. How do we get them involved (the right way)? Can we learn from what we have done so far…
This is what made Arie connect to Agile in 1994 before it was named Agile in the first place and is what his presentation will be about.