Modern Agile’s four guiding principles define a simpler, safer, speedier way to achieve awesome results: Make People Awesome, Make Safety a Prerequisite, Experiment & Learn Rapidly and Deliver Value Continuously. These principles are present in the products and services we love. Modern Agile doesn’t define what roles, rituals or practices to follow. You choose how to act on the principles.
Performing Code Reviews helps to increase code quality, share knowledge and responsibility, and build better software and a better team. However, the big question remains – what is it we should be looking for? There are a lot of different things to consider. This article will list a wide range of items to check, and drill a little deeper into two specific areas: performance and security.
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
The Scrum Field Guide - 2nd Edition is a "what to expect" book for organizations transitioning to agile, which aims to help teams to deal with issues that occur and fine-tune their own implementation. 1
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.