Togetherness “Togetherness” is a fittingly nauseating name for an old ideal in planning theory. This ideal is that if anything is shared among people, much should be shared. “Togetherness,” apparently a spiritual resource of the new suburbs, works destructively in cities. The requirement that much shall be shared drives city people apart. When an area of a city lacks a sidewalk life, the people of the place must enlarge their private lives if they are to have anything approaching equivalent contact with their neighbors. They must settle for some form of “togetherness,” in which more is shared with one another than in the life of the sidewalks, or else they must settle for lack of contact. Inevitably the outcome is one or the other; it has to be; and either has distressing results. City residential planning that depends, for contact among neighbors, on personal sharing of this sort, and that cultivates it, often does work well socially, if rather narrowly, for self-selected upper-middle-class people. It solves easy problems for an easy kind of population. So far as I have been able to discover, it fails to work, however, even on its own terms, with any other kind of population. Jane Jacobs, The Death and Life of Great American Cities Doing community classcommunity
Bridges as walls The biographer of Robert Moses, Robert A. Caro, refers to the bridges and underpasses of the famed New York State parkways. These bridges and underpasses are quite low, intentionally specified by Moses to allow only private cars to pass. All those who traveled by bus because they were poor or black or both were barred from the use and enjoyment of the parkland and its "public amenities" by the technical design of the bridges. Even at the time of Robert Moses, a political statement of the form "We don't want them blacks in our parks" would have been unacceptable in New York State. But a technological expression of the same prejudice appeared to be all right. Of course, to the public the intent of the design became evident only after it was executed, and then the bridges were there. Ursula M. Franklin, The Real World of Technology politicsclassracediscriminationurbanism
Why buses represent democracy in action A Talk by Enrique Peñalosa www.youtube.com An advanced city is not one where even the poor use cars, but rather one where even the rich use public transport. transportationclasscities
Manifesto for Agile Software Development A Definition agilemanifesto.org We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Deliver early and continuouslyWelcome changing requirementsSelf-organizing teamsTechnical excellence and good designAgility and sustainability+7 More agileprocesssoftware
Deliver early and continuously Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. A late change in requirements is a competitive advantage planning
Self-organizing teams The best architectures, requirements, and designs emerge from self-organizing teams.
Technical excellence and good design Continuous attention to technical excellence and good design enhances agility. craft
Agility and sustainability Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
The amount of work not done Simplicity—the art of maximizing the amount of work not done—is essential. -2000 Lines Of Code simplicity
Build projects around motivated individuals Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. On ValueOn Talent
Deliver working software frequently Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
Business people and developers Business people and developers must work together daily throughout the project. collaboration
Face-to-face conversations The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. teamwork
Reflect, tune, adjust At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.