« first day (4 days earlier)      last day (21 days later) » 

bobo2000
bobo2000
10:52
@BloodGain all I did was try to make the environment more transparent which is a core agile principle, if I/that was the cause of the tech lead resignation it is clearly because he would rather things be confusing and hidden. Senior management in private have been complaining that devs are not reliable.
 
1 hour later…
bobo2000
bobo2000
12:13
@BloodGain Yes, I agree, my job is to facilitate the process and help people to communicate. The idea is for everyone to communicate, not only me. Tech lead was NOT communicating well, once I started putting processes in to encourage that, he resigns. As I said before, it is a 2 way street, and from experience the people who avoid communicating are just not normally that good at their jobs and would prefer to hide instead of being transparent. I doubt I was the cause of his resignation tbh.
 
10 hours later…
BloodGain
BloodGain
22:32
@bobo2000 @bobo2000 So he was good enough to become a tech lead, but clearly "not that good" at his job. How likely do you really think that is? Could he have been a bit of curmudgeon that had a poor attitude toward management? Sure, I've met lots of developers, including leads, who are just plain misanthropes. They can really test your communication skills...
@bobo2000 But some of them were really good at what they did, so you learn to work around their attitude. I've met almost none you can't get on board eventually.
Senior management at a lot of places complains about the developers. Smart PMs know to ignore that, because they are almost always wrong.
To be fair, I didn't say you were the cause of his resignation. It sounds like your company has a toxic environment that needs fixing. You may have been a factor, but at worst you're a symptom of the system that was already in place. Try to be a cure instead. Maybe you can turn them around and b…

« first day (4 days earlier)      last day (21 days later) »