How do you measure the success of a software project? Do you rely solely on deploying the solution on schedule? Does the quantity and quality of design documents, such as a vision and scope document, package diagrams, component diagrams, key feature class diagrams, and other various Unified Modeling Language (UML) diagrams provide an indicator of a project’s success or failure? Have you seen the documentation created in a waterfall design–based software development project? I think trying to keep all of these documents in sync with the constantly changing requirements of a system is a nightmare. No thanks; I’d rather sleep at night.