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.
Katas are great for learning new skills or to improve existing ones but don't address the intensity we face at work when there is a raging fire such as a deadline, release date, fixing a bug in huge legacy code, etc. This article covers the skills of good developers and highlights changing your training approach to improve your skills for high-intensity and challenging environments.
While it is rare to hear the question, "Is this software safe?", the safety aspects of software are becoming increasingly important. The proliferation of IoT devices increases the widespread impact a small problem can cause. Several techniques exist to help developers analyze and improve the safety of software they create.
Modern Agile is four guiding principles that define a simpler, safer, speedier way to achieve awesome results. It has no roles, rituals or anointed practices. You choose how to act on the principles. 3
Learn two novel practices for continuous delivery to increase speed and reliability of software development and reduce risks: Latent-to-live code pattern and Forward compatible interim versions.
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.