Цитаты из книги Software Project Survival Guide

Software project survival does not happen accidentally. The work that is required to make a software project succeed is not especially difficult or time-consuming, but it must be executed diligently from the first day of the project to the last.

Be sure that all project stakeholders understand from day one that on a healthy successful project development teams refine their estimates at predetermined moments over the course of the project.

Be sure miniature milestones are set up early in the project. As with other aspects of project control, it's easiest to exercise more control in the beginning and relax control as the project progresses.

Testing is a means of discovering the quality level of a software system, not a means of assuring software quality.

Requirements are not "out there" in the users' minds waiting to be gathered in the same way that iron ore is in the ground waiting to be mined. User's minds are fertile sources of requirements but the project team must plant the seeds and cultivate them before the requirements can be harvested. The most difficult part of…

The risk officer's function is to play devil's advocate during planning meetings and when reviewing planning materials (continually looking for potential problems)

Considering the amount of uncertainty contained in the project estimates even after requirements development has been completed, the best way to think of preliminary schedule and budget targets created at software concept time is as aids that help the development team identify features that cannot be delivered within the…

Several of the most serious software project risks are directly related to planning: - Failure to plan - Failure to follow the plan that has been created - Failure to revise the plan when project circumstances change

The cone of uncertainty has strong implications for software project estimation. It implies that it is not only difficult to estimate a project accurately in the early stages, it is theoretically impossible. At the end of the requirements development phase, the scope of the project will be determined by myriad decisions…

Good project leadership established a clear vision and then puts a process framework into place that allows programmers to feel incredibly productive. Programmers appreciate enlightened leadership that emphasizes predictability, visibility and control.