Communication between programs should occur through as many channels as possible.

- Informal communication: Clear definitions of intergroup dependencies can encourage informal communication among teams.
- Meetings: Regular meetings can be held, where one team or programmer presents technical details. This can help to identify and resolve misunderstandings.
- Project Workbook: A formal project workbook can be created to document the technical details of the project and serve as a reference for all teams involved.

## Project Workbook

The project workbook should define a structured framework for organizing all documents related to the project. It should include, at a minimum, the following sections:

- Objectives
- External Specifications
- Interface Specifications
- Technical Standards
- Internal Specifications
- Administrative Memoranda

One of the challenges of using a project workbook is that it requires everyone involved to read it. Therefore, it should be easily accessible, and users should be able to quickly see any changes made to the document, without having to re-read the entire document.

However, not everyone may be comfortable with this approach, as some may prefer to shield individuals from unnecessary complexity. This approach requires that all interfaces are complete and that the necessary documentation is in place.