I have always been a fan of Cricket and Rahul Dravid. It’s not every day that you find a role model like him. And once you understand the things he has done for the team, it’s very difficult not be in the league of his admirers. He is that one man who put team’s interests ahead of himself. Right from starting an innings to coming 7 down, he has batted at various positions; He has kept wickets too, so as to maintain the team balance. These things are not easy. Making someone comfortable not caring about yourself requires a strong determination, great deal of flexibility and self-sacrifice, to some extent.
Software development is a kind of a job, which gets monotonous after some time. Unless you experiment new stuff, it gets really boring. Trying out different technologies is one part. The other part is to try out different team strategies. Somehow, I caught this bug of trying out how Dravidism works in a typical software team.
I would like to share my experience about what happened in my team, in the past 4 months.
Background:
The story begins in the month of February, when our team starts on a new project. There was a lot of work, and I do a decent job, which brings me some recognition. This phase goes on till May.
Start of Experiment:
By the month of June, I was looking for some change when this experiment came to my mind.I took a conscious decision to follow Rahul Dravid’s principles at work.
Easy principles:
1. Always put team ahead of your interests. (Take tasks that others are not willing to, but are essential for team’s success)
2. Be highly flexible, change tasks when required for the team, though it has a significantly bad personal impact
Results:
Horrific is the one word to describe the results. The entire feat achieved in the first two months became useless.
Conclusion:
Its as if I have misjudged/misinterpreted Dravid’s principles or its not a good idea to have it Software companies.
Praveen s
praveen0989.wordpress.com 