Is your first agile project doomed?
People don’t generally get things right the first time. Remember the first time you tried to ride a bike, or the first time you drove a car? Chances are you fell off, or had a fender bender. With this in mind, doesn’t it stand to reason that the first time you try to use some agile methods in your software projects, you’re going to get them wrong?
The problem is that when you fall off your bike, its not a big deal. Screwing up a software project can cost big bucks though. How many chances do you get to figure it out? Do you spend a bunch of money up front to get some agile consultants and training so that you can ensure you’re doing it right? Doesn’t it also depend on everyone buying into the processes and methodologies? If you have some developers who think agile is a bunch of hooey, I would think you’re screwed from the get-go.
I suppose this argument could be applied to anything, but agile in particular seems like a big step and one that requires a lot of discipline to follow procedures and trust the people around you. What do you think, is your first agile project doomed?
jpalermo said,
Wrote on March 9, 2006 @ 11:54 am
Your last paragraph struck a chord with me.
YES, it requires A LOT of discipline.
YES, you have to TRUST the people around you.
It’s easy to not have discipline, and it’s easy to not trust people. I’ve worked in an environment where everyone was concerned about covering their own butts. After a 1 on 1 conversation, they’d ask me to email them our decision. Or if I promised them something, they’d ask for it in an email.
In my current company, a coworker asked if I wanted an email saying what we had just said. Feeling disgusted just for a moment, I recovered and politely said “no”.
Agile development is harder that other types. It requires strict discipline, and it doesn’t come easy. It requires actually solving problems and not hand-waving them.
Agile is just an umbrella for common-sense approaches that have worked for many people. Each team should be self-organizing: That includes deciding what process they will follow. You don’t have to follow a big-bang project template. Discuss with your team one practice at a time to put in place.
Anonymous said,
Wrote on March 9, 2006 @ 12:55 pm
If you’re going to make a huge change to your process, then it’s probably a good idea to have someone on the team for whom it’s not completely new. In XP, this person is designated the “coach”.
Also, be prepared for a dip in productivity as the rest of the team get up to speed.
jpalermo said,
Wrote on March 9, 2006 @ 2:44 pm
I have to agree with Coach.
Apprenticeship is the fastest way to learn, so it’s definitely helpful to have someone who has seen Agile work.
breichelt said,
Wrote on March 9, 2006 @ 3:16 pm
thats the conclusion that I came to as well, the best way would be to have someone who has been on successfull agile projects to learn from, its too bad that that option is the most expensive option as well, as opposed to reading a book/blogs
sahilmalik said,
Wrote on March 9, 2006 @ 3:19 pm
You need a team of developer with either no egos, or very co-operative superstars to make it work. Good luck finding that in the real world.
johnwood said,
Wrote on March 9, 2006 @ 3:39 pm
>>After a 1 on 1 conversation, they’d ask me to email them our decision. Or if I promised them something, they’d ask for it in an email. <<
It’s not always about CYA. Some of us don’t have very good memories so it’s easier to remember what was decided if there was a record. Also you can forward an email on to others who perhaps should have been in on the conversation. You could just write out what was said, but an email from the person tends to carry more weight and have less of a ‘chinese whispers’ feel about it. Just MHO.
jpalermo said,
Wrote on March 9, 2006 @ 5:18 pm
John,
In my case, it was CYA.
jkimble said,
Wrote on March 15, 2006 @ 2:40 pm
BTW, you can apply the same logic to offshoring (and I know a company that has done exactly that 4 times at twice price… and dare I say they are doing it a 5th time…)
I should blog about this… provided I can avoid being sued
Anonymous said,
Wrote on March 15, 2006 @ 3:07 pm
Ben&rsquo;s post&nbsp;made me think about something I&rsquo;ve been meaning to write about.&nbsp;&nbsp;I…
Anonymous said,
Wrote on March 15, 2006 @ 3:07 pm
Ben’s post&nbsp;made me think about something I’ve been meaning to write about.&nbsp;&nbsp;I recently…