Managing software project teams is a complex task further complicated by a continued increase in the size and complexity of software-intensive systems and the distribution of project teams. Given limited project resources, distributed teams require appropriate team processes and adequate tool support to help them remain focused on the most critical design tasks, thereby structuring the design process and improving team coordination. However, existing project management tools typically fall short. Software project management as a discipline is not unlike humancomputer interaction (HCI) in that both combine technical concerns with human psychological concerns. Both could benefit from a more systematic approach to applying theory to practice. One proposed approach to the science of design involves constructing a record of design rationale by leveraging design knowledge from previous projects. Extending the reuse paradigm from product-related knowledge to process-related knowledge could improve software project management by helping teams to externalize and maintain a physical record of their design process. A risk management model could help teams to prioritize design knowledge, allowing them to focus their effort on key design tasks.