Scrum
We foresee an inevitable revolution in the world of software: Software processes will strongly rely in short inspection/ adaptation cycles that will lead to self-organizing structures		For 30 years the world of software has been influenced by the ideas of manufacturing. This all started when manufacturing managers took jobs at software development companies and manufacturing thinkers were asked to think about software. Unfortunately they came with lots of manufacturing baggage and we tried to apply the same techniques used in manufacturing at the time: Standardized repeatable and defined processes TQM techniques Management in the large, where inputs and outputs were only looked as milestones of phases Unfortunately, this manufacture-like paradigm doesn’t fit software development very well. Instead, software requires an approach much more like a NEW PRODUCT development process, because software is always a combination of 1) creating new components or 2) assembling old ones in a new ways. Creating new products requires research, creativity and try/fail approaches. And this fits software very well because: finding the requirements, designing a solution, implementing it, and testing it; do require research, creativity and try/fail implementations. On the other hand, and more often than not, these activities don't come in linear repeatable sequences -- they are simply the result of constant testing and inspection, where any activity may trigger any of the other activities. As such, software requires a new set of practices and attitude, that allow software to be developed in a much more dynamic, adaptive, and self-organizing way.. that's what Scrum is.	Our book (click on the image to go to Amazon)
	Copyright Mike Beedle 2001