Organize Source code tree based on functional unity

In a team development environment , we need to come at a Work Break Down structure. Since the expertize vary among the developers , we try to take into consideration the strength and weakness of developers in the team.

To a certain extent , Architecture of the application will be colored by the team composition as well.

Try to have an architecture were Layers are having some kind of "Closure of Operations " and communicate through well defined evolvable (!) interfaces. We need to distinguish the above from the Work break down structure.

When we do WBS , there is a potential for having modules organized along that line(Organizing the code along the political lines aka Political units ) . We should try to have an organization where Functional units are clubbed together. With the help of modern version control systems , it is possible to have such an arrangement

To Sum Up,
        Architecture for the team ( I know it is counter-intuitive )
        Source code organization based on Functional Unit
        Once some kind of stability has arrived , Collapse some Layers for Performance