3 ms·
That is opposite of personal responsibility. There is very little space for making individual decisions and being responsible for them. I see it as a continuum
by mindcrime 10y ago
That is opposite of personal responsibility. There is very little space for making individual decisions and being responsible for them.
I see it as a continuum, with a lot of room between "absolute autonomy and no responsibility to the team" and "slave-like adherence to someone else's position". In between there is a place where you take a position and have to sell the rest of your team on it and then once everybody buys in, the whole team does own the decision.
But I think here we're talking about design decisions, architecture and what-not. What I mean earlier was more about responsibility for actually delivering the things you say you're going to deliver. So if, on your self-organizing team, you volunteer to take on the task "Write Fromgizzit-A I/O module" then there is indeed responsibility around actually delivering the code in question, as opposed to coming in every day, spending all day reading HN, and not delivering anything.
- watwut 10y agoWhole team owns decision is precisely lack of accoutability. They might have agreed, they might have choice between pretending to agree and circularly discussing the same detail for hours, they might have been afraid to disagree for political reasons. They might not consider it important. They might have been introverted geeks uncomfortable with heated discussions. If you and code reviewer ends up not agreeing on something, then you are not responsible for delivering it. But more importantly, agile tasks are max half day long, so your inactivity would be very fast recognizable and responsibility is limited by that. You are not responsible for communicating issues nor recognizing them, you are not responsible for overall deadline nor anything like that. The only thing you are responsible for is not slacking for half a day, everything else is taken for by other people.