The 1916 Zoning Resolution Architecturally, what is striking about the 1916 legislation is that it sought to articulate a logical formula for achieving a public good in the absence of a specific vision of exactly what would actually be produced. Michael Sorkin, 20 Minutes in Manhattan regulationsconstraints
The air doesn't know about zoning boundaries Work uses suggest another bugaboo: reeking smokestacks and flying ash. Of course reeking smokestacks and flying ash are harmful, but it does not follow that intensive city manufacturing (most of which produces no such nasty by-products) or other work uses must be segregated from dwellings. Indeed, the notion that reek or fumes are to be combated by zoning and land-sorting classifications at all is ridiculous. The air doesn’t know about zoning boundaries. Regulations specifically aimed at the smoke or the reek itself are to the point. Jane Jacobs, The Death and Life of Great American Cities zoningregulationsseparation
The source code for SimCity Local Code was Sorkin’s attempt to design a whole city from scratch—with one big twist. The whole thing had been written as if it were the byzantine, nearly impossible to follow codes and regulations for an entire, hypothetical metropolis. The effect is like stumbling upon the source code for SimCity. Sorkin’s exhaustively made point was that, if you know everything about a given metropolis, from its plumbing standards to its parking requirements, its sewer capacity to the borders of its school districts, then you could more or less accurately imagine the future form of that city from the ground up. Geoff Manaugh, A Burglar's Guide to the City Local Code: The Constitution of a City at 42º N Latitude rulesregulations
Local Code: The Constitution of a City at 42º N Latitude A Book by Michael Sorkin www.goodreads.com The source code for SimCityLocal Code: 3,659 Proposals About Data, Design & The Nature of Cities regulationslawcities
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