This content is part of the Essential Guide: Making the Agile development model current again
Problem solve Get help with specific problems with your technologies, process and projects.

Is Agile stuck? Looking for answers at Agile2017

It’s hard not to ask the “Is Agile still relevant?” question today. And it’s harder to still to hear some of the answers, ranging from straight up “No” to “too much focus on process” to “they’re their own worst enemies.”

That’s why, in advance of Agile2017 next week, I reached out to Ronica Roth, adviser and team lead for agility services excellence at CA.

Roth says the negativity is inevitable (though she’s quick to add she’s eternally optimistic). “There are too many people who’ve hung out their shingles as consultants and focused too much on the process and gotten stuck there,” she said.

Her solution is simple: get back to basics, which in this case means have a clear idea of what your goal is before you start anything. “Our message to customers lately: go in knowing what outcome you have in mind. Have a clear hypothesis why you want to be ‘Agile.’ You need to apply some lean principles to it and be clear about what aspects of Agile you need to leverage to get better results.”

And no matter what, don’t listen to the naysayers and particularly to those who hold your feet to the fire because your “process” isn’t sufficiently Agile.

“If a consultant or coach says you’re not doing Agile right I don’t want them to work for us,” Roth said flatly.”Agile is all about being learning driven and not plan driven. It’s about paying attention to what’s working and to customers.”

In fact, Roth says she sees a time when we won’t be calling anything Agile, or Lean, but rather just “modern software development.”

Her advice for what to attend at Agile2017, besides her own session of course? “You want to go to anything related to culture and leadership because that’s going to transcend whatever process you’re focused on.”

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

I think that most of the agile community is built around "software agile" and they are completely clueless when it comes to other industries adopting agile.
There appears to be no concern whatsoever for other industries adopting agile. The focus is always on software team. I contend that there is much larger potential in adoption of agile outside of just software team. Fortunately, there are some tools that help with this adoption. For example, Ravetree is a nice tool for whole company agile. It's not just about a tool, but it helps to know that others are embracing the adoption of agile beyond just software teams. 
The big lie that agile is new did not allow anyone to learn from history.  My System Analysis and Design textbook and class in 1983 described all software development as happening in iterations.  The iterations can be small (develop a small piece, install in production a small piece); or the iterations can be large (develop the entire hundred million lines of code; then install); or anywhere in between. 

My 20 years business consulting experience prior to IT told me  the rest of the world worked in iterations.  Some retailers change their product line and ad campaign very gradually.  Others change their entire store layout and image in a flash point. 

I saw plastics manufacturers who used small iterations and those who used big iterations. 

"There is nothing new under the sun." as a wise man said a couple thousand years ago.