I was in similar situation and it took months to figure out a workaround. What was working for me: delegate bigger packages, not task by task, but a longer term goal, let the team understand a bigger piece and the goal of the project and let them work and trust them. Sometimes check in the version controlling system how it is going and ask them what is the status (I asked them for weekly status report). If you see a big difference between code and reports go deeper, otherwise let them work. That was what was working for me.
I agree with you on giving the team some autonomy. I think it’s important. I try to do that as much as I can. But I dont think doing weekly status reports will help. Havin junior devs on your team means that they need mentorship, especially when you need to deliver a high-quality codebase to your client.
I’m hoping that I can be more hands-off with time.
Sorry, I missed the point that they are juniors. I think the only thing what could help to introduce one senior developer to that team as local team lead.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.