Anyone
who knows me first hand in or from the corporate world knows I’m first and
foremost an Agilist. Whatever my title is, at my core I’m an Agilist. That
means I live and breathe the principles of what it means to be Agile, and I’ve
done so for quite some time now. Sure, I can do and follow traditional
practices when it’s called for, but when it isn’t it tears my heart out. When I
write ‘Agile’ it’s not a typo either; anyone can be ‘agile’ without being ‘Agile’
and some companies out there may still be doing it very well.
A
conversation I recently had with a senior R&D manager included her saying “there
are a thousand ways” to be agile. And while that is true there are just as many
or more ways to pretend to be agile and not reap any of the benefits that exist
by truly being Agile. The following platitudes are a few examples to highlight
why some companies have ‘adopted’ or ‘embraced’ agile practices and are still barely
or no further along in enhancing productivity, quality or engaged teams.
The
companies and teams who say they’re taking a ‘blended’, ‘modified’ or ‘hybrid’
approach to Agile have most certainly adopted something out of a book or
webinar on Agile but at their core they’re still 100 percent pure waterfall. I’ve
lost track of the number of examples I’ve witnessed or read about that show how
much this is the case, and how many billions of corporate dollars are lost
every year as a result. It’s enough to almost make a grown businessman cry.
A very
wise uncle of mine a long time ago shared with me Mark Twain’s definition of an
expert, “someone from out of town.” I’ve always remembered that and been
saddened within my career that so many others did not have access to uncles
like mine. How that applies here is when companies choose preferred employees
with strong influencing skills to attend a conference or something on Agile.
That in and of itself can be very good, but only if those same employees are personally
interested in the topic have something to lose if they don’t adapt to and adopt
to what they learn. Similarly, if you’re going to spend budget money to send
those people somewhere, please, please, please make sure it’s from someone who is
actually qualified and certified to do that. For example, someone with CST
after their name would be good. About a year ago I was speaking with someone in
a team lead role at a company who went with the lowest bid. That trainer told
the attendees that testers should “go for coffee” while the developers plan the
backlog. That company has been adopting agile for about six years now and still
hasn’t seen one quantifiable improvement in how they manage projects or
products.

Finally,
like any activity, being Agile takes practice to get good at it. Some would
even say 10,000 hours of practice. So send people on courses, attend
conferences, hire a consultant, whatever you need to do to grab that ‘Agile’
brass ring. Just don’t keep doing what you’ve always been doing except now with
some agile term on it that sounds good. You won’t reap the promised benefits
(no matter how many excuses are forthcoming) and it tears the heart out of us
who really care about this stuff.
No comments:
Post a Comment