I can point you to Alistair Cockburn's thoughts on this aspect of 'true' Agile projects:
One member in the Crystal family of methodologies is Crystal Clear.
Crystal Clear can be described to a Level 3 listener in the following
“Put 4-6 people in a room with workstations and whiteboards and access to the users. Have them deliver running, tested software to the
users every one or two months, and otherwise leave them alone.”
I did, in fact, describe Crystal Clear in those words to a savvy
project sponsor. He followed those instructions and reported five
months later, “We did what you said, and it worked!”
I interviewed the team leader some months later and his report was
about as short as my instructions:
“Following your suggestion, the four of us took over this conference
room, which has network connections. We kept it for all four months,
drawing on the whiteboards over there, delivering software as we went.
It worked great.”
that's what agile was about, and it seems this is the approach taken by the Anarchy methodology - the point is that, if you have experienced guys, then you can tell them to "sod off and make it work" and they will do just that. (this doesn't work with less experienced people, you wouldn't let a team of juniors do it without at least some supervision).
All the guff about agile that's built up over the years, like daily standups and scrum boards, product backlog grooming sessions, pre-meeting meetings about the product backlog scrum board grooming session planning meetings.. are all heavyweight project stuff that should be seen as overheads to successful product delivery.
Too much today though, these things are seen as mandatory and the 'agile' methodology descends into a system that has more process than the old methods!