Comments on: When Everybody’s Responsibility Becomes Nobody’s Responsibility http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/ Ideas for building efficient developers and software Fri, 12 Mar 2010 12:19:55 +0000 hourly 1 By: Coder Blues http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-2806 Coder Blues Sun, 14 Sep 2008 03:17:40 +0000 http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-2806 Excellent post. I think the best results are when a company can find the right balance between silo and group ownership. To much group mentality and you run into chaos, too much structure and the company slows to a halt. Excellent post. I think the best results are when a company can find the right balance between silo and group ownership. To much group mentality and you run into chaos, too much structure and the company slows to a halt.

]]> By: Anthony http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-2285 Anthony Fri, 16 May 2008 03:37:18 +0000 http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-2285 I will never, ever, ever utilize "agile" or any for thereof. That stuff is so fruity that its not funny. I'd want to smack the first person who came to me and said "who is taking care of SHARED responsibility X?" Going with this logic, why do we even need a corporate structure? A CEO, a Board of Directors, VPs and CIOs and accounts or secretaries... I mean, wasnt the secretary supposed to go out on that sales call in Duluth and wasnt the CEO supposed to order staples for the office? Come on. There is a LOT to be said for structure and its those same people that cry "change is good" that the same types that dont adhere well to "staying the course" and certainly dont take too well to personal responsibility for the actions they took. I.E. if you think I am going to fix your bugs, you're crazy. I'd rather work alone then. =) I will never, ever, ever utilize “agile” or any for thereof. That stuff is so fruity that its not funny. I’d want to smack the first person who came to me and said “who is taking care of SHARED responsibility X?”

Going with this logic, why do we even need a corporate structure? A CEO, a Board of Directors, VPs and CIOs and accounts or secretaries… I mean, wasnt the secretary supposed to go out on that sales call in Duluth and wasnt the CEO supposed to order staples for the office?

Come on. There is a LOT to be said for structure and its those same people that cry “change is good” that the same types that dont adhere well to “staying the course” and certainly dont take too well to personal responsibility for the actions they took.

I.E. if you think I am going to fix your bugs, you’re crazy. I’d rather work alone then. =)

]]> By: Vinayak http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-604 Vinayak Thu, 22 Nov 2007 03:52:04 +0000 http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-604 a commmon issue most nicely brought out... the hippie style can be observed in startups where the number of people involved is less or in small teams. and things work out fine, probably better than the rigid responsibility division.. but as the number of people increases, then usually because of communication problems some of the work will not be done at all or done by 2 or more people.. then begins the blame game :).. a commmon issue most nicely brought out… the hippie style can be observed in startups where the number of people involved is less or in small teams. and things work out fine, probably better than the rigid responsibility division.. but as the number of people increases, then usually because of communication problems some of the work will not be done at all or done by 2 or more people.. then begins the blame game :)..

]]> By: MSDN Blog Postings » "Everyone" Is Not A Valid Owner http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-562 MSDN Blog Postings » "Everyone" Is Not A Valid Owner Wed, 14 Nov 2007 21:48:30 +0000 http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-562 [...] this over on {Codesqueeze}.  He talks about the danger of self-organizing teams.  When people [...] [...] this over on {Codesqueeze}.  He talks about the danger of self-organizing teams.  When people [...]

]]> By: Ryan Cooper http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-451 Ryan Cooper Fri, 02 Nov 2007 13:18:52 +0000 http://www.codesqueeze.com/when-everybodys-responsibility-becomes-nobodys-responsibility/#comment-451 Good post! I've definitely see this issue crop up on agile teams. It seems pretty common when teams first transition to an agile way of working. Thankfully, in most cases it was temporary while team members get used to the extra responsibility that comes with self-organization. Once people learn to ask "who's taking care of (shared responsibility x)?", the confusion often clears up. It's a good example of the agile principles of communication and rapid feedback. :) Good post!

I’ve definitely see this issue crop up on agile teams. It seems pretty common when teams first transition to an agile way of working.

Thankfully, in most cases it was temporary while team members get used to the extra responsibility that comes with self-organization. Once people learn to ask “who’s taking care of (shared responsibility x)?”, the confusion often clears up. It’s a good example of the agile principles of communication and rapid feedback. :)

]]>