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
Two kinds of usability An Article by Ryan Singer world.hey.com I divide usability problems into two kinds: Perceptual: "They couldn't figure out what to do next", "they couldn't find the feature", "they didn't know they could click that button..." etc. Domain-specific: "We need a way to jump back here because in their workflow this happens..." In general, usability testing only catches type 1 perceptual problems. Because in those tests you take people out of the real world and assign them tasks. Usability testing doesn't catch domain-specific problems because they only come up in real life use. uxethnography