project management - How much of the Mythical Man Month still applies? -


This book was written in the time sharing system, procedural programming, and software engineering experience in about 30 years of age. How much book still holds true with improvements in existing libraries, high level languages, IDEs and documents available on the Internet?

I can believe that adding new people to a project can initially slow down, I think unit tests, separation of concerns, and other forms of automation and design improvements like new ones Members were quickly taken into the book to become productive to the team, good design documentation and procedures were in place to handle this project.

I do not have experience with big projects or big teams, so you are interested to hear who among you has experienced the experience of those people: I was thinking that wiki, instant messaging , And in general, new communication devices like the Internet have communicated to reduce the time. Based on the responses of everyone, I would say that any increase in the communication capacity has been offset by the increased complexity.

There are still things to tell us in the book, and I have experienced problems in communication for one Which increase the size of the team. You should know that there are no new concepts, such as separation of unit tests, concerns etc.

However, some things have not been on the test of time. I do not believe that writing a ASSCI flow chart in your code is a good idea, and it has been suggested that many people (mostly Charles Simony in MS) have tried and did not work very well from the "surgical team" approach Found to be / P>


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -