This is indeed an open question. Looks like it has the potential to lead to interesting boards in any case.

I wouldn't frame it as always superior (I'd argue the article falls a bit in this trap). Still this can sometimes be an alternative to driving everything purely on project mode. Some organizations would benefit from such a change of perspective other less so.

An explanation about where the SRP comes from and what it really means. It's very often misunderstood or overlooked.

A bit old but still relevant. Don't focus on tools or the fashion "du jour", instead have a set of timeless principles and evaluate your work against them.

Interesting view... This explains quite well why most organizations have both formal and informal processes. I'm not sure I agree that the informal will always be fought against by management though. I've seen clever management which accepts the informal processes as long as it doesn't harm the organization.

This is definitely a skill which is hard to teach an learn. When it sticks it brings really nice results though...

Reminder that there are a few cases where you might not want your variables declared as const.

A little introductory article about putting an ATDD cycle in place for your development.

I'm a bit on the fence regarding this article. That being said there's something I like about it: it's not always purely about money. It's also a good reminder that if the reward is in monetary form it's almost impossible to not somehow alter team dynamics with it.

I think the Open Agile Adoption ideas have been unfortunately unnoticed. It's thus hard to tell if it would have been fairly efficient. What's sure though is that the widespread mandate approach used during the past decade does a disservice to teams.