Archives for 13 May,2016

You are browsing the site archives by date.

Going Agile Can Be Scary: Chapter Two

Risk is Scary…

More than a decade after my own transition to Agile and after having the privilege of watching other teams make their transitions to Agile as well – I have realized how scary it can be to take that first step into Agile development.

Why? Because Agile transitions typically occur in a moment of crisis or upheaval.

People reach out for something to help them out of their chaos. Agile typically arrives at a time when teams are over worked, stressed out, and pretty much struggling just to maintain their basic requirements. Taking time out of an already over-burdened schedule to learn something new seems like a risky endeavor.

Another thing we see: Agile is sometimes adopted at the beginning of a huge new project when process management becomes critical. Starting a huge new project is stressful, and applying a new methodology can feel like you’re only adding to your pile of stress.

A change in leadership can also bring a change in methodology. An organization acclimating to new leadership wonders how much things will change when they are asked to adopt Agile. It’s stressful to not know what the future holds.

Very rarely will I see a successful, productive, happy, thriving waterfall shop make the choice to go Agile.

When you decide to apply a new methodology – a whole new process in many cases – during a time when you’re already stressed out, that can feel like a risk.

Fear Slowly Fades…

stepsAgile adoption is a step process. First you learn the most basic aspects of Agile and your chosen methodology, and then you begin applying them.

You don’t need to be an Agile expert to begin.

In our Agile Foundations course, for example, we begin by teaching the basics of Agile – which are really only a set of principles and values. (“Agile” itself is not a process to follow.)

Next, we quickly go over a few of the most common Agile methodologies such as Scrum, XP, and Kanban.

We walk you through the beginning steps of your chosen methodology, and engage teams as they begin applying what they’ve learned to their own work load.

Before anyone realizes that they’re Agile, they’ve begun!

It’s a lot less painful than most people anticipate it to be.

But that first step? Well, that first step can be scary.

It’s less scary when you’re moving forward with experienced trainers and coaches. Call us today to discuss taking your first step. You’re going to ace this! We’ll show you how.

Talk to Us Today

Going Agile Can Be Scary: Chapter One

First…

I vividly remember the first time I was introduced to Agile. I was working for Intuit at the time, building a new piece of finance software. The project was on schedule, but only because we were all working 12 hour days, and working 7 days per week.

working lateThe people I worked with – all great people – and I rarely spoke about anything but our project. When we left the office, it was to go home, see our families for a bit, then sit back down at a computer and continue working.

In hindsight, I suppose it felt a bit like treading water with a weight strapped to one foot and the other foot tied to the people I was working with. (When you take an hour on Sunday afternoon to go to the park with your kids and you spend the whole time on the phone putting out fires – you begin to understand what I mean by this.)

One day, our Project Manager (PM) walked into the conference room and plunked down a book. “We are doing Scrum.”, he announced.

We looked up with bleary eyes, half-ignoring him, waiting to be excused so we could go back to our desks and continue our daily grind.

PM said, “I have one of these books for each of you. I’ve highlighted the chapters I want you to read – do it today, because we’re starting this tomorrow.”

Our responses varied from hostility to disinterest to what could best be described as numb capitulation.  (Some of us had lost all of our fight by this time.  Any hope for “greatness” had been worn down by investing countless hours just to squeak by as “okay”.)

I’ll go ahead and admit that I was one of the people who responded with hostility.

We were barely able to get by as it was, and now PM wanted us to read some book and learn new terminology for things that already had perfectly good names?  (I didn’t understand at the time that test cases and user stories were actually different.)

The Agile Manifesto just about made my head explode.  “Responding to change over following a plan?  Now we’re going to build this massive product without a plan?!”

Honestly I thought it was the stupidest thing I’d ever been told to do.

Then…

We followed our PM into the Scrum process, slowly acclimating to the Agile principles and values.

I can’t really say this was something we embraced – it was more of a surrender at first.  Capitulating to the fact that we weren’t in charge, and accepting that we’d probably fail because we stopped working hard and started marching to a whole new tune.

Honestly at times I felt like Fred Flintstone walking into The Royal Order of the Water Buffalo.

flintstone

One day, maybe even just a few weeks into our Agile journey, I looked up and realized that we were on schedule.  We were done at 4pm – ready to go home, and we were killing that extra hour by meeting for a beer or appetizers, talking, laughing, and bonding as a team.

These amazing, smart, funny people I worked with – they were my team now. My friends. We actually had time and bandwidth left over at the end of our work day to unwind and enjoy each other as individuals.

Our project drew attention from the Intuit offices in California as people saw our progress.  They wanted to know what we had done to achieve greatness.

And Agile grew.

Now…

I will never again work on a development project without implementing some form of Agile development.

Yabba.

Dabba.

Doo.

[continue to chapter two]

Talk to Us Today