Gal Zellermayer describes the 0 bugs policy, a process for handling bugs that is based upon 1 rule: whenever you encounter a new bug, you should either fix that bug, or close it as "won't fix" and don't think about it again.
One of the most overlooked but important areas of software development is quality. It often is not considered or even discussed during the early planning stages of all development projects, but it’s almost always the ultimate criteria for when a product is ready to ship or deploy. This article will explore how to measure quality and minimize the factors that negatively impact software reliability.
Hot-fix redeployment is a waste of time and effort at best, and often a source of further regression, Adam discusses some ready-to-use techniques that helped he and his team reduce the frequency of hot-fix deployments to almost zero.
The authors have concluded after analyzing 15 years of ATAM data that modifiability, performance, availability, interoperability, and deployability are key quality attributes for Agile practitioners.
Projects can be categorized as failures because of cost overruns, late deliveries or poor quality, but the right estimation processes can increase the likelihood of project success 16
We all want to delight customers with a quality product, and many companies focus on process to reach quality goals. But culture eats process for breakfast. How do you create a culture of quality?
"Enterprise Software Delivery" is the latest book by Alan W. Brown, and is a must-read guide for anybody concerned with the development and delivery of software in a large organisation.
Giving up certainty doesn't mean giving up predictability. This article examines 4 flow choices for software delivery and presents 3 choices for IT Delivery: Throughput, Flexibility & all out speed.
The QA role in Scrum is much more than writing tests and reporting bugs. In this article, Priyanka Hasija shares her experiences and the valuable lessons learned while serving as a QA in Scrum. 33
The software industry has created two separate roles: The developer and the tester. Traditional software development put these two at odds. Now, agile practices are bringing them together again. 2
When developers know how their applications are really being used “in the wild,” they will build better software. Sebastian Holst shows you how using application analytics.
Fabian Kiss makes the case for a lightweight approach to documenting the rationale and decision process behind design decisions to tie the source code to its meaning in the application domain. 4