Managing Software Quality Business Risk

How to manage quality up, and risk down. This invaluable guide to project planning and strategic decision making for software developers presents practical and realistic planning techniques to increase chances of a project delivering to time and budget. Offering clear explanations and real-world experiences, the key components of technical management are laid out as templates and checklists to assist managers with their project development. With thirty years of experience in software development, Martyn Ould provides:

* Proven strategies for a disciplined approach to project planning

* Steps to take in 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

How to manage quality up, and risk down. This invaluable guide to project planning and strategic decision making for software developers presents practical and realistic planning techniques to increase chances of a project delivering to time and budget. Offering clear explanations and real-world experiences, the key components of technical management are laid out as templates and checklists to assist managers with their project development. With thirty years of experience in software development, Martyn Ould provides:

* Proven strategies for a disciplined approach to project planning

* Steps to take in 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

Martyn Ould has spent thirty years in software development, mostly with UK software houses, Logica and Praxis, and was latterly with Deloitte Consulting. His role has ranged from developer and manager on projects to setting company software engineering policy. He became an independent consultant in 1998 and now consults for clients on the software engineering process, specialising in project audits and rescues, reviews of software development methods, and risk management. He contributes articles, reviews and papers to the computing press, and lectures to public, government, university and corporate audiences.