There has been a lot of misinformation about the nature of DevOps and its relationship to (Big A) Agile. Our Agile Architect explains why DevOps is an important component of (little a) agile, plus offers the top five DevOps misconceptions dev teams often have.
Quality assurance has long been an important component of an agile team. But times change. The introduction of new capabilities like ubiquitous cloud computing, containerization and microservices changes the way we think about QA. Here's how.
Agile is not a hard science like physics or chemistry. There is no fundamental theorem of agility. But practices in agile act along empirical scientific principles in that experimentation can lead to measurable results, reproducible across teams in similar conditions. So why does each agile team feel compelled to rediscover this again and again?
Our Agile Architect recently celebrated his 10 year work anniversary and uses this as an opportunity to look back and see how agile has changed over the last decade.
Things agile developers want to tell you but won't.
Our Agile Architect talks about the benefits of T-shaped people in agile and the dangers of stressing broad knowledge and participation over deep expertise.
Our Agile Architect discusses strategies for working with a product owner that can't hold to a decision long enough to see it realized.
It is difficult to solve a problem if the problem itself cannot be stated clearly. How does one "create a compelling user experience that will double our sales" or "build me something really cool"? Our Agile Architect discusses why the first problem an agile team must often solve is to define the problem itself.
After tearing down code branching strategies in a previous column, our Agile Architect demonstrates a different way to support parallel software development that fosters greater agility and speeds development.
Our Agile Architect shares a success story of extreme agile taken not just to the edge but over it.
We have the best software development tools in history. Why are our developers so afraid to refactor? Our Agile Architect explores how powerful code management tools can lead to powerful problems that inhibit agility -- and what you can do about them.
This is the completely true and not at all exaggerated story of how I, the Agile Architect, saved the Earth from complete and utter destruction. I'm sure there's an agile lesson in there somewhere.
Agile software development can be stressful. Recognize it, admit to it, deal with it, fix it.
Agile proponents promote self-organization. But what does this really look like? It turns out that achieving real self-organization takes...organization.
Who needs respect? It's more important to be right! And to be right, you have to be heard. So go ahead and talk over your colleagues. It's for the betterment of the project. Am I right?
A standup meeting is supposed to be an effective way to have a quick, meaningful team meeting, yet it is routinely despised as being too long and a waste of time. And it can indeed be a waste of time. Our Agile Architect explains why you might just not need a standup.
A standup meeting is supposed to be an effective way to have a quick, meaningful team meeting. Yet it is routinely despised as being too long and a waste of time. Our Agile Architect investigates ways to turn that around.
Agile rules can sometimes become a barrier to progress and even be perceived as impenetrable. Our Agile Architect spins a story about recognizing these artificial barriers and how to break through them.
If you've seen any trailers for movies lately, you know that superheroes are the new hotness. In a blatant rip-off of the genre, our Agile Architect describes how to have your own secret origin as a super software developer.
Our Agile Architect, for whom Spock was his primary emotional role model, brings in a ringer to talk about the soft skills required to be successful in the agile world.