2 Comments

I loved the technique of asking your team. Sometimes this step is enough to diffuse a lot of the frustration - as you will definitely take something from what was raised, and everyone will understand why there might not be enough time for everything. I did this once in a 'team focus day', and it was a huge success. We divided the tech debt among us, and each developer was reponsible for leading a single area.

For us, it's a bit less than 33%, it's around ~20% of time. It is usually not planned in the quarterly planning, but the estimates of work are given with the assumption that there will be some technical debt along the way.

And great book recommendations! :)

Expand full comment