It is very easy as a development team each developer just focuses on what he/she has been assigned and is not aware of what his peers in the project is working on. But from the application perspective it is not restricted by who is working on what feature rather every feature has to work cohesively together. So it is very important that a developer understands his/her module dependencies as well as understands the modules that are dependent on his/her module. Much important than this is to understand how the module that he/she is developing fits in the overall application and how critical it is and what value add it brings in from the business perspective.

In this process usually in a medium to bigger projects developers try to fail in understanding this. The effect is there will be unnecessary issues cropping up during integration. More than the issues I have realized a lot of times a lot of time is wasted on finding out who was the core cause of the problem rather than finding out the core of the problem. Usually this finger pointing exercise ends up like a traffic deadlock with no clue as to who caused it. As said even if the team ends up in such a situation there is no need to find out who caused it rather the team should try to release the deadlock. To release the deadlock at least one person has to say that he/she will fix everything from his/her side so that the problem is solved. Avoiding the finger point deadlock is the best but if that situation arises, see if you are that person who can release the deadlock.