Code for Concinnity

I’ve been reading about software project management, agile practices and stuffs for several months now, almost becoming the metaphorical PM that’s read 20 books on agile. Came across this post that’s hands down the most true, funniest description about software management I’ve seen.

A man is flying in a hot air balloon and realizes he is lost. He reduces height and spots a man down below. He lowers the balloon further and shouts: “Excuse me, can you tell me where I am?” The man below says: “Yes you’re in a hot air balloon, hovering 30 feet above this field.” “You must be a software developer,” says the balloonist. “I am,” replies the man. “How did you know?” “Well,” says the balloonist, “everything you have told me is technically correct, but it’s of no use to anyone.” The man below says, “You must work in business as a manager.” “I do,” replies the balloonist, “but how did you know?” “Well,” says the man, “you don’t know where you are or where you are going, but you expect me to be able to help. You’re in the same position you were before we met but now it’s my fault.”

There has been a lot of fuss about agile methods — XP, Scrum in this decade. My experience is primarily with fixed-price so I can’t speak for myself the effectiveness of agile methods. On the other hand, what I do feel is how sucks when the client is firing change requests: often trying to get it free.

I recently worked with a client who just refuses to write any detailed specs. When I pressed him, he put up agile to his defense.

Recently read the book Extreme Programming Refactored, which sums up my thoughts pretty well:

In the real world it’s called making your mind up, having a clue. Yet XP wants to stand all this on its head and encourage ever-changing directions and goals.

Yeah, it’s called making your mind up, adults.