Going Beyond the Waterfall

Every year technology projects face hard decisions about how to mitigate risk and address challenges as teams work to deliver on the promised business value in terms of ROI by creating useful solutions. Those decisions impact scope at every step and help evolve it until the final product is delivered and implemented. It means scope cannot be set in stone. Current literature focuses on scope under the project manager, not as a task that is impacted by multiple factors before, during and after the project. This guide crosses roles, phases and the triple constraint barriers to identify the risks and issues of restricting scope management to a single role, and demonstrates how it should be managed. Going Beyond the Waterfall explains how to define scope at the outset of a project. It provides a solid model for predicting, and managing solution scope across a project life cycle where the decisions and actions of every project team member contribute to that evolutionary process. It will help project teams understand how and when scope shifts and changes as a part of a living development process. This guide identifies the impacts that key tasks and activities will have on scope and how each can be managed effectively to prevent unnecessary scope creep and reduce run-away projects. Key Features Defines scope from program management to business case, to requirements and business as usual (BAU) Identifies how scope evolves and what causes it to change Describes how project and enterprise architecture methodologies impact scope & management Demonstrates the implications of change management and implementation on scope throughout development and roll-out processes Discusses the evolution of scope as a key process in the achievement of the project objectives Explains the definition and management process of scope from concept to implementation Illustrates how stakeholder engagement, requirements, project and enterprise architecture methodologies impact scope & management