Sergey Galushko - Fotolia
My watchwords for 2015 are "Agile maturity."
I know it's not the next big thing. It's not a new initiative. Nobody is shouting it from the rooftops. But in 2015, I heard Agile practitioners use the phrase "Agile maturity" over and over again. You had to listen hard to hear it. It was a whisper, a phrase that kept coming up when I spoke with software pros about other topics such as continuous delivery, automated testing, better business engagement and mobile testing, to name a few.
I picked it as my 2015 phrase because Agile maturity -- that thing that software pros kept whispering -- is crucial. The big initiatives mentioned above are tough to tackle without it. A mature Agile practice does not guarantee success. But it provides a crucial underpinning to help make successful projects happen.
There's another reason Agile maturity matters. It's not a passing fad. No matter how long you have been practicing Agile, doing it at a high level of fluency is enormously challenging. It's an ongoing quest, according to software quality expert Matt Heusser, principal consultant at Excelon Development in Allegan, Mich. Successful Agile teams are continually "moving toward maturity," changing course when they need to, he said.
I asked Heusser and others whose words appear regularly in our pages for their definitions of Agile maturity. Here's what they said.
Don't act immature
Johanna Rothmanhead of Rothman Consulting
It's no surprise that teams that strive for Agile maturity understand the importance of mature behavior on the part of individual team members. They treat one another with respect and keep their egos in check. "When I think of the term maturity, I think about the old, French definition of the word: Having a studied and considered understanding of one's actions, and living with the consequences," said Heusser, co-author with Markus Gartner of the book Save Our Scrum: Tools, Tips, and Techniques for Teams in Trouble. He compared that approach with an immature one, characterized by "magical thinking, crying, attempting to 'get away with it.'"
Quality assurance engineer Abby Buell, a contributor on ITKnowledgeExchange, said, "Mature Agile teams are made up of … members who are respectful of each other and … have learned to work well and efficiently with each other." As teams approach Agile maturity, they move past "the ego problems that plague less mature teams," added test manager Mike Corum, weighing in on the same discussion.
Reflect and then refine
Another mark of Agile maturity? Getting good at reflecting on what works and what doesn't, then refining the software development process accordingly. Of course, this is part of the very definition of Agile, but becoming accomplished at it takes practice. "[Mature teams] reflect at regular intervals and experiment with their internal processes," said Johanna Rothman, head of Rothman Consulting in Arlington, Mass., noting that "Agile maturity occurs at the self, team, management and organization levels."
Agile maturity requires practitioners to "articulate why they do things, what problems that creates and why those problems are better than what they were doing before," Heusser said. "[They] understand the trade-offs involved in the software delivery process."
By contrast, less mature teams do things by the book. Following the rules has its place, of course. But over time that approach can result in rote actions and responses. For an Agile practice to evolve, you have to "move past the useless stand-ups (yesterday I worked on that, today I'm working on this, no obstacles),"noted Corum, posting on ITKnowledgeExchange. Mature teams refine their processes to adhere to the spirit of Agile, he said.
Can Agile maturity always be achieved?
Experienced Agile teams understand "there are always new problems to solve, always improvements needed," said Lisa Crispin, an Agile testing coach and practitioner, and co-author with Janet Gregory of the book More Agile Testing: Learning Journeys for the Whole Team.
What is Crispin's definition of Agile maturity? "In my experience, there's no mature Agile," she said. "I currently work for a company that's been Agile since the late '90s, and though I think we are more Agile than most, we still have to identify obstacles and try experiments to chip away at them."
Now, that's the most mature definition of Agile maturity I've heard all year!
Three signs you're part of a grown-up Agile team.
Beware "faux" Agile
With mature Agile, should there be a new Manifesto?