The document is an essay about the challenges of estimating time for software projects. It discusses how programmers often fail to accurately estimate timelines, costs, and progress, which can lead to projects going over schedule. Programmers tend to be overly optimistic in their timelines. Thorough system testing takes significant time to find and address bugs, but this phase is often ignored or underestimated in schedules, causing problems. In conclusion, the essay emphasizes the importance of properly valuing and estimating time for software projects.
The document is an essay about the challenges of estimating time for software projects. It discusses how programmers often fail to accurately estimate timelines, costs, and progress, which can lead to projects going over schedule. Programmers tend to be overly optimistic in their timelines. Thorough system testing takes significant time to find and address bugs, but this phase is often ignored or underestimated in schedules, causing problems. In conclusion, the essay emphasizes the importance of properly valuing and estimating time for software projects.
The document is an essay about the challenges of estimating time for software projects. It discusses how programmers often fail to accurately estimate timelines, costs, and progress, which can lead to projects going over schedule. Programmers tend to be overly optimistic in their timelines. Thorough system testing takes significant time to find and address bugs, but this phase is often ignored or underestimated in schedules, causing problems. In conclusion, the essay emphasizes the importance of properly valuing and estimating time for software projects.
Asignatura: Calidad de Software Profesor: Isaas Contreras Bentez
Bacalar, Quintana Roo
2016
Ensayo
The mythical man-month
What is one of the main problems for a programmer? Easy answer, the TIME. In this reading are discussed and several issues are discussed in relation to time, and how this affects projects and cited a part of the text More software projects have gone awry for lack of calendar time. The Reading mentions that programmers tend to have many failures estimating their times, and not only that, later in the same way that speaks when estimating costs and sell your product find it difficult In the same way speaks of having problems monitoring progress, and really do not have the certainty that much progress has been made in the project, and this leads to problems of time. Optimism, one word, sounds simple, but itsnt, the Reading mentions Programmers are optimistic, then use as an example to young programmers, saying they are the most optimistic in the industry. No parts of the schedule are so thoroughly affected by sequential constraints as component debugging and system test. Furthermore, the time required depends on the number and subtlety of the errors encountered. Looks simple, but the system test takes time and effort, two things that often are ignored and this brings problems in future, because as mentioned above, no time is respected or no criterion to follow the software release life cycle as it should and when the project is delivered come to light bugs and horrors. In conclusion, the time is something to be valued and today many programmers would pass through the triumphal arch.