so true! especially with the typical deadlines in I.T, if there isn't explicit time scheduled somewhere to clean up, improve, catch up with all the little annoyances and "good enough at the time" patches, technical debt gets out of hand quickly. And it starts having a knock-on impact on future work, because the more messy the foundation is, the harder it is to maintain & extend.
I think what you're suggesting also helps to diminish the "just rush and throw it over the wall when you're done" mentality, which might help encourage a bit more care & tidiness.
4 days a month dedicated to improvement. And then do stuff like:
so true! especially with the typical deadlines in I.T, if there isn't explicit time scheduled somewhere to clean up, improve, catch up with all the little annoyances and "good enough at the time" patches, technical debt gets out of hand quickly. And it starts having a knock-on impact on future work, because the more messy the foundation is, the harder it is to maintain & extend.
I think what you're suggesting also helps to diminish the "just rush and throw it over the wall when you're done" mentality, which might help encourage a bit more care & tidiness.
Yes, i think there is much to gain when these improvement days are done right.