Estimating too low on a software development project can destroy your budget and ruin your project schedule. Here's the reason why. I have been developing software for more than twenty years, and I have experienced first-hand the consequences of estimating too low (and estimating too high). Estimates at the beginning of a software project are rarely accurate, given the team's limited knowledge of the project. More often than not, users don't yet know all of their own requirements for the system to be developed, and developers don't yet know everything about the domain in which the solution will operate. Building software is a process of continuous improvement, and a well-run project attacks the areas of highest variability first in order to reduce uncertainties as quickly as possible. Ideally, your estimate for a software project should be allowed to evolve along with the software itself. And remember: the potential for an exponential overrun on cost and/or sche...
This code of ethics was developed by the IEEE-CS / ACM joint task force on Software Engineering Ethics and Professional Practices . It was jointly approved by the ACM and the IEEE-CS as the standard for teaching and practicing software engineering. This summary version of the code of ethics summarizes aspirations at a high level of abstraction. The clauses included in the full version of this code give examples and details of how these aspirations change the way we act as software engineering professionals. Without the aspirations, the details can become legalistic and tedious; without the details, the aspirations can become high sounding but empty; together, the aspirations and the details form a cohesive code. Software engineers shall commit themselves to making the analysis, specification, design, development, testing, and maintenance of software a beneficial and respected profession. In accordance with their commitment to the health, safety and welfare of the public, software ...