How do you handle the technical debt in your development? In your practice, how do you integrate, or aggregate, the framework between teams?

[Dingshan Li]

For technical debt, in my own projects, is not handled very well. Because we are working on a huge legacy product. We are trying to improve it. The first thing we are going to do is to introduce TDD to the team or at least to help the team to start to write real unit test. I think it is a very  practical way to help the team to reduce the debt. Another way is to help the team to learn how to write clean code. For framework, like I mentioned in 2nd question, I would suggest to organize a core team to work on the framework establishment in advance to set up a minimum common base. Then kickoff all of the other teams work. But be careful, I am not suggesting to take long time to have a big architecture design first. I am saying to set up minimum common technical base so that the whole product teams can start to develop the first feature. The whole framework / architecture will be keeping on enhancing, refactoring during the whole life cycle.

[Dingshan Li]

From Hugo:

TDD and Continuous Integration help the code quality, but concerning framework or architecture design, in my opinion, it depends on the capability of your team members, to some extent. Maybe I'm wrong, but the problem I met is that my team have to rework frequently. We have to refit the framework frequently, based on the new demands coming up in new sprints. That's really annoying. Did you meet the same problem? Did the team members feel upset, leading up to the morale sagging?

I'm wondering whether this is a birth defect of Scrum. Of course, if you love a girl, you have to love all her defects. But I still wanna see if a plastic surgery can help.

If you know any good plastic surgeon, pls tell me. ??