1 nota · última: 21 Sep 2015
Brooks argues that software schedules fail because communication overhead and complexity grow with team size. He also presents practices for preserving conceptual integrity, managing change, and limiting redesign.