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

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

Git tools for keeping patches on top of moving upstreams

At work, we maintain patches for some pretty large open source repositories that regularly release new versions, forcing us to update our patches to match. So far, we've been using basic Git operations to transplant our modifications from one major version of the upstream to the next. Every time we make such a transplant, we simply squash together the modifications we made in the previous version, and land it as one big commit into the next version. Those who are used to very stringent keeping of Git history may wrinkle their nose at this, but it is a pragmatic choice. Maintaining modifications on top of the rapidly changing upstream is a lot of work, and so far we haven't had the opportunity to figure out a more clever way to do it. Nor have we really suffered any consequences of not having an easy to read history of our modifications - it's a relatively small amount of patches, after all. With a recent boost in team size, we may have that opportunity. Also the need for be

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