Software delivery expectations have been rapidly evolving for the past decade. Large software projects are shifting from the traditional waterfall process to agile methods. In the waterfall approach, business process, workflow and behaviors are defined at project start, engineering effort is estimated and development begins once requirements are confirmed. Change management is used for updates after baseline. Software enters business review shortly before scheduled release and support is typically handled separately, with documentation handed off to an operations team.