This is RonJeffries.com, the combination of new articles, XProgramming, SameElephant, and perhaps even some new items never before contemplated. Copyright © 1998-forever Ronald E Jeffries

There are myriad ways to optimize teams, but all too often we ignore the individual. When the individual is overlooked, the software production engine can be severely…

What if the Agile software movement was the manifestation of an entire industry that was, just, like, dealing with some stuff right now?

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.

When the Manifesto for Agile Software Development was first published, it was not a process, but a set of guiding principles. Two of the core, foundational principles of agile development are reflection and continuous improvement. By creating tight feedback loops of iteration, analyzing the meta-process of product development, and constantly experimenting in order to improve communication and efficiency, these early agile teams were able to efficiently deliver high quality software while being able to quickly adapt to the shifting priorities of the business.

Continuous delivery is a set of principles, patterns, and practices designed to make deployments predictable, routine affairs that can be performed on demand at any time. This article introduces continuous delivery, presents both common objections and actual obstacles to implementing it, and describes how to overcome them using real-life examples. Continuous delivery is not magic. It