There is one very simple rule to make distributed projects work – or fail:
Do what you say, say what you do.
“Agile” is becoming a “slow hype”. Originating in IT, where it has turned everything upside down many years ago, the desire to “be agile” is starting to spread into other industries. Especially where feedback cycles are a lot slower than in IT, leaders would like to benefit from the “toolbox” of agile without recreating the entire company culture.
On the other hand, every serious practitioner of agile is going to tell you “agile is an attitude” or some such. Agilists tell you that agile is a mindset, and that that mindset has created a matching toolset, and that the toolset without the mindset has questionable value.
In a sense, both are right. In another sense, both aren’t.
Continue reading Agile – mindset or toolset?
There is a simple pattern that can be used to spot and solve one of the most unnverving communications problems in teams, distributed or otherwise. Once you know the problem, there’s a simple recipe for a solution.
Virtual teams are around for ~20 years now. Still, they are far from universally mastered. Here is a first clue about what it takes to make them work.
Out of ten bullets on software architecture, this is the third: the thought that software architecture is not decided by features, or at least: that features usually only have a minor impact on the whole topic Continue reading Features. Software Architecture (3/10)
Out of ten bullets on software architecture, this is the second: the realization that no software architecture is good or bad – at best, it is appropriate (or not). Continue reading No good, no bad: Software Architecture (2/10)
Out of ten bullets on software architecture, this is the first: the realization that there is no silver bullet. Continue reading No Silver Bullet: Software Architecture (1/10)
Most people have heared about Zuckerbergs and Musks argument about AI. Here are four observations that probably make this argument mute:
Continue reading Four points on AI
A while ago, someone provoked me to put software architecture in ten bullets. Nothing that short does such an important topic justice, but these ten held up pretty well in day-to-day discussions – even though I don’t consider myself an architect.
“Can we return to a constructive discussion, please”? – Often, that is easier said than done. However, there is one question that usually does the trick: Continue reading My favorite question