This is the seventh post in a series about what makes a team effective. Effective means, the team does the right thing to reach its goal. I’ve seen several projects that started well, but after about one year into the project problems arose. The developers started to do software archaeology before adding new functionality. They simply weren’t sure any more what happens inside their software. So they went from method to method and from class to class to guess what a change would do...
Effective teams: know your code
E