I am the team lead of a team with quite a diverse background in both age and knowledge. 2 COBOL developers around 60 years old, 1 business person, one project manager, and 3 Java developers. I am the most experienced Java developer and I also did the architecture design around the product we develop so I also act as architect. Now the problem is that the PM asked me to be team lead and I have very significant problems with the 2 developers that are around 60 years old. Just for comparison I am 38 years old with 18 years experience.
The two senior developers are questioning and competing with me on every possible occasion. Even though we develop Java applications and not COBOL it just happens that we are doing Core transformation so we need their knowledge which technically is not very relevant to what we do. It is very tiring and I really don't like my team lead position at the moment. I feel that at one moment it will just generate an open conflict which I prefer to avoid.
I am considering to go to my PM and directly state that I don't want to be team lead in this situation. What are my options? It should be noted that one of the old COBOL programmers is in my opinion not very well with her head. So I am not sure I can actually reason with her. At the same time they have worked with the other COBOL developer for 30 years and they defend each other on every occasion. So the situation when it comes to reasoning is a bit special.
Meetings very often are dragged in. One of the reasons I became team lead was the PM trying to put more structure and reduce the meetings and let the Java developers drive the project.
The COBOL developers need special attention all the time. They involve themselves into the Java development seeking explanations for everything. Very often they argue about things they don't understand.
Example situation: The COBOL developer finds out a new feature and wants to add it. Then I mark it as good to have and then a discussion happens about who am I to decide if it is good to have or MUST. At the end I find out that the developer has no idea about the Moscow prioritisation. Still the discussion drags on.
Another example: They need something to analyse all the time, while at the same time they are not able to deliver. We can not create smaller tasks for them because they want to be involved in everything.
At least on two occasions I have been the recipient of something similar to "Who am I to decide" or "Why should I decide". I find it actually pretty abusive. At the same time I have created the design of the complete application and I am the reporter of 180 Jira tasks. 180!!!!! for the last 3 months. This is in contrast to them reporting 0 tasks.