be careful. self-managing team is different with self-organizing team. the latter should always be the case. the former, depends on the situation. 
 
may help: http://www.estherderby.com/2010/11/how-much-self-management-is-right-for-a-team.html

i've been hearing stuff about not using the term "self-managing team". personally, i don't see any difference except that "self-managing teams" are usually terms you try to avoid so that existing PMs won't feel threatened about losing their jobs. :) wdyt?

the article explains it better :-) has nothing to do with threats to PMs

@none don't get me wrong here. i'm in no way implying that scrum is the holy grail. :) i'm just saying that the daily stand-ups are effective in fostering communication. in our team, we practice agile but not any specific flavor.

scrum is a lousy fit if you don't even know how to practice it properly.. like anything else in this world :-P 
 
@joed so what is agile for you if you don't even attempt to stick to flavor? yes, that is a trick question :-P

@none we adhere to these http://agilemanifesto.org/

'Sticking' to a flavor does not sound like 'Individuals and interactions over processes and tools'.

@none our administrator opted to delete your previous comment due to the vulgar use of language 
 
we adhere because it works for us. we experiment and continue to improve. we aim to build great software in the fastest and most efficient way possible. we don't surround ourselves with sticking to a flavor. :) 
 
this might enlighten our POV more  
https://www.readability.com/read?url=http://blog.versionone.com/blog/the-agile-development-blog/lean-or-kanban-or-agile

Here is the comment referred to by the blog author, with the last word replaced. 
 
"i could claim that i'm favoring individuals and interactions over processes and tools, and all the other stuff in that website, for all the world to see. how do you measure that? how do you measure agility? that's like reading the bible, and saying i believe in what i've read, i'm already a christian. always, there will be frameworks and processes around anything.  
 
'flavors' to use your term are there for a reason. if you tell me i practice agile by following the manifesto, without a process around it, i'm sorry but i have to say your full of *it*" 
 
(Posted @ Monday, April 25, 2011 11:43 PM by none too none@none.com)

crap = vulgar? have you visited the slashdots and the dzones of the world? for a geeky site, you sure are something :-) 
 
@joed you just pointed me to a scrumban article. which is, guess what, another flavor. that's kinda conflicting don't you think? here's the point. people go read the manifesto. thinks they know the meaning of life. goes experimenting with whatever they can get their hands on. and goes blogging about it. but guess what. agile is beyond the manifesto. what makes you think that your experiments are better with well documented and incubated practices by agile practitioners with over a hundred years combined experience? yes, be dogmatic initially. and learn the rules. before you can transcend it. in my previous analogy, this is why we have organized religion compared to just let people go off and interpret the bible to however they want to.

scrums and agile manifestos should be used as more of a guideline than a solid rule of thumb

problema ng agile puro nlng agile. dapat meron ding strength na tumatanke ng damage. dpat meron din int na nag susuporta sa agi at str. kung puro kayo agile /gg

My thoughts: 
 
(1) The blog is about 'daily scrum' it may be called different names by different agile flavors like 'daily standup' or just plain 'daily status meeting' but it definitely didn't focus on the scrum stack, which makes most of the comments off-topic. Please don't equate seeing scrum in the title with the blog being about scrum or desecrating it. 
 
(2) The article I posted talked about the difference of agile (scrum, xp), lean/kanban. Again, don't assume that the article is about scrumban because you saw scrum + kanban in the article. I suggest you read it again. The author of the blog is merely stating his take on agile and lean, and his desire to create great software efficiently (i.e not to measure how agile/scrum they are but 'to build great software as fast as possible'). Which, as IT people involved in development dream of. 
 
(3) The agile manifesto is there for a guide. We don't adhere to it blindly. Experimentation always starts with trying what is the defacto of the process. With each team being unique, you will discover which of the processes works for the team. So what do we do with the things that doesn't work? You try to look for alternatives that could work. We don't merely mix things up. We consult, research and try again. And guess what, scrumban was born because of experimentation. 
 
(4) I may not have dozen of years experience but I've been a developer in a co-located team, a non-colocated team, team with other nationalities, one-man team, successful team, failed team, no PM team, with PM team. I have a solid programming experience to back me up. I could and I am still coding on my free time despite my work as a PM nowadays. I participate in meetups, tech groups and mailing list to gather insights and learnings (i.e. learning from their years of experiences as well). I don't pull these things out of the blue. 
 
(5) As this is a company blog, we have the right to monitor our comments and what we post. Besides, if you become aggresive like that in the agile, lean, kanban, scrum, java, mobile dev, etc community, you will be reminded/warned by the moderator/admin as well. 
 
Hope we were able to clear any misunderstandings.