In the past, a long waterfall-style development was briefly punctuated by the delivery of documents such as the design documents and status reports. It finally culminated with the real end goal—the software delivery. The documents were often seen as the proxy for the real product because nothing else was available to communicate progress through the long dark phases proceeding the final delivery. Needless to say, these documents often had no correlation whatsoever to the actual product or its quality. A status report could at best only communicate the past (which everyone already knew!), but never really predict the future in ways that would be meaningful to the product development team and the customers so that they could collectively re-plan their activities to align with the evolving dynamics of a project.