How do you handle a long list of defects in your project? You don't. If it is not worth fixing a defect right now, it’s not likely that we will find the time to do it later. Also, it becomes more and more difficult over time to correct the defect, so it is cheaper to solve it now. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them.
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 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-fixing. 2
An interview with Eddy Bruin and Ray Oei about test plans in agile, how to make stakeholders aware that they can influence quality, and which agile practices they recommend for testing.
Moving your release cadence from months to weeks is not just about learning Agile practices and getting some automation tools. It involves people, tooling and a transition plan. 2
Gil Broza explores agile values, beliefs and principles, and explains how they can be used to drive agile adoption in his book The Agile Mind-set.
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
The book Fifty Quick Ideas to Improve Your Tests provides suggestions that cross functional teams that are doing iterative delivery can use to manage and improve their testing activities.
James Grenning talks about why people are not doing technical practices sufficiently or well enough, TDD and unit tests, and on becoming better in discovering "bad code”.
Software developers spend time and energy on building the best possible products looking at web frameworks, using a NoSQL or SQL database, etc. There's another equally important aspect: culture. 1