« first day (1 day earlier)    last day (24 days later) » 

Stinkfoot
Stinkfoot
09:06
@bobo2000 I actually told FYI senior management that I was concerned that he was and we may need multiple tech leads to distribute the load That was very bad mistake. Bringing in others before you have figured out what the real problem is - Sparrow and BloodGain have given you some very good insights on that - will brand you as an enemy to the tech-lead, and probably everyone else on the team. You need to understand that you are a new-comer and an outsider.
@bobo2000 -(cont) Your title alone does not guarantee you respect and obedience with experienced developers. You need to prove yourself to your team by showing that you have sufficient technical knowledge and grasp of technical problems to be able to intelligently manage them. Otherwise, you will be viewed as a pest and adversary-tool of a disinterested management who considers developers a commodity rather than valuable and unique assets. If you fail to do so, disaster awaits you.
@bobo2000 A PM who takes charge of a development team without proving their bona-fides and manages developers with brute force, has as much chance of success as someone who walks into a lions' den with nothing but a "Lion Tamer" badge. (And if that's not the case, you have a talentless group of developers.) The Tech Lead is sending you signals: You ignore/misinterpret them at your own risk.
@PhilM o me, it is obvious that the lead lost status/authority from before the OP got there How so? Because he doesn't take kindly to an outsider with relatively little technical knowledge pushing him around because he has boxes to check on his charts and schedules? The Tech Lead is probably extremely knowledgeable and may be doing difficult work that must be done alone. He is probably also providing valuable knowledges and insights to the others.
@PhilM - You seem to have a very poor grasp of how development teams work 'in real time'. I'm glad I don't work with you.
bobo2000
bobo2000
10:14
@Stinkfoot It takes more than in depth technical knowledge to deliver a project; organisational skills, team work and strong communication is equally important. This is why PMs are hired to begin with, the team are now finally communicating a lot better are things are more organised after I somewhat streamlined the process working with senior management.
bobo2000
bobo2000
10:40
@Stinkfoot Phil has a point, the problem I have seen time and time again with devs is where they are dismissive towards softer skills and become arrogant from feeling that all that is needed to deliver a project are technical skills. Beyond tech, many struggle working as a team which leads to delays, over budget projects without someone guiding and putting pressure on them to get it delivered as a team.
 
2 hours later…
Stinkfoot
Stinkfoot
12:34
@bobo2000 more than in depth technical knowledge to deliver a project... Understood. Nor did I indicate anywhere that such is not the case. Neither did @Sparrow or @bloodgain . So I really don't understand your comments at all. Perhaps that is part of your problem. You are projecting some of your own notions onto the tech-lead, and placing too much value on your own particular skills, while minimizing others'.
@bobo2000 Phil has a point - Since it seems clear from your question that you are by no means familiar with how the tech lead works and how he contributes to the team on a long term basis, I don't see how Phil can possibly claim that, nor how you can think he does have a point.
@bobo2000 - Also note @berry120 's excellent comments. You are not on the path to success here, IMO. I have worked under several PM's - those who take your approach end up being snickered at and ineffectual, unless you are unfortunate enough to have really bad management above you that is willing to purge their tech staff in order for you to establish your power. In that case It's up to you to decide if you want to be "small fish in a big pond" or "a big fish in a small pond"....
 
3 hours later…
bobo2000
bobo2000
16:12
@Stinkfoot Turns out tech lead resigned last week. Found out today, so there has been deeper issues from before I joined the company :)
 
2 hours later…
BloodGain
BloodGain
18:37
@bobo2000 Yeah, I imagine those "deeper issues" came from management, and you're just the latest hammer they've hired to beat the team over the head with. He probably decided it was time to get out of that toxic environment (of which you are only a symptom, not a cause). Good for him. Maybe he'll find somewhere he can be successful.
@bobo2000 You seem to be of the impression that most of us are replying to your question and comments as some sort of attack. On the contrary, we're trying to help you address the things you can change in this situation, namely _your_ attitude, perspective, and …
 
4 hours later…
Stinkfoot
Stinkfoot
22:49
@BloodGain - You beat me to it. :)
@bobo2000 - So: You came in one month ago, and didn't get on well with the tech lead, because although you were the new-comer, you opted to start pushing him around. A few weeks later, the tech lead resigns. Sounds to me like your entry was the cause of his resignation, or at least "the last straw". (What management says is IRRELEVANT - management lies all the time for 'political' reasons.) Congratulations - you've bagged your first scalp. I predict there will be more to come.
Stinkfoot
Stinkfoot
23:16
@bobo2000 - I see on the other chat that you had a 'mending fences' meeting with the tech lead. Probably "too little, too late". You lost his trust through your initial blunders - coming back later trying fix things a bit isn't necessarily enough. My guess is that after a week of your antics, he started looking for another job. As soon as he found one, he resigned. Keep reading the answers from @berry120 and @TheSnarkKnight over and over until they sink in very well. Good Luck...

« first day (1 day earlier)    last day (24 days later) »