This week's book giveaway is in the OCMJEA forum. We're giving away four copies of OCM Java EE 6 Enterprise Architect Exam Guide and have Paul Allen & Joseph Bambara on-line! See this thread for details.
I have a problem. My role is Project Lead. My present project team size is 2 including me. At onsite we have one more resource. My project is complex, but stable. It has been built long ago and we are doing maintenance. The existing set up is that, no matter whether we do something or we do not do anything and put some stupid text in status mail, my onsite coordinator is least worried. He simply puts another mail for the tasks for the day. The project domain is big and pretty complex, the technology is Flex, JSON, Core Java and web services. Flex is being used only by us and in our account there is no other project which implements it. We do not have any enhancements. Only some bugs, which are rare and mostly we have to monitor issues logged in production logs with ERROR severity. Again, whether our analysis is right or wrong, whether we fix the bugs or not, people are least bothered. All this is between offshore and onsite and the management does not know that this how it runs. For them, going by metrics, the project has rarely anything to do, which at the higher level is true. But if there is a bug to fix or to analysis, lots of time needs to be spent regardless of whether someone bothers about it or not.
Now the issue is, i have been assigned as lead to another project comprising of 2 junior resources and one senior at onsite. I am not able to do any justice to that role. I dont know the project, nor the functionality and I have not worked on that project before. My management says, spending some time daily 20-30 mins asking that team to explain what they have done will ramp me up and I would know at 70-80%, 6-7 months down the line. I dont understand how that is possible. Not understanding anything they do, and even though I would have code walkthrough for 30 mins daily from both the resources, i still cannot understand how I can come to a level, where I can handle to 70% efficiency. Is that how it works elsewhere also. To my knowledge working on the project daily, on its issues at ground level only will give me a grip on the project. What can code walkthrough do. I cannot sit with them daily and spend all my day with them. i have my own project and a fresher, new to the project. Regardless of the importance or result, I have to work in my project too. Firstly is this the right setup at all? If I were directly assigned to the other project and asked to oversee my present project, I wouldnt have had any issues. I know what goes on in my project and having worked on it already, I will be at a good place. But this setup, I am just clueless and I am looking as a dumb fellow to everyone.. Your thoughts please.
There is no issue with the project execution. The existing team is carrying on their business. My issue is that I have been assigned as a lead to their project in which I had never worked earlier and neither Am I working now. How will I lead them, if I dont know much about it..My manager says I dont have to do anything at the ground level, just spent 20-30 mins each day on code walkthroughs and on what they do and in an year I will be atleast 70% proficient in their project...I cannot understand how can that be...Doing and knowing at superficial level are entirely different..Or is it that all leads are supposed to be equipped this way..Am I on the wrong impression.
Its most common Ram...The work they allocate is the need based.Lead may not be proficient pertaining to the applications.How can one expect to be proficeint with someboy elses's application within a short time.But the experience you bring in for them during code reviews,walth-thrus etc will help them to a great extent..Who knows you may catch a critical bug in the program and this they can't achieve with a less experienced guy..Don't worry..Read the system design docs(this you have to do apart from your daily work..thats inevitable) and give the best you can.
All the best.