In my last post I said we should let Scrum die. We can’t let Scrum die. It doesn’t behave like that. It will only die off its own accord if we die first and then it dies because it has no reason to exist. So you got to kill it. Here’s why (again?).
Software development is about people and the way people work alone and together. People create code in software development. Without that code, these people don’t exist; they have no purpose. Code is the creation of the people, and people live off this code. When the code is good, then life is good. When the code is poisonous, then people start dying slowly. When the smell of death is in the air, they look for help. Some stare into the mirror called Scrum. They see themselves and the way they behave. It’s an ugly sight. They realise that they should behave better. After all, software is about the way people work alone and together.
Regularly looking into the Scrum mirror, they improve their behavior over time, and everyone is happier than the moment before. That’s a nice view. Just look in the mirror and it looks good. Very rarely do they also look again through the window into the fields of code that feeds them. The poison is still coursing through their veins. They will die, eventually … by the host that they created that was supposed to nourish them. The only way to survive is to deal with the fields of code. Get rid of the toxins. There are two fundamental ways(*) that you can get rid of toxins: (a) eliminate duplication, and (b) make the code as you wish it to be.
If they just stare into the mirror and hardly ever look out the window, they will just exist on the plateau of complacency. In order to avoid that state of being, they need to focus on the fields of code. The urge to look in the mirror is strong, and as useful as it was, it becomes a very unbalanced state of existence.
So, look in the mirror, but look through the window too. Create fields of code without toxins so that you provide nourishment for the next person. That is ubuntu coding.
Actually, the only mirror you need is the person working next to you.
(*) Think deeply about these two fundamental things and try it out. Everything else will fall into place from this. For example, the act of eliminating duplication forces you to consider where to locate a single piece of code, how it should be used and where it can be used, etc. That is design and architecture. With duplication, you don’t need to consider any of those things. That’s toxic.