What happens when an Agile team falls flat on their face?

Much has been written about the benefits of doing Agile software development.  I won’t spew the various catch phrases and mantra’s that you’ll find across the web on agile, sufficient to say it has proven to work well for many people.  With that said, there is a great number of developers who haven’t tried agile software development.  Some because they just don’t buy into it, others because their organizations won’t let them, and others because they don’t know what it is.  With all that’s been written about the benefits of Agile I think we often times forget to tell people that it isn’t the easiest thing in the world to do.  While thats understandable given the fact that many people are trying to bring people to agile, not scare them away, I think we do run the risk of giving people a false sense of what is involved with doing agile development.  It can be hard, it can be frustrating, and it can be painful.

This past week was one of those painful times.  At the beginning of the week we went through our planning session and identified a single story that we were going to focus on for the week.  While the story was quite large it wasn’t something that we didn’t think we could handle.  As the week progressed we all felt we were making decent progress (we weren’t) and we all felt that we’d be able to meet our commitments (we didn’t).  By Thursday afternoon many of us started to realize that we were in trouble.  We’d have to put together a Herculean effort in order to finish everything that was left by Friday afternoon.  As you might have guessed we didn’t make it, in fact we didn’t even come close.  It sucked.  To make matters worse we didn’t cut our loses on Friday afternoon.  We all decided that we wanted to try and put some time in over the weekend to complete the story.  After-all we had committed to finishing the story and we’ve done a pretty good job of meeting our commitments over the last several months.  While we made an attempt it wasn’t nearly enough.  It sucked…big time!  To make matters worse today we broke down the remaining tasks required to complete the story and realized we had enough remaining work to fill up the entire next week.  SH*T!  How depressing.

When doing Agile software development your going to fall on your face from time to time, and it’s going to be painful.  The Green bars might make you feel a little bit better but its still going to hurt.  Lucky for you you’ll get to do it all over again “next week”. 

# re: What happens when an Agile team falls flat on their face?

Tuesday, June 27, 2006 4:07 AM by Howard van Rooijen    
Were you using a burndown chart? Didn't this indicate something was going wrong early on?

# re: What happens when an Agile team falls flat on their face?

Tuesday, June 27, 2006 9:01 AM by Steve    
We don't use a burndown chart. We do 1 week iterations so I don't think it would have helped. While it stunk to miss our committments, we've identified a lot of the problems that we think led to it and are doing what we can to make sure it doesn't happen again. Every once in a while it's good to be humbled, right? :)

# re: What happens when an Agile team falls flat on their face?

Tuesday, June 27, 2006 9:03 AM by Robert Hurlbut    
That's no fun! But, it sounds like the team learned something from it in terms of refining the estimates. It's all a learning experience, I think.

# re: What happens when an Agile team falls flat on their face?

Tuesday, June 27, 2006 9:21 AM by Steve    
It's definitely a learning experience. The great thing about agile is that we identified a lot of things to look out for going forward. Instead of waiting a couple weeks or months to identify the problems we waited a week, and promptly took steps to correct them.

# re: What happens when an Agile team falls flat on their face?

Wednesday, June 28, 2006 3:52 AM by Howard van Rooijen    
Even with a 1 week iteration, I think it would help - I know it's the focal point of our project space - a really powerful visual cue.

If you have a 5 man team and you estimate your tasks on the assumption of a 5 hour man day (as we do, if you factor in stand-up, group design sessions, other distractions, then we estimate 5 hours of actual coding) then each week you have 100 hours to burn down.

If you're running your project using Scrum and are using Team Foundation Server - you can always use Scrum for Team System as your methodology and you get all those charts for free (and it's good to stick the burndown as your active desktop background)

Another visual cue we've used in the past is to have all the tasks on a whiteboard and when they are done cross through them with a green pen - by wednesday the board should be half green or you have a problem...

# re: What happens when an Agile team falls flat on their face?

Wednesday, June 28, 2006 9:10 AM by Steve    
I should have mentioned in my previous response that we do have a giant whiteboard with all the tasks broken down on it. As we start tasks we "brown" them to indicate they've been started and when they're complete we "green" them. It gives us a very good visual indicator of where we are and what we have left. The whiteboard is very large and sits right next to our desks so there's no way of ignoring it.

Unfortunetly it didn't give us enough last week because it appeared we were well on our way. It turned out that many of the stories that had been started ("browned") were a lot less far along then some of us realized. We've taken some action to ensure that doesn't happen again. I'll try to write more about our process in a seperate post since it might be good to give a little more context to how we do things and were we found things went wront last week.

# re: What happens when an Agile team falls flat on their face?

Wednesday, June 28, 2006 9:12 AM by Aaron Feng    
I believe everything will come out in the wash over the long haul. It does feel painful, but I'm sure some weeks more stories got done than estimated. However, no one writes about that ;)

# re: What happens when an Agile team falls flat on their face?

Wednesday, June 28, 2006 1:34 PM by Sam Gentile    
Good points Howard but we do have a huge Information Radiator in our large board with all the tasks broken down. It usually doesn't fail us (we've hit the last 11 out of 12 one-week Iterations) but as Steve said too many stories were browned and we assumed they were much further along than we thought. You may also want to see my blog post as we figured out what was wrong and promptly fixed it.

# re: What happens when an Agile team falls flat on their face?

Saturday, July 01, 2006 1:13 AM by Bob Leano    
Eating Humple Pie is always good for everyone who has succeeded 11 out of 12 times. That shows you that (a) you are human, (b) you have to be humble.

# re: What happens when an Agile team falls flat on their face?

Saturday, July 01, 2006 8:18 AM by Steve    
Although being humbled stinks, I agree that it often times is very good for an individual and team.

# re: What happens when an Agile team falls flat on their face?

Saturday, July 01, 2006 8:26 PM by Jason Yip    
I recently experienced a similar crunch (though we still ended up pulling through). The lesson I took from that is that I want to be even more adamant about keeping stories smaller.

"While the story was quite large it wasn’t something that we didn’t think we could handle."

That's very similar to what we were thinking and I'd submit it's a common theme for these failures.

# re: What happens when an Agile team falls flat on their face?

Saturday, July 01, 2006 9:06 PM by Steve    
Jason, I agree 100%. Underestimating the size of a story and/or doing a poor job of breaking down your stories into tasks is one of the best ways to get yourself into trouble.

# re: What happens when an Agile team falls flat on their face?

Monday, July 03, 2006 7:06 PM by Sam Gentile    
Manual trackback

# re: What happens when an Agile team falls flat on their face?

Monday, July 03, 2006 7:09 PM by Sam Gentile    
Agreed, Bob and Jason. It was real good to get humbled to a) show we're human and b) humbled, but the team also benefited from correcting the mistakes and bouncing back with something like 55 tasks done last week and finishing everyting. Should be interesting this week though with a "three day Iteration" -))

Enough of these addition questions Steve, my brain hurts-)

Post a Comment

 
 
Prove you're not a spammer: 
9 + 8 =