Complexity science is the study of complex systems, like ecosystems, biological systems, economic systems, etc. "Complexity science" is the scientific approach to "systems thinking". It can be used to understand and explain why complex systems behave the way they do. Ken Schwaber, Jim Highsmith and other experts have explained in their books that a lot of agile concepts have been copied from the study of complex systems. However, agile software development has not covered all there is to learn.

I will show why practices must be agile (self-organized) *and* formal (controlled), why any software development method is doomed to fail, why managing scope is a too simplistic interpretation of the principle of “embracing change”, why most process improvement initiatives are linear and wrong, and why some sets of practices will be show chaotic behaviour when combined.

I will go a step further than what has already been described in mainstream literature, linking some of complexity theory with down-to-earth experience from the trenches in my role as chief information officer for a software development company.

	Cyber Dojo Jon Jagger : 3rd May 2012
	Technical Intro to CD Sam Newman : 30th Apr 2012
	What & Why of Agile Allan Kelly : 30th Apr 2012
	Using Real User Metrics to Measure Perfo Tom Bassindale : 26th Apr 2012
	Simply Business Lukas Oberhuber : 23rd Apr 2012
	7digital Rob Bowley : 23rd Apr 2012
	Milliman Adrian Withy : 23rd Apr 2012
	Elevate Michael Delaney : 23rd Apr 2012
	Bazaarvoice Brendan Sterne : 23rd Apr 2012
	LOVEFiLM Steve Webster : 23rd Apr 2012
	ThoughtWorks Nick Hines : 23rd Apr 2012
	Leadership and agility Ed Cortis : 10th Apr 2012
	Patterns for Development Allan Kelly : 21st Mar 2012
	Elevate Launch Event Michael Delaney : 7th Mar 2012
	Deception and Estimation Linda Rising : 27th Feb 2012