You have a problem? It involves people and technology? I can help you...I've lead and coached software teams, projects and businesses involved in emerging technologies in both service-oriented and product oriented organizations.I also still code, quite a bit. I find its a necessary part of my job. I’ve been coding professionally for nearly 20 years, most recently Python and JavaScript, but also PHP, Java, C, C++ and assembler.I’m a problem solver and hands-on leader. I'm passionate about building technology that fixes real world problems. I get teams to deliver. So why don’t I just focus on software development? After all, it is a comfortable place to be. Travelling to share my knowledge to speak at conferences was very nice for my ego, and I really enjoy learning a new stack or a new pattern.But at the end of the day I discovered that I care much more about my team than any specific technology I get to play with. And protecting them requires much more than deep technical skills. I’ve seen many projects in my career, and quickly discovered that non-technical problems are what usually kill projects. While it may be difficult to predict the future in an innovation context, the number of teams and projects stifled by completely predictable problems is simply astonishing.So I embarked on a quest to figure out why smart people make decisions that kill projects, and how to prevent it. I dived deeply in project management, the agile movement and organizational leadership.Nowadays, agility is transitioning from buzzword to cliche. Sadly, people in both startups and large organization still misunderstand what basic concepts like self-organization and product ownership actually entail.The problems that kill projects generally live at the interface between the product team and the rest of the organization. I specialize in bridging that gap.
Listed skills include Software Project Management, Agile Methodologies, Open Source, Sql, and 42 others.