This paper introduces the module linkage diagram (MLD). This diagram identifies communication bottlenecks between development teams in the release-planning phase. Managers can relieve these bottlenecks by reorganizing the team, and programmers, by modifying the code. Additionally, MLDs can indicate opportunities for releasing "loosely linked" software modules independently from the rest of the project. By separating critical loosely linked modules into independent releases, managers can deliver new feature content more effectively.