Generally speaking, a decent rule of thumb to follow when thinking about team projects is that team projects “are bigger than you think”. Another rule of thumb to consider when deciding your approach is to look at the effect of a typical requirement on your software development project; if this requirement, for example, affects several applications or tiers (like front end, middleware and backend) then all these application should be grouped under the same team project. [Read more…]