World Conflicts
Yesterday
503
Is "From the River to the Sea" So Wrong?
Personal Finance
Yesterday
1113
Thank you AAPL and NVDA
Tech Industry
Yesterday
728
Better long term earning potential: IC or management
India
Yesterday
636
'Hindutva': The Radical Hindu Ideology That Seeks to 'Push Christianity Out of India’
World Conflicts
Yesterday
440
Why I Find Free Palestine Inspiring
So, our PM (which actually is more of a PO than a PM :)) has been assigning a front dev (lets call him Dave) from another squad to some of our squad's work. The reason is that their squad has no more work for them as we approach the end of the sprint (in 2 days). The thing is: - we are currently refactoring the app (which is a MESS, and partly because of Dave) and bringing outside contributors for one or two days will cause more harm to the codebase than benefits - bringing for 1-2 days a dev that has not contributed to the codebase for 1+ year will result in productivity loss (they will most likely need help from seasoned developers of the squad, during which they will not work on their tasks) The squad leader (tech lead) is off for 2 weeks and I am in charge of the tech part of the squad while they are off. I am strongly against the idea of bringing outside contributors for such a short period of time. Particularly since we've been fighting so hard to finally be able to start refactoring the app, and I'm afraid that allowing this thing once (which would have a small impact on the codebase), will result in it becoming normal and happening more and more, which could in the end have a GREAT impact on the codebase and productivity of squad devs. Am I wrong to react that way? Also,I feel like it's a failure of their squad's leader and PM that were unable to plan enough work for their team.
You shouldn’t push back on offers of support from other engineers. Even if justified in some cases, it’s generally perceived as a red flag, non-collaborative, etc. You should gently push back on work being assigned to individual engineers by someone not in an engineering role. If an additional person has been assigned to the team, and you are currently tech lead, then identify the least risky area this person can contribute to, and enthusiastically propose that to the PM instead. Pushing back on this person entirely is unlikely to get the result you want, and could make you be perceived as difficult to work with.
Your logic sounds reasonable.
I think this is more likely a political game where Dave want to see what you gonna do to his old baby and intervene if he thinks it is not right. In your situation, you cannot change much because (1) you dont have authority because u are not official teamlead and (2) you might not have the same visibility as your team lead. Maybe something like this has been discussed way long before. also agree with Atlassian, you should not push back on help offer. You should find least impact work for him and let your teamlead deal with the rest.
I agree on your pushback. I think bringing someone in for a sort time is a bit of a micro optimisation seems really naive. I’m getting echoes of mythical man month.