Learning organisation

More and more software development departments are converting to agile methodologies - since agile is the key thing to be right now. As long as you're agile everything is super! Or is it?

This means that many software development departments adapts agile methodologies without really understanding the basic principles of which the frameworks are built upon. When you don't understand why you are doing something a certain way then you don't understand why you just can't do it in another way or don't do it at all.

I know e.g. of a development department that after using SCRUM for 6 months don't do retrospectives, since they don't really see the use of it. What is SCRUM without retrospective, how can you learn and improve without the basic mechanism in place.

In order to be able to learn and improve - do your retrospectives!

Learn to forget

Learn to forget. The first time you hear this sentence you are knocked off your feet, but when presented with the concept of learning to forget you can start to appreciate it.

First you learn, then you understand, then you understand why you understand, then you forget - so learn to forget.

This is the Asian logic as it was presented to me.

In west it has recently been in the spotlight, thanks to the promotion by the pragmatic programmers, and is known as The Dreyfus Model of Skills Acquisition.

Tomato or Tomato. It is worth checking out.