Beware SAFe, an Unholy Incarnation of Darkness An Article by Sean Dexter seandexter1.medium.com The Lean Portfolio Management function that controls funding, are given sole authority to approve which Portfolio Epics move into each stream. Epics are not explanations about a problem that needs to be solved. They are pre-formed ideas about how best to solve those problems. Right away we can see signs of the old-school mindset of viewing teams as a “delivery” function instead of a strategic one. The high level thinkers come up with ideas, and the low level doers execute on those ideas. Ignored is the possibility that those closest to the work might be best equipped to make decisions about it. Escaping from this misguided mindset is a core goal of Agile thinking that SAFe fails to remotely accomplish. SAFe is oriented around volume, not value Why Scrum is killing your productAgile Scrum is not workingThe management strategy that saved Apollo 11Design Systems, Agile, and Industrialization agile
Such tortuous syntax How does a writer manage to turn out such tortuous syntax? It happens when he shovels phrase after phrase onto the page in the order which each one occurs to him. The problem is that the order in which thoughts occur to the writer is different from the order in which they are easily discovered by a reader. It’s a syntactic version of the curse of knowledge. The writer can see the links among the concepts in his internal web of knowledge, and has forgotten that a reader needs to build an orderly tree to decipher them from his string of words. Steven Pinker, The Sense of Style Who the fuck is Guy Debord?The curse of knowledgeChoose a suitable design and hold to it