Developers holding each other accountable as professionals.

The role is Developers, plural, for a reason. They share a joint accountability for their commitments and so if things go amiss there can be no shifting of blame or finger-pointing.

Holding each other accountable also encourages mutual respect and collaborative focus.

Hi Avinash, I hope my answer will still be of use to you.

I would suggest to look into RACI matrix concept - to understand what is "accountability" and what are the differences between "accountability" and "responsibility".

Further, I would suggest to think about how the team can ensure their accountability "inside-out" - meaning if the team is accountable, how the team can transfer this mindset of accountability to the rest of the organization and  "outside-in" - meaning how the organization can support accountability to the team from outside the team.



Hope my comment helps!

Hello,

 

I'm at an organization that the developers managers are very hands off.

They don't look or track if the dev is getting any work done on the dev team. This falls on the dev team to bring up devs that aren't getting work done to that persons manager.

We were work remote first and so the dynamic is a little tricky. For 6 weeks now I have 1 dev who hasn't completed a project. I don't think he'll get another one done for another 2 weeks. Every time it's brought up he sometimes will own up to it "Oh sorry yeah I got distracted and then just didn't start my work and by the time I started it it was too late to have anything done this sprint." 

What do I do with that? Should I talk to his manager? The scrum guide seems to be very anti that- but for background this dev has a history of this.