We optimize what we measure Scrum does not say “only focus on output”, but, unfortunately, humans will optimize for what they measure. If you worry about story points & hitting your estimations, that’s what is going to consume your attention. That is what you and your team will optimize for. And that is the core critique of Scrum as it is practiced: That it focuses a product team’s attention so heavily on delivery — on building lots of features quickly & efficiently — that teams fail to focus on spending time to discover what the right thing to build is. Henry Latham, Why Scrum is killing your product optimizationagilefeatures
v0.crap I couldn’t seem to convince my writers that I was genuinely ok working with a super rough first draft — i.e., that I’d harbor no hidden judgment about their intelligence, commitment, or excellence at their craft. So I came up with a new word. “Just give me a v0.crap.” (Pronounced “version zero dot crap”.) v.0.crap works because it’s attuned to the psychology of the situation. It’s punching through our innate desire not to “look bad”, plus years of corporate conditioning that tells us not to share less-than-polished work. It’s easier for people used to delivering exceptional work to feel they’ve exceeded the goal of “crap”; they can sit comfortably in “good enough for the current purpose.” Courtney Hohne, The monkey, the tiger beetle and the language of innovation blog.x.company Writing, Briefly qualityideaswritingmaking