Learn about purchasing for teams

My name is Lars Hueper. I am working in software business since 1999.
As I became part of larger software projects, most of the time, I had the feeling, that how we were organizing our requirements and deadlines, was somehow wrong. But I couldn't explain, what we should do instead. For many years, I accepted what other people told me: There is well known methodology in writing huge specifications upfront and managing projects in a "static" way and I thought that it was me, who didn't understand or practise good enough those methodologies.
I was part of a crisis project in 2008, when the project manager left the company in a situation, where it was no longer possible to repeat the old phrases. We (the developer team) and the customer were left back with a list of 800 open points/defects and without a project manager. So, we put "methodology" aside a tried to reduce complexity by having bi-weekly prioritization meetings, while focusing on developing top priority features in the middle of those meetings.
After that experience, I read about Scrum and it seemed to be the right answer. Since 2009 I am practising Scrum in different contexts, trying to convince customers to do it right from the beginning. Over the last years, I also spent time on learning about agile organizations, Management 3.0, working at eye-level. Since 2014, I am part of an Agile Community of Practise in my company. We try to facilitate the adoption of agile practices throughout the organization.
Since 2011, I am organizing a local Scrum Usergroup in Hannover, the Agile Wednesday. We meet once per month to discuss and learn from each other.
Career history