Thread by @alshalloway

@Lilysonherway @johncutlefish @allenholub it's not that SAFe has too many things. It's the way it's organized. People confuse having too many items with poor design. There are things that SAFe should have: MBIs, focused solution teams, more. The challenge is it's organized around hierarchy instead of value stream. 1/

@Lilysonherway @johncutlefish @allenholub it's not how much is in something that makes it complicated, it's how it's organized. This distinction is lost both in SAFe and Scrum (which I think is ironic). SAFe ignores design so it's complicated to use. Scrum confuses # of items in it with simple. 2/

@Lilysonherway @johncutlefish @allenholub Scrum is simple in #of pieces but poorly designed so it's not fit for purpose in most place. Consider unicycle vs bicycle. One is simpler in design the other is easier to use and more effective. This is why Scrum has problems - it's designed around its values and empiricism 3/

@Lilysonherway @johncutlefish @allenholub when you understand theory you can combine empiricism with theory and make better, intuitive designs. Scrum also conflates it being easy to use with the problem it is being used to solve being easy. ... 4/

@Lilysonherway @johncutlefish @allenholub That's like saying a hammer is easy to use but difficult to master. No a hammer is relatively easy to master as I learned one summer helping a friend build a house. But building a house is difficult to master. 5/5

@Lilysonherway @johncutlefish @allenholub @threadreaderapp unroll