A Book Call The Mythical Man Month

1458 Words Oct 12th, 2015 6 Pages
Man Month which represents the production effort a single persons in a 4 week period. This is also known as labor month. To figure out the total hour of a man-month is done this way. A man day usually runs 8 hours a day for five days a week which equals forty hours a week (8 hours a day * 5 days a week = 40 hours a week). In a normal mouth you will have for weeks within that month, so we take the forty hours a week and multiply that by four which will gives us one hundred and sixty hours a month (40 hours a week * 4 = 160 hours a month) . Brooks 's law says that the possibility of measuring useful work in man-months is a myth, and is hence the centerpiece of the book.
In 1975 Fred Brooks wrote a book call The Mythical Man-Month. This book was about a claim for software project management and introduces Brooks’ law. It also regarded widely as a classic on the human elements of software engineering. This was based on experiences of Brooks’ observation while managing the OS/360 development at IBM. Brooks’ added programmers to a project that was falling behind schedule. This will later put the project further behind then anticipated. Brooks’ also wrote an ALGOL complier that would add six more months onto that project. By incorporating more manpower to a software project that already behind will only makes it later.
Project cannot be partitioned perfectly into discrete task within complex programming projects. This will have to be done with communication between the leaders…
Open Document