Archive for February, 2012

Why (Most) Companies Don’t Learn

February 28th, 2012

I’ve been thinking about and researching the topic of organisational learning for some time now. Last year, I presented on the topic at LESS 2011, but realized it was time to take some time and write about it. So this is the first post of a series to explore the topic, which I’m also hoping will help me clarify my view on the subject.

Organisational learning. Should anyone care ?

My hope is that this goes without saying, but I guess that the first question to be asked is why should anyone care about learning? Some businesses make money staying still, while the world keeps moving. Full stop.

While this could be true for established business in the past, it’s something that is not so clear anymore. Gary Hamel makes a good point in his “Reinventing the Technology of Human Accomplishment” presentation: Change is changing, and it’s much faster now than it has ever been.

The world is changing, and faster than ever, so (every) company has to adapt, not only once but constantly.

Why is it so hard ?

A company has to learn. If this was an easy task, it wouldn’t be so rare, but creating a learning organisation is one of those things that gets harder the more you try and control it. If you want to form a learning organisation, a few questions you might think of are:

  • What does my company need to learn ?
  • If I had to setup the body of knowledge necessary to run my organisation, what would it be ?

While these could have been easy questions to answer 50 years ago, nowadays, in this ever changing (specially IT) world, whatever you write as being essential today might not be useful at all in one year’s time.

And the big issue is that most companies are not setup to deal with this problem. Instead of an evolving structure, modern organisations still have a very hierarchical structure based on top down control, with the vision of a CEO (put any other senior role here) that drives the strategy while most of the company just follows.

They have Project Management Offices that dictate how to deal with projects, architecture teams that say what can and cannot be done and common policies that dictate behaviour for everyone. Bjarte Bogsnes  has a good tale about how companie’s policies try to establish control over the employees:

“A friend of mine works at SAS. Even if he is trusted to fly planes around the world, if he wants to change his shirt more often than what the policy states, he needs a written authorization”

So the common alternative to evolution in this kind of structure are the well known “Change Programs”. They try to implement a top-down approach to change, that can be explained in two simple steps:

  1. Senior people decide how to move forward
  2. They teach the rest of the company how to do it

While step 1 is always a success, step 2 is usually more troublesome that people would like to think. And it’s not hard to understand why, since the whole idea of a change program is quite an unfair proposition to the affected employees, which could be described like this:

“You have to embrace change, but only the change we want”

As expected, people resist. Peter Senge has a quote that explains this situation quite well – “People don’t resist change, they resist being changed” – It’s natural that most employees will doubt and resist something that they haven’t been asked about. I would, and I’m quite confident that most people would too.

And as a result, money is spent, time and most importantly people are consumed through the process, and not much is learned in the end.

So is there an alternative to this situation ? Do you agree with this view ? Let me know what you think

Knowledge Sharing on Steroids

February 23rd, 2012

One of the challenges I’ve had to face a few times in my career was how to ramp-up a software development team, specially in what relates to knowledge sharing.

Why is it hard?

I still remember watching an old presentation from Dan North where he kept hiting on the same point, which was that there is always a story behind any decision made on a project. And that is the main problem I see when joining a new team: there is always story, and you probably don’t know it.

Working in a new codebase for me feels much like moving to a house in a new neighborhood. It takes some time until you know where all the shops are, what’s the best way to get anywhere and where can you buy stuff in the middle of the night. In a software project you don’t know exactly where things are in the codebase, it takes time to understand the rationale behind the design and you are afraid of making big changes, even when they should be made!

So when ramping up a team with a considerable amount of new developers, there is a risk they won’t be able to be effective for quite some time, or that in the urge to be effective they will end up changing what doesn’t need to be changed, being counter productive after all.

So here we go again

This challenge came up again in my last project, where we were starting to work in our second release and wanted to include a team of developers in China in what would turn into our new distributed team.

Gladly enough we were able to spend 2 weeks together as a colocated team in Xi’an, but still we needed to use this 10 working days to ramp up 5 new developers who had little or no experience in the codebase we had been working on.

This time we decided to try something out of the ordinary with some inspiration coming from my period at Thoughtworks University  (what Sumeet would call workscaping), in what could be described as a mixed of promiscuous pairing and very frequent showcases.

What does that mean ?

The idea was:

  • We rotate pairs every 2 hours
  • After each 2 hour block the team would stop and every pair would do a 5 min presentation on what they had done
  • We have a 30 min slot available at the end of the day for having a more in-depth discussion about topics that the new developers had doubts about.

Some of the benefits we expected to achieve were:

  • Everyone would work together quite a few times, improving the relationship between team members
  • The new developers would have an opportunity to touch different parts of the codebase quite soon, hearing the stories from the old ones about what was there and why
  • By presenting it back to the team, everyone would have a chance to raise questions and understand a little bit more about a specific topic
  • The constant sharing of information would enable newcomers to get more questions answered and deliver functionality quicker, which always helps with confidence

So the day would start with a normal standup, and after 2 hours the team would swarm and go around the room, hearing what had been happening. Pairs would then rotate and start again. Repeat that 4 times and the day is over.

How did it go ?

Overall the result was quite good in my opinion. Most of the results we expected to obtain actually happened, specially the communication within the team, which was great after a few days.

After one week of doing it most people started feeling the need of working more hours without interruption, so we changed our pace to 2 rounds of 4 hours and then eventually rotating pairs once a day, where we ended up stabilizing. Despite being earlier than expected, it felt like a natural point where people had enough knowledge to deliver and wanted to focus on that, which can probably be considered as a success.

Another Take at Distributed Retrospectives

February 15th, 2012

Some time ago I’ve wrote here about a small distributed retrospective that we have done in one of my last projects. While it was effective at the time, I’ve recently been in a distributed project for longer, and had the opportunity to learn another lesson from Herry.

In our project together we had a team divided between Melbourne and Xi’an and have been running retrospectives every two weeks. To avoid the common problems of distributed retrospectives, our team was using a simple format that worked (and is still working) quite well.

  • We began by having a 5 minutes chat with the whole team present and setting the goals for the meeting
  • The teams would then go into a 15 minutes offline mode, where they would raise and vote for the topics they wanted to discuss separately
  • After the initial voting, we would normally pick the 2 most voted topics on each side and discuss them all together.

While it seems quite simple, the separation for the voting and initial exchange of ideas makes the the retro feel much more focused and better than other distributed retrospectives I have previously attended, and definitely a format I will keep using for distributed situations.

 

Measuring Cycle Time, the Easy Way

February 9th, 2012

If you have heard about Lean and Kanban software development, one thing you might be doing is measuring the cycle time for the cards in our project, meaning the time between when a card is started until it’s finally done.

I’ve been doing it for a while, and have tried a couple of ways to actually get the data so far, going from having a spreadsheet where I would keep all the dates when cards transitioned (very detailed and very complex to maintain) to the usual noting down those dates in the card itself (less complicated but still troublesome, since people would forget to write on the card when they moved it).

Since I’ve started my last project, Herry introduced me to a new way, which as most good ideas, is so simple and good that I wonder how I had never thought about it.

The way we have been doing now is using stickers to keep the count of the number of days a card has been on the board. Whenever it starts to get played, we apply one _put your favourite colours here_ sticker to it for every day it is in play until it’s done. We currently just have two states in our board (doing and accepting) so we have two different colours to track the days in each specific stage.

The reason I find it much simpler is because you don’t have the problem of getting dates wrong anymore, or have to remember to note things on cards when they move. The only action needed is to apply a sticker to every card being played after the standup.

Feedback at LESS 2011

February 1st, 2012

I’ve been to quite a few conferences in the past few years and one thing that is always a contention point is how to gather feedback from presentations. Solutions that I’ve seen go from feedback forms and putting votes in a ballot to high tech iPhone apps where you can register your impressions.

At LESS 2011, the organizers ditched the standard forms and went with simple post-its for feedback.

Instead of answering multiple questions, all you had to do is to grab a post it (available in all chairs) and stick it on the right place on the door when leaving (picture below). If you had anything more to say, you could write it in the actual post it, which were then delivered as they were written to the presenters.

   That’s it! Simple and effective.