Seven Pragmatic Practices To Improve Software Quality
Incremental Changes Can Have A Big Impact On Quality
August 11, 2010
Why Read This Report
All software has bugs. Application development teams do the best they can to avoid and fix them. But developing quality software is hard. Why? Virtually all application development teams are squeezed by the need to develop and change applications faster, but few have the time to implement a full-blown, guru-based quality program. What they need are shortcuts — pragmatic changes that application development teams can make to improve software quality without getting the brass and rank and file in a tizzy. Forrester has identified seven pragmatic changes that can have a big impact on improving the quality of the software you deliver to the business: 1) define quality to match your needs; 2) broadcast simple quality metrics; 3) fine-tune team and individual goals to include quality; 4) get the requirements right; 5) test smarter to test less; 6) design applications to lessen bug risk; and 7) optimize the use of testing tools.
Already a Client?
Log in to read this document.
Become a Forrester Client
Customers are the new market-makers, reshaping industries and changing how businesses compete and win. Success depends on how well and how fast you respond. Forrester Research gives you insights and frameworks aligned to your role to shorten the time between a great idea and a great outcome, helping your teams win in the age of the customer. Contact us to learn more.
This report is available for individual purchase ($499 USD).Purchase
Table of Contents
- You Already Know The Importance Of Quality
- Seven Pragmatic Practices To Improve Software Quality
WHAT IT MEANS
- Pragmatic Practices Can Improve Overall Quality
- Related Research Documents