Commitment Review

Summary

When an idea for Network Improvement has been proposed and explored, the proponents will go before the Commitment Review Board to determine if there is enough merit in the idea to continue planning in more detail. The Commitment Review Board consists of (a) all affected parties in IS, and (b) all resource (funding) providers.

They review the Project Plan, which includes:

• Which IS groups are affected by the proposed network improvement.
• The purpose and corporate benefits of the project.
• The financial impact and cost/benefit (ROI) analysis.
• The initial target architecture for interface fit and potential problems.
• The initial deployment and support plans for feasibility and risks.

Preparing for the Commitment Review

A: Prepare a Project Plan describing the proposed Network Improvement Project ("the Project").

The Project Plan template can be found at (http://xxx.xxx/NetImprove/Templates/Project Plan.doc)

B: Send this filled out Project Plan to the Network Improvement manager to have it posted on the Architecture Review web site (http://xxx.xxx/NetImprove/Project_Name/Project Plan.doc). If it is not filled out completely, it will be returned to you for completion.

C: Within 3 days you should receive a scheduled date (based on your date selection) stating when you will be able to go before the Architecture Review Board for the first review (the "Commitment Review").

D: Prepare a summary viewgraph presentation (no more than 2 slides per Summary heading). You will have up to 20 minutes to present, with another 10 minutes for questions. Please try not to go overtime. If you think your project is so complex that it cannot be fully explained in this time, please call the Network Improvement manager to request an extension.

During the Commitment Review

A: During the presentation, note any concerns or problems raised, and make sure that these issues are dealt with after the meeting.

B: After the presentation, the representatives will discuss with you whether or not you should continue with this project, and why.

C: After the decision has been made, if the decision is either (a) to continue the project without conditions, or (b) to continue the project under the condition that some issues are dealt with, then:

You should identify the IS managers whose groups will need to take a role in building, coding, or implementing this project, and those whose groups will be responsible for maintaining and managing it once it is installed. Ask them if they think they will need to have someone from their group assigned to work with you in developing the Architecture Plan, the Test Plan, the Deployment Plan, and the Support Plan. If they think their group needs to be involved in your project, make sure that you get a date by which they will have identified that resource for you.

After the Commitment Review

A: After the presentation, write down the Commitment Review meeting notes for your project. Focus on the decision made: either to continue the project without conditions, or to continue the project under the condition that some issues are dealt with. If there were conditions or problems raised, then resolve those issues and record the resolution in your meeting notes. When complete, send these meeting notes to the Network Improvement manager. They will be posted along with your Project Plan.

B: If there were problems or conditions attached to the acceptance of your project, rethink and rewrite those parts of the Project Plan document that required further work, send it in again and request a new scheduled Commitment review date.