The following content has been provided by the University of Erlangen-Nürnberg.
Hello everybody. Thanks for the warm welcome. Thanks for letting me be here.
I would like to talk to you about the interaction between classical and agile project management at Sixth IT.
As you can see, the presentation is in German while I am talking English.
I hope this isn't a problem for anyone.
So you might know this presentation existed before I was invited here.
So just to make it transparent, as transparency is my primary principle of agile development,
this presentation is just like a set of presets that I thought that might fit here.
So just a few sentences about me.
As you can see, I started as a veterinarian in my career.
Even while studying, I was doing a lot of stuff with computers,
administrating them and programming them.
And by finalizing my studies, I switched over and started to work as a developer.
I taught myself PHP.
I taught myself several database systems.
Additional education of one year as a developer.
I learned a lot about networks, about development in C, C++, Java,
and started then to work as a freelancing developer.
After that, I soon got involved in more architectural and conceptual discussions.
I started to lead teams, to organize teams, and somehow to manage projects, whatever that means.
So while doing this, I always got more deeper into the question,
how do we organize software developers in a way that the work they do isn't totally for nothing,
but somehow productive, and in the end you have something as a result which you can use
and hopefully sell.
While doing this, I think it was about 2004 or 2005,
some people came up with some fancy new weird ideas called Agile.
So you have to do it totally different and then everything will be perfectly fine.
We tried and adopted this very early, and I found out within a year or something
that Agile had a lot of answers to questions that I had in project management
or project development for a while, so I really started to love it and to use it.
Later on, I worked as a freelancing project manager, team lead, and consultant.
That's how I came to SIXT in 2014.
I started to work there as a freelancer for a year,
and then I have to say I liked the company that much that I joined them.
So I'm working as a senior manager for Agile development for SIXT since March 2015.
Until then, SIXT IT was managed classical, whatever that means,
with just a few ideas of skirmish behavior that haven't been too successful,
and my mission, idea, and job was to change this.
So just a few words to this presentation.
I don't want to stand here and have a monologue about ideas
that I think might interest you, because if we have bad luck,
I just would waste your time, and this would be a waste of my time.
So please, again, transparency, inspect, adapt.
What do you need to inspect is feedback.
So whenever you have the feeling that I'm talking about something
that you simply don't want to know because you know it already or whatever,
please let me know.
Meanwhile, the other way around, if I don't talk about something
which you urgently want to know, please let me know as well.
So we can swap topics, comments, whatever you like, whenever you like.
Presenters
Daniel Liebig
Zugänglich über
Offener Zugang
Dauer
01:24:38 Min
Aufnahmedatum
2016-07-06
Hochgeladen am
2016-07-06 15:48:34
Sprache
en-US
Traditional and agile project management take different approaches to reach the same goal: Deliver working software, even though it can be a challenge to run both methodologies under the same roof. This talk is about how Sixt experienced, accepted and managed this challenge.