Director of Engineering @FidelHQ. Prev @talkdesk @addcode_io, @thetrainline and @farfetch. Bass player, Aikido Black Belt, Crossfit athlete and motorbike lover.
@johncutlefish Context matters. Keeping reports (team size) 6-8 is a sweet spot. Too many reports/teams hinder one's ability to grow reports. If over 8/2 teams, consider growing junior team members by proxy - using more senior reports. Play infinite games and work on clever succession planning.
@allenholub Wholeheartedly agree that ideally there would be no need for anything but a team of makers to decide on what the team needs and customers to steer the product needs.
However, when things go south… that’s a different story. ultimately, those with skin in the game take action.
@allenholub Allen, I respect you and don’t want to go in circles on 2 different threads.
Agreed that one should not be judged from a single example, but then again, HR won’t be close enough to the team to determine the best way of handling the situation.
@allenholub I agree everybody likes to be acknowledged and liked. But not everyone values their work and professionalism the same way.
I have seen people slack or try too little and just lay low in hopes no one will notice.
@allenholub Got it, and it might work out some times.
But it could also happen that Jim is quite comfortable with underperforming and the rest of the team is unhappy with what’s going on.
Probably this would make the rest of the team leave the company, not Jim.
@allenholub the person can simply be a casting mistake, is it the team’s job to carry that person’s weight?
They discuss that in the retro and agree that Jim has been slowing down the team for 1 year and refuses to collaborate. What happens then?
@allenholub Who are the powerful and who are powerless?
Is it possible for a team or an individual to underperform on a agile setup? If so, who should start the difficult conversations?
Agreed. And I don’t think it’s necessarily a choice. Both are part of the role, and leaning more towards one side than the other, without appropriate org support, will lead to problems later on.
@allenholub I said winging because it’s unplanned/unprepared. Obviously it surfaces from something such as feedback.
If we also remove the sprint constraint to become even more agile, we are left with defining work based of every valuable feedback that surfaces. Basically, winging work.