As a technical program manager implementing Scrum for the past two years, bottom line, it works. If you do not know about Scrum, we have an introductory article titled “The Basics of Scrum, Sprints and Cycles” which I highly recommend you read first.
Nowadays, many Project Managers and Developers are using the Scrum framework for their large software projects. Using this proven methodology allows the engineering team to set clear expectations about the scope of the project and timelines, enables the client to be predictable and plan training/readiness activities and provides transparency and accountability to all sides.
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.