You're actually supporting the GP's point, in that you had a good result due to maintaining good practices; 'good people' do not automatically make good software regardless of practice.
Part of the GGP's point was that management has a role to play, and that they know things developers don't. That is the conclusion I was responding to.
You are right too, of course, we still had a process.
Ok, fine... I'll be that guy: No True Scotsman. If you define "good developers" as developers that can successfully create software without management, then yes a group of "good developers" can successfully create software without management.
Understandable. My comment was already getting to long, and I didn't have space to explain every detail.
BTW, if you feel members on your development team aren't capable of self-managing, this book is really good to help you develop those skills: http://www.amazon.com/Clean-Coder-Conduct-Professional-Progr...
Self-management is something every programmer should have in their skill-set.
(disclaimer: I wrote it :)
A different standard, such as not engaging in rash rewrites that disqualifies someone from the "good developer" category, would keep this from becoming a "no true scotsman" argument.
Nailed it.
Those were not good developers; ie, there are some skills they were clearly lacking.
I've lived through the opposite situation as you: management left the company, and we continued to release for the next few months without any management at all.
The key, I think, was that the managers had pushed the decision making down. Everyone took turns being scrum master......so when the next sprint came, we elected a new scrum master and carried on.
Fred Brooks pointed out that with a group of competent programmers, any development methodology can work. The best development methodologies help programmers become self-sufficient (teaching them the skills if they don't have them), instead of trying to micro-manage.