This post is dedicated to the supposed "Superman" of a software project. In any software project, you will find one or two blokes who have this habit of taking on the responsibility of the entire project on their heads, even when there is no need for such drastic actions.
Over the years I have analysed some traits of these "Supermen":
1. The basic habit of "I'll do all" comes from the fact that they wish to become the "hero" of the project.
2. In their hearts they are so insecure about their position in the project/organisation, that they start to involve themselves in all unnecessary tasks, be it trivial or complex.
3. These guys are naturally poor at time management. You will find them slogging till late hours just to prove to management that they are the most "hard working" blokes around. (And also "secure" their insecurity mentioned in point no. 2 above).
4. Naturally, their output in terms of quality is pathetic, since only a "real Superman" can work 10-11 hours a day and produce a decent quality.
5. At the end of the year (more precisely after the appraisal cycle), they will always complain to the management that they were not rated appropriately.
Well I understood long ago, that in this trade, you need to work smart and not slog. And also the fact that pick up only that much work that is possible for one to do within a decent time with a decent quality in it.
God bless the "Supermen"!!!!
Subscribe to:
Post Comments (Atom)
तुम आओ तो सही...
This blog of mine, would be saying to me the same thing... एक वादा करो अब हमसे ना बिछड़ोगे कभी, नाज़ हम सारे उठा लेंगे, तुम आओ तो सही। An...
So true! I saw traits of that in me earlier, I think now I can't be bothered to work at all, superly or otherwise!! :P
ReplyDeleteYup! same was the case with me. After this "realization" it is bliss at work!
ReplyDeleteSorry frinds i do not agree here , not sure how large / complicated / poorly managed those projects where where you saw someone doing poor timemanagement and eventually working 10 12 hours a day . But generally what i see and what i also belive that there should be one or two persons who can take the projct through , it is just like someone in a ODI playing through teh 50 overs and ending up getting a handsome score for the team . Similarly even in an Project you need to have someone who takes it through , we also need to accept the fact that all fingers are not alike and we end up using a couple of fingers more than the other . Every project should have a Superman and a Spiderman :-)
ReplyDeletehmm... but why should it be like that? How is time management not an issue if others in the project are not up to the mark? The scenario you are depicting is a classic one always seen in a waterfall model of project execution! On the contrary, management should never decide on time estimates, it is the team that should decide and it is up to the team to decide if the shipment is OK to deliver. Perhaps you should take a dive at this: http://agilemanifesto.org/principles.html
ReplyDeleteThis is very well put into words .... i totally agree
ReplyDeleteLooks like we are going to enlighten ourselves with the project management skills :-) . Anyways.. even when working in Agile mode the success of an iteration will always depend on someone taking charge of situation and making sure that the stubs and harnesses of the other modules are ready in time so that the workable part is properly tested and the iteration can move towards the new phase ( This is my view and i am not and Agile Guru by any means :-) ).
ReplyDeleteAny i agree management should never decide on time estimates and it should be left to the engineers . But again Business is not driven by engineers it is drivern by the customer and management wants to keep the customer happy at all times :-)
I am sure you will also understand someday .. i had my lessons and transformation a couple of months back when the business was low and there was a need to cut donw 3% of workforce and now there is work and i see the importance of delivering the things in impossible timelines...
@Soumen, it seems you have moved to the "other side" of software development, wherein you wish to push the "sale" to the customer, than focus on the art of software writing. I'm afraid, but you do not have a correct view of Agile way of working. I've seen great success in this methodology and there were no "Supermen" in those projects. What you may have practiced was probably Waterfall within each iteration, which is even more dangerous. I wish you best of my luck in "delivering" the "right thing" to your customer in impossible time lines...you will "deliver something" alright, but may the customer and your team be happy at the end of it!
ReplyDeleteYou will also learn the trick of the trade and will move to the DARK Side for sure... my best wishes are with you as well.
ReplyDeleteThanks! but I've seen it all in my short stint in this industry. I've no wish, desire or aspiration to move to "that side" of the industry. I would rather prefer to be a "small fish" in a "big pond". I pray to god, that I am never forced by circumstances to take up such a role.
ReplyDelete