Thoughts on the Myth of Man and Month

The human moon myth derives from author Brooks's experience with IBM as the system computer family and its large software system OS project manager.

Brooks most of the project manager wrote this "People's Month myth", I think as a programming for bread where to eat the future of IT jobs, it is necessary to read this book. Brooks in detail with his work experience to introduce to others the necessary things the project manager should do on a project: First of all, you must understand what the customer needs, what functions to have, and then understand what the member can do and what the code can do. Finally, a detailed process arrangement is needed.

Once the members of the project confirm that there is no obligation to communicate with each other, the communication between the members should be promoted instead. This will enable the project to progress well. Instead of having problems, members are at the side of the deal. Of course, when the project is stuck, it cannot be blindly diaoren from elsewhere. This in turn makes the project more complex. New members can not quickly keep up with the project process, if the idea is not unified, will let the project stop development.

The reading of the myth of People's month and the explanation of the teacher's software project manager in class gave me a deeper understanding of the project manager position.

Thoughts on the Myth of Man and Month