It was an interesting first day of the conference. Most speakers talked about their experiences when trying to adopt Scrum into their company. Some shared some interesting facts while others didn’t quite get their message through. The highlight was probably the first talk when Carsten Jabobsen told us how Systematic Software Engineering, a CMMI level 5 company, were using Scrum. They adopted Scrum after they had reached level 5, and the journey from level 1 to 5 took them 6-8 years and a lot of money. He claimed they got pay-back from their efforts, but I would like to see that calculation. My question is: “Could it be done quicker and cheaper if they adopted Scrum already in the beginning of their CMMI journey, instead of at the end?”

As for my own performances the speak went really good and I got some great feedback from the audience, however not everybody were convinced. They found the ideas really interesting, but since I couldn’t show any real results from any large scale project, they stayed a bit sceptic. Fair enough! I hope I get the opportunity to try it in large scale some time. At the moment I can only redirect them to the results of Corey Ladas and David Anderson.

2 Responses to “Nordic Scrum Forum 2008”


would you say that nordic countries are dealing differently in using SCRUM because of different management style and culture to deal with people?

How would you see intercultural scrum teams (communicating only over web)?


I don’t know if we do it very differently, but I do know that the Scandinavian mentality fits very well with Scrum. Scandinavian/Nordic organisations are generally less hierarchical and workers are very independant and more goal oriented than task oriented. This together with a direct communication style makes it very natural and easy to form empowered and cross-functional teams.

Some would claim you are not doing Scrum if your team is not co-located. I believe you can achieve good results despite not being co-located, but it’s definitely harder.

My experience is that team communication gets magnitudes better if you meet at the start of the project for some kick-off activities, such as workshops as well as some leisure time. Depending on the distance and the travel costs I would try to get the team together regularly. Perhaps for a common planning day at the start of each sprint, or something. But at least once in the project.