Skip to main content

Agile Transformation Defined

I'm currently leading an agile transformation, and it has been an incredible learning experience.

It has also been a frustrating experience that causes me to drink to wretched excess, and sometimes kick my dog.  But that's a whole different blog post.

Some Background

My company went "Agile" 3 years ago, and I was hired as part of that process.  We did it mainly by bringing a large amount of offshore software development back onshore, and hiring people who had the right skills to replace the offshore team.  This may be the easiest way to do it, and explains why we were successful where so many others have failed.

This Spring, one of our remote offices was having some trouble delivering a flagship product, so the suits decided that a leadership change was in order.  They moved a couple of people around to make room, then appointed my boss as the interim leader of the remote office.  Being a savvy businessman and a keen judge of character, he charged me with leading things from the engineering side.  (The fact that I held my breath and threatened to cry if he didn't let me do it may have had something to do with his decision.)

Compared to my previous experience, this has been a much rougher ride.  There are a couple of reasons for this: 
  • First and foremost, the people already on the ground weren't hired with agile development in mind - most of them had to be sold on the concepts before we could get them on board.  This is by no means done yet.
  • Second, the people (I won't call them a team, because they're still not) had never been part of a healthy development group, and had no idea what it felt like.

I'm not maligning the people.  They're smarter than most of the developers I've worked for, but they didn't sign up for this.  Three of them have already taken their services elsewhere.  That's actually an opportunity for us because we now have room to hire people who do want to do this crazy Agile thing.
You can't force a culture on people, it has to grow by itself.  And it won't look like what you expected when your'e done.

OK, so what does "Agile Transformation" mean?

There are probably as many versions of "Agile" as there are people practicing it.  That's why I usually put it in quotes.  The way we do it is:
  • We don't need permission to build in quality - we use the engineering practices of pair programming and test driven development.
  • Everybody that can code does - managers are programmers too.
  • Build a learning culture - anyone can do a short presentation or hands-on exercise to teach others, and many do.
  • We set aside a day every few months for an in-house software conference, usually technology focused.
  • The 60-80 developers (1/3 - 1/2 are contractors) we have at any time, are split into 4-6 teams based on products or platform projects.
There are a lot of little cultural quirks, but that's the core.  Applying the same methods to a team 1/5 the size should be easy, but it's not.  

(Photo by Алексей Харченко, and no, I can't pronounce that either)
1 comment

Popular posts from this blog

Agile Performance Management: Why Performance Reviews Suck

Many thanks to Mary Poppendieck, who wrote about this topic in 2004, and proposed a comprehensive solution.  She is the inspiration for much of my thinking on this subject.  She is also a better writer than I am a cartoonist.

Performance reviews suck.  I don't know of anyone who goes into their appraisal without some trepidation.  Your boss is guaranteed spring some surprise criticism on you that is ill-informed or misses the point as you see it.  It's a real challenge not to get defensive about that.

The only thing that makes your own performance review suck less is having to give them.  As a manager, I have dished out quite a few, and some of them went pretty badly.  (To the people at my first management job: Thanks for helping me learn how to get better at them.  Your sacrifice was not in vain.)  Since then, receiving one isn't nearly as gut-wrenching, if only because I try to make it easier for the guy on the other side of the desk.  I've been there, and I know how …

Windows 10 Driver Issue with Falcon / Z-77 Keyboard

Windows 10 has an issue with this mechanical keyboard (which works great, BTW).  It's a Chinese-made keyboard (aren't they all?), but it doesn't have much English-language support.

I captured a few screen shots of how to fix it in case someone else has the same problem.  (I got the instructions off of Tom's Hardware, but it doesn't have screen shots & isn't clear on some of the details.)

First, open up Device Manager and select the controller under USB controllers (not under keyboards).

Next, choose "update driver" from the Drivers tab.
Then choose the "browse" option (search doesn't find anything).
Then select "Let me pick from available drivers on my computer."
Finally, switch it from the ND device (which is the wrong one) to the generic USB compatible one (which works fine on my machine).

You might want to clip these instructions into your favorite notes software because:

You need to do this for each USB port you plug in…

Showing Off: How to Do a User Demo

Rather than repeating what has been said elsewhere, here is a nice short post on agile-for-all that covers the basics.

Here are a few things for my own future reference and teams that I'm working with...

Try to keep each demo to 5 minutes or less.   If it's longer than that, it's possible that you should be demoing more than one story.  More likely, you're just being too wordy.

TALK LOUDLY.   No, louder than that.  Louder.  Do you feel like you're yelling?  OK, that's about right.  You need to put your voice in public-address mode for 5 minutes.

Focus on why your audience should care about the story  This is particularly important for back-end work.  For example: Your story generates a feed of XML that will be consumed by another application. Show the output, and point to a couple of salient features in it.  Then be done.

The important part of the above is "show the output."  Showing the end users how to interact with your service is a separate sit-d…