Invaluable guide to project planning and strategic decision making for software developers. Managing Software Quality and Business Risk How to manage quality up, and risk down If you were investing in a costly software development project, which horse would you back - managerial technique or technical solution? In the software development arena, you will often get two opposing views to this question depending on whether you ask a manager or an engineer on the team. Equally motivated to ensure the success of a software development project, each will dig deep into their domain for solutions. Martyn Ould presents practical and realistic planning techniques to provide managers and senior members of software project teams with a pragmatic means of increasing the chances of a project delivering to time and budget. Inside you will find:
* proven strategies for a disciplined approach to project planning
* steps to take in assessing risks and uncertainties in the project
* reliable methods for reducing risks to an acceptable level
* a quality planning process that is rooted in the technical requirements of the system
* insight into monitoring and measuring project progress
* real world experience through case studies and examples
Visit our Website at http://www.wiley.com/compbooks/
Jedes Jahr verlieren Unternehmen Millionen durch Softwarefehler. Entwickler sind permanent auf Suche nach verbesserten Möglichkeiten der Qualitätssicherung und -kontrolle für ihre Produkte. Einer der erfolgversprechendsten neuen Ansätze fordert, daß - ebenso wie in anderen Industriezweigen - auch in der Software-Entwicklung Verfahren des Qualitäts- und Risikomanagments angewandt werden. Dieser handliche Führer macht Sie vertraut mit diesen Techniken und Methoden und zeigt Ihnen, wie Sie diese auf Ihre Projekte übertragen. (cat06/99)
Martyn A. Ould
Computer Science Informatik Informatik, EDV / Informatik Programmierung u. Software-Entwicklung Programming & Software Development Softwareentwicklung
"Managing Software Quality and Business Risk addresses itself to software project leaders, managers and technicians alike, pulling them temporarily away from their own discipline and encouraging them to view the gestalt of project planning. You get an overview of what each of these areas of expertise has to offer: a technician, for example, might learn the importance and practicality of risk planning first, followed by quality planning. (The software project team that does not calculate for the eventualities of many kinds of failure is re-enacting a tragedy of Shakespearean proportions.) The unifying theme is studying and perfecting the planning process, and ensuring that your project plan has minimised associated risks and maximised quality.
The style is clear, and though the writing is studded with a fair amount of jargon, it clearly lays out management information and perspectives. On the practical side, the author takes you through several techniques and introduces insights from those skilled in coping with market forces or with service users, often underestimated, misunderstood or completely ignored by programmers. There are plenty of interesting, well-designed grey tone charts and diagrams that instantly bring to the fore the subject or strategy being developed, and examples are given throughout. This is a book that is best approached as a good, thought-provoking read rather than as a reference.--" -Wilf Hey, Amazon.co.uk
()