Projects Integration Strategy – 7

New Scope Administration

New Scope is one of the very important factor, which mostly neglected by the projects teams. You really need to manage your new scope. As you move near to Integration of projects into one Program at that time your old program and projects scope changed into very new scope, which you don’t know. New Scope is kind of blind spot that every program Integration strategy should consider.

Ok, that’s lots of talking, so what is the solution, honey.

Solution is:
Each integration project starts with a high level understanding of the scope of their project from the Program Roadmap and roadmap estimates. As projects review requirements through the inception and elaboration phases, they are expected to discover the following:

• Clarifications to the scope of the project to make it more complex than was originally envisioned during program planning.
• Elements of functionality that logically belong to their project that were not identified during program planning.
• Elements of functionality that were not identified during program planning that don’t appear to fit well with any integration project.
• Elements of functionality that were not planned to be delivered during the Alliance release that are re-assessed and determined to be mandatory within this release.

To manage this watery scope, each project is managing change through formal change requests. To manage scope that is not logically in any project, the program SHOULD maintain a Scope Management spreadsheet. That spreadsheet SHOULD available for view onto the Program intranet. Spreadsheet, scope items are listed along with the project that will be picking up this scope. Spreadsheet SHOULD also be used for program close out, as it will track scope items that did not logically belong within the program integration.