The level of software quality attainable is a reflection of an organizational business decision. There are many factors that influence this decision, including development, build and testing environments effectiveness, resources and their associated skillset, integrity, motivations and experience levels, commercial agreements, and adopted processes and productivity tools.
Over the last couple of years eSailors IT solutions has implemented big technological and organisational changes: from functional silos to cross-functional teams, from a work flow that looked like an assembly line to dynamic loops, from a monolithic platform to microservices, from hierarchical command-and-control to leadership as a team sport. This article provides a summary of their journey.
This article describes two novel practices for continuous delivery: Latent-to-live code pattern and Forward compatible interim versions. You can use these practices to simultaneously increase speed and reliability of software development and reduce risks. These practices are built on top of two other essential continuous delivery practices: trunk-based-development and feature toggles.
The book Effective Debugging by Diomidis Spinellis describes 66 different approaches for effective debugging of applications and systems.
How do you handle a long list of defects in your project? You don't. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them. 2
Gal Zellermayer describes a process for handling bugs 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. 2
Quality is one of the most overlooked areas of the software development process. 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.