The drift The Situationists were also practitioners of a special urban-analytic walking style, the dérive—the “drift”—which Debord described as “a technique of transient passage through varied ambiences. The dérive entails playful-constructive behavior and awareness of psychogeographical effects; which completely distinguishes it from the classical notions of the journey and the stroll.” “In a dérive,” Debord deadpans, “one or more persons during a certain period drop their usual motives for movement and action, their relations, their work and leisure activities, and let themselves be drawn by the attractions of the terrain and the encounters they find there." The dérive joins the free association of surrealism, the LSD of hippiedom, and cinematic montage as tactics for overcoming the fixity of received ideas of order and logic. By putting progress through the city into a state of constant indeterminacy, it represents a schooled “style” of being lost. Michael Sorkin, 20 Minutes in Manhattan PsychogeographyRaindrops leaving an erratic trail psychologymovement
The axis of movement Moving in the city means constantly changing the axis of movement. In general, lateral movement is confined to a single plane, what’s called grade, the ground level. Because circulation in multistory buildings is fundamentally one way—which is to say from the bottom up—the condition at the top is invariably different from that at the bottom. Rooftop circulation is the domain of Fantômas, of cat burglars and fleeing criminals, of lovers, and of those acrobatic enough to negotiate the gaps between buildings. Michael Sorkin, 20 Minutes in Manhattan A Burglar's Guide to the City movement
Why Scrum is killing your product An Article by Henry Latham uxdesign.cc Product owner vs. product managerWe optimize what we measure Beware SAFe, an Unholy Incarnation of Darkness agilemanagementsoftwareproducts
Product owner vs. product manager A Product Owner is focused on output i.e. how quickly can we build these features? Product Management, on the other hand, is focused on outcomes i.e. why are we building these features in the first place? agileproducts
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. optimizationagilefeatures