Program System Structure Explanation: This section identifies the Program in graphical view at the three highest levels: 1) Program, 2) Project, and 3) Systems. Where Sub-programs are included, add them to Level 2 and the Projects at Level 3. Schedule Explanation: This section includes the Program begin and end dates, based on all the known Projects within the Program. It will identify the critical path for accomplishing the Program goals. Program’s Acknowledge that some or all of the Component Projects may not have completed project Program’s plans or individual timelines at the time of the Program document the method Charter’s creation. Also for determining milestone dates when no project plans exist. If timelines are presented in graphic form include a legend in this section for determining the significance of specific indicators used in the graphics. Program Roadmap Explanation: This subsection represents at a very high level the Program chronological critical milestones in graphical representation. Construct a significant milestones and dependencies list for all known Projects within the Program in a table format. This section describes the key dependencies including business processes, legislative, and IT for the Program, based on all the known Projects affecting the success of the Program. Program dependencies are Project activities or deliverables within the Program that depend on key milestone activities or deliverables of another Project. All of these Projects may or may not be included in the Program. Timelines Explanation: As needed, consider including various Program timelines in this section of the Program Charter in graphic form. Change the definition of the milestone colors to represent the Program. You may also wish to copy the timeline to denote each year, so if you have a five-year Program, you may have five timelines, for example. Benefit Realization Strategy Explanation: This section includes a brief overview of the cost-benefit analysis. The Program Sponsor and/or the Program Manager need to document the key benefits and how they will be realized. Ideally, the Program should return a positive Return on Investment (ROI) over six years. That is, the total cost of ownership (TCO) of (a) implementing the Program, plus (b) the cost of operating and maintaining
Program System Structure Explanation: This section identifies the Program in graphical view at the three highest levels: 1) Program, 2) Project, and 3) Systems. Where Sub-programs are included, add them to Level 2 and the Projects at Level 3. Schedule Explanation: This section includes the Program begin and end dates, based on all the known Projects within the Program. It will identify the Program’s critical path for accomplishing the Program goals. Acknowledge that some or all of the Program’s Component Projects may not have completed project plans or individual timelines at the time of the Program Charter’s creation. Also document the method for determining milestone dates when no project plans exist. If timelines are presented in graphic form include a legend in this section for determining the significance of specific indicators used in the graphics. Program Roadmap Explanation: This subsection represents at a very high level the Program chronological critical milestones in graphical representation. Construct a significant milestones and dependencies list for all known Projects within the Program in a table format. This section describes the key dependencies including business processes, legislative, and IT for the Program, based on all the known Projects affecting the success of the Program. Program dependencies are Project activities or deliverables within the Program that depend on key milestone activities or deliverables of another Project. All of these Projects may or may not be included in the Program. Timelines Explanation: As needed, consider including various Program timelines in this section of the Program Charter in graphic form. Change the definition of the milestone colors to represent the Program. You may also wish to copy the timeline to denote each year, so if you have a five-year Program, you may have five timelines, for example. Benefit Realization Strategy Explanation: This section includes a brief overview of the cost-benefit analysis. The Program Sponsor and/or the Program Manager need to document the key benefits and how they will be realized. Ideally, the Program should return a positive Return on Investment (ROI) over six years. That is, the total cost of ownership (TCO) of (a) implementing the Program, plus (b) the cost of operating and maintaining