The Agile Manifesto Principles: Self-Organizing Teams
Group of adults organizing their work

The best architectures, requirements, and designs emerge from self-organizing teams. The cultures that are trying to adopt agile are usually command-and-control, because most organizations are. This means that there’s a boss who tells their subordinates what to do, and then those subordinates tell their subordinates what to do. Agile attempts to flip that script upside […]

Read more
The Agile Manifesto Principles: Welcome Changing Requirements

Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage. In traditional development methodologies, like waterfall, a customer might try to specify how a system should look and behave completely upfront before they even start development. The problem with this is it assumes that it is possible to completely […]

Read more
The Agile Manifesto Principles: Maximizing Through Simplicity
abstract backlight black

Simplicity—the art of maximizing the amount of work not done—is essential. When I first started in development, I tried to plan for every possible situation. I was given the requirements, but always asked “what if?” What happened more often than not was I’d build a feature and then never actually implement it because either the […]

Read more
The Relationship between Agile and DevOps

Many are beating the drum that DevOps is something new and different—just like agile was new and different before it. Make no mistake, DevOps fixes an age-old conflict between software development and operational teams, but it’s not new. In fact, the DevOps philosophy is ingrained within the Agile Manifesto, and one could argue that DevOps […]

Read more