Category Archives: Nothing official about it

Stretched beyond limits

With 2 development projects, my plates are more than full. One of that project is a high visible one – progress report goes up to top executives at offshore and at client’s place. For the past 3 – 4 days, I have worked almost 20 hrs/day. There is no appreciation of the hard work, there are only issues to resolve. I have been squeezing my little brain to resolve people issues, planning mistakes and putting up with management pitfalls. Recently I read a quote, to plough a field one needs two strong oxen; not 1000 chickens. When these projects started, I was asked to induct project interns and whoever was available at that time. I persisted to get at least one experienced candidate. Now with all these issues the management is realizing that we don’t have an oxen. Little late, but nevertheless not too late. There are remedial actions taking place, but running against tight schedule and implementing a transition is no easy job. I have been doing well so far (I guess). I hope to see through this tough time and deliver this project meeting expectations.

Development project vs. Production support

One of the tasks recently added to my plate is managing a J2EE development project. Ever since I joined back at offshore, I have been managing production support projects. In a typical production support project, the team’s main task is to adhere to the agreed SLA (service level agreement) in keeping the system alive and well for the end-users. Normally there is no project plan. The team works on an ad-hoc basis. If the system is a new one, there will be more number of tickets to work on and if it is a stable system then the tickets are distributed over the available time. The life time of a production support team is normally a longer one.

Whereas it is an entirely different scenario in a development project. The project starts with a document of understanding and then it goes into project plan, requirements gathering, design and the rest of software development process. If the pressure of production support is one, that of development project is another. In a development project, one is running against a deadline. One has to track the hours/progress of oneself and the resources effectively. There is always a delivery to be made. It is challenging to keep the users satisfied, team members motivated and the management at a distance. So far, so good – we are on track. Hopefully it will be so till the end.

New development project at offshore

In my portfolio of applications, there is a new development project that has come forth. It is around 2000 man-hours project spanning 4 months. This is the first development project that I will be involved at offshore. With the addition of this project, the number of resources in my team has increased to 10. That is kind of cool, considering the fact that last year this time I was running between poles to get into a project.

Reason for silence

It has been long time, since I blogged. For the past 25 days or so, it has been extremely tight at office. I was here every day working for more than 12 hrs a day. It was all because of poor planning from client side and my team at offshore was pulled into the shit by ‘please-the-client-at-all-cost’ managers. Man, it was a marathon activities tiring all of us. But with support from many quarters, we were able to finish the tasks and get out of the shit-load. One thing I learnt: if you are good, you will get lots of work. If you are really good, you will get out of them successfully.

Pain is mine; Praise is thine

It all started out when one constipated monkey called onsite manager wanted to get into good books with client. Without consulting any of us, he commited to the client that we will finish a certain task. He explained to us as if the whole task will take a day to complete. But the devil is in detail. It took three days to develop and three of us were staying through the weekend to complete it. When I informed the onsite manager, he cooly replied that those planing should be dealt with the client manager! Amazingly idiotic, but true. I wonder how these people get into managerial positions. They commit saying such-and-such task could be completed within such-and-such time, without knowing a bit about the work involved. They all think if we increase the resources, it should be fine. Try impregnating a woman with nine men to get a baby in one month!

In addition, I got to put-up with managerial madness at offshore. I have one guy who repeats everything twice. Everything he says, he says twice. When it happens to others it is comedy, when happening to me it is a real tragedy. He will send out an e-mail and come to you saying, “I have sent you a mail. Check it out”. Whenever he does it, he gets into my nerves.

Finish the task. Suddenly there is a crowd to pick up the glory. You would wonder, where the hell were these people when you were boiling and toiling.

Organizing a training

Our client is using Vantive, a CRM tool which is in its dying ages, for tracking their problem tickets. As it is in its last phase, client decided to migrate to Remedy, another CRM tool. The client manager felt that Remedy is much more complex and insisted that we undergo training. And the managers wanted to catch a big fish with the smallest fish. Well in my case it turned out to be not even the smallest fish was offered. For the past two months, I have been running on all options to get my resources trained in Remedy. Every time there was some obstacle. But surprisingly I got help from unknown quarters. Finally, we had a Remedy training arranged for this weekend. The instructor was good and the class went very interactive. All the resources were very much involved. I was thrilled to see the fruit of my efforts. Of course, I still need to get the project to the offshore. But this itself is satisfying. I learnt couple of lessons during this period:

  • You already have a no. Make it an yes:This is not always easy and possible. But give a try. I learnt this from a Flemish friend of mine. During this period, most of the things I wanted to do had a NO as an answer. Either I had to find a workaround or cajole them to say yes.
  • Be persistent: As a true Taurean, I persisted. Sometimes I had to bend and other times bend others, but bottom line was to get the work done. Keeping the spirit high for two months was tough. In between other official happenings put me down. Sometimes how the team members behaved hurt me. But I kept my beat.
  • Get an authority behind you: My immediate boss was supportive of the efforts that I was taking. Having him behind me helped me to kick some asses and be bold. There were times when I was feeling pretty low, he would come along and encourage me. It helped.

Being the center of attraction

Every month, on the last Wednesday, we have a project-get-together to welcome new comers into the project and to celebrate, in a small way, birthdays and other special days of project members. Every person has to go in the front of every one and say a word or two. What I realized is that I cannot stand being the focus, even for few minutes. I like to stand out in a crowd, nut having the crowd focus on me is a big No! Call me crazy, but that is me. I sneak out in such situations, as I did today.

Managing maintenance projects

There is a distinct difference between managing a development project and a maintenance project. In a development project, there is a deadline to meet, finite number of tasks and sub-task, for each of which one could track progress. But in a maintenance project, that is not the case. One never know in advance, how many problem tickets will be assigned. This leads to chaotic working hours. Added to it, if this is an offshore project, it requires night shift to support people in the US. It requires a good understanding of business process that is already implemented. Debugging technique is a prime skill. As someone is looking into a mess created by someone else, the resources can fall out of interest quickly. All this means, keeping the team motivated is a challenge of its own kind.

Nevertheless, I guess, I have been doing a good job. I am pretty satisfied with whatever I have done so far.

You too Brutus!

In my current project, I am at the offshore managing few critical applications for a US client. There are few Indians working for the client as well, with whom I have to interact time to time. What I have found is that, it is easy to deal with Americans or for that matter anyone other than these Indians (there are one or two exceptions though). These people of our own blood make our life so difficult. These non-Indians out there are ready to help or offer a piece of advice. However, the Indians out there are so tough and make everything an issue. And on top of it, they paint a black image of us. Once one of my resource failed to get to the root cause of a problem. He has been a good resource, but failed in one. When the client manager and the leads from offshore discussed about that, an Indian in the client place generalized and said that Indians are only ready to do what has been asked to do and they cannot think further. Man! if he was anywhere near me, I could have given him a slap. That was so a wrong message. When I explained the diligence shown by the team member in earlier instances, the client manager agreed that this was an isolated issue and dismissed the poisoned opinion. I deal with another one of such a moron. He has been in this application from the requirement stage. So he knows the system so damn well. Obviously, having taken the maintenance of the system just 3 months back, I am not well versed with the entire application as like him. I take so much effort to understand the application and to deliver the modifications after much testing. But invariably, once in a while I fail to get a whole picture. He waits until I fail and then boom, he will shoot out a mail to my boss that I am not good enough. The client manager so many times appreciated me for handling such critical applications without much of escalations, but getting a good name from this guy has been next to impossible.I say often (to myself), Brutus! get to hell.

Lessons learnt

It has been only a short period since I have been a manager – less than six months. But this period has been remarkably eventful. Dealing with people, both subordinates and bosses, is much different from dealing with PCs and programming. Even in that, boss’ needs are different from subordinates and I need to often find a balance. I don’t know how many times I failed, but in general I have a satisfied feeling. These are some of the lessons that I learnt in this period. One day I am planning to write an article on this, but for now, this is just in the blog.

Ask right questions
Soon after I took over and even now in the day to day affairs, lot of time goes in finding facts. Depending on the comfort level with whom I interact, I go with an assumption that they will be honest. But I understood, even then I need to ask the right questions to unearth facts. If not, I could be discussing for hours but not getting the fact.

Don’t take everything your subordinate says into heart
While I was busy fighting for the team and taking every step to build it, few of the resources spread tarnishing rumors of me. Well, I was disappointed and depressed when I heard them. But then, I kept the direction and continued what I was doing. It wasn’t easy, but I persisted. Thank God! I persisted. I see a slow but definite change in their attitude.

Make a balance
A manager’s expectation is very different from that of the subordinate. I have to make a delicate balance between both. If I side with managers to create profit, the measures hurt motivation of the resources. However, I need to make sure, enough profit is made as well. If I tax resources by way of getting-most-out-of-less policy, then subordinates become disappointed. Some decisions might be risky too.

Be part of the solution
This one thing I learnt long back. People don’t want to hear of the problem, whether it is your boss or subordinate. Strive to get to the solution. Think creatively. Brainstorm! Do whatever. But find a solution. Sometimes, I have very little time, probably few minutes. I have thought through while walking to manager’s cabin. It may be difficult, but once you train yourself then it becomes part of yourself.