How we used the improvement kata to gain 25% of productivity - Part 3
This is the third post on a series of 5 about the improvement kata. If you haven’t read the beginning of the story, I recommend you start from part 1.
Recent Posts
How we used the improvement kata to gain 25% of productivity - Part 2
In my previous post, I described the productivity issue our team was facing. How retrospectives did not work, and how I started looking at the improvement ka...
How we used the improvement kata to gain 25% of productivity - Part 1
If you are serious about continuous improvement, you should learn the improvement kata.
Throwing code away frequently
Here is the main feedback I got about my previous post eXtreme eXtreme Programming.
eXtreme eXtreme Programming (2017)
What would XP look like if it was invented today ?
5 Remote energizer tips that will make your remote retrospectives rock
Do you remember how people who are not used to the phone tend to shout in it, for the message to get far ? Read on and I’ll explain how this silly habit will...
Forget unit tests, only fast tests matter
Don’t worry if your unit tests go to the DB, that might not be so bad.
10 things to know that will make you great at refactoring legacy code
We write tons of legacy code everyday. Experienced developers understand that legacy code is not something special. Legacy code is our daily bread and butter.