Doing projects better doesn't stop at agile. In this presentation I attempt to distill new advances in software development from the field of complexity science. 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 behavior when combined.