Skip to main content

Agile Lean Europe: Some thoughts

Just jotting down some thoughts..

A couple of weeks ago, I drove up to Düsseldorf to attend the Scrumtisch Rhein/Ruhr meeting, because the topic was this new Agile/Lean Europe (ALE) Network. Olaf Lewitz facilitated the discussion ( credits to CodeCentric for the free beverages/food).

I first heard about this network in this discussion in the Norwegian agile forum, initiated by Sergey Dmitriev and followed up on by Johannes Brodwall.

Olaf and Deborah Preuss were both involved in the Agile Coach Camp in Norway earlier this year, and I suspect that they already discussed some of these things there. This makes for a firm connection between the German and Norwegian agile scene, and I hope to be able to support this bridge somehow.

Now, why does this European interconnection matter anyway? 
I'll give you three reasons why it matters to me personally:

1) It's no fun doing it aloneAgile is deeply nested with social drive. While it's perfectly fine to drive on the social forces within a closed community (say, the German agile scene), it gets a lot more interesting if we know that this is an international effort. Knowing that other countries are interested adds motivation.

2) A mirror for our culture
We make changes based on feedback and inspection. For the sake of fresh perspectives, we often use externals (consultants, coaches) for gaining insight. Agile depends heavily on, and influences, culture. Ergo, for a fresh perspective, we might benefit from using externals from other cultures/countries.

(One thing is organizations of business, another thing is getting feedback on how our communities are operating.)

3) Synergy, or re-using knowledge and experience in other countries
If I spent hundreds of hours creating some crystallized knowledge on how to deal with some particular problem (like introducing agile in public sector), it would be an awful shame if it only came to the benefit of the few thousand potentially interested in my country. Letting other countries benefit from the same knowledge is win/win.

A few thoughts on Germany/Norway in particular

There are limits to how much we can absorb from American (and even British) experience reports. Germany and Norway are both social-security oriented economies, with conservative innovation habits, well on the way into privatizing a bunch of former national institutions (rail, telecom, post/logistics, health).

So we have a lot of things in common. And if I may say, people are very similar in regards to personality and behavior (the way we eat, drink, talk, politeness, etc.). But Norway is tiny and Germany is huge, which makes Norway a bit like a miniature test-lab for Germany. What works on in Norway could work in Germany on a larger scale.

To name one example: The traditional rejection of agile projects in Norway's public sector projects was overcome some few years ago by (among other things) the creation of an agile contract standard, the PS2000 agile. Since then, several successful projects have made use of this contract, both in public and private sector.

Is this a lesson we could port to Germany somehow?

Also check out Kurt Häusler's thoughts in this post and Olaf Lewitz's summary from the Düsseldorf meeting. Both of them, as well as Johannes Brodwall are attending the ALE Network events at the XP Madrid conference in a couple of weeks.

Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do: # install vcsh & myrepos via apt/brew/etc vcsh clone https://github.com/tfnico/config-mr.git mr mr update Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files . No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed: config-atom.git     -> ~/.atom/* config-mr.git     -> ~/.mrconfig     -> ~/.config/mr/* config-tmuxinator.git       -> ~/.tmuxinator/* config-vim.git     -> ~/.vimrc     -> ~/.vim/* config-bin.git        -> ~/bin/* config-git.git               -> ~/.gitconfig config-tmux.git       -> ~/.tmux.conf     config-zsh.git     -> ~/.zshrc How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for o

Leaving eyeo

Thirteen blog posts later, this one notes my departure from eyeo after 4 years and 3 months. I joined eyeo around the headcount of 80 employees, and now I think there's just over 250 people there. My role coming in was as operations manager, doing a mix of infrastructure engineering and technical project management. I later on took on organizational development to help the company deal with its growing pains . We introduced cross-functional teams, departments (kind of like guilds), new leadership structures, goal-setting frameworks, onboarding processes and career frameworks.  And all of this in a rapidly growing distributed company. I'm proud and happy that for a long time I knew every employee by name and got to meet every single new-hire through training them on company structure and processes.  At some point, we had enough experienced leaders and organizational developers that I could zoom back in on working in one team, consulting them on  Git and continuous integration

Joining eyeo: A Year in Review

It's been well over a year since I  joined eyeo . And 'tis the season for yearly reviews, so... It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling. Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes: How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies wit

Using Voice-Chat for Gamers in Distributed Teams

This is a post going into the usefulness of live voice-chat tools in distributed teams. If you've ever seen the Leeeeeroooooyy Jeeeenkiiins video of World of Warcraft fame, you've heard this kind of tool in action. It's how the participants in the video are speaking with each other - this is not a feature built into the World of Warcraft game - it's a separate team-oriented VoIP software, and it's all about letting gamers communicate orally while gaming.  Since these tools are for gamers, they have to be fast (low latency) light (as not to steal CPU-cycles from heavy games graphics)  moderate in bandwidth usage (as not to affect the game server connection) There are several options around: TeamSpeak , Ventrilo , more recently the massively grown Discord , and finally Mumble , which is the open-source alternative of the gang. A few years ago, when I joined eyeo (a distributed company), several of the operations team were avid gamers, and had a TeamSp