PROJECT DESCRIPTION This section provides a high-level description of the project. This description should not contain too much detail but should provide general information about what the project is, how it will be done, and what it is intended to accomplish. As the project moves forward the details will be developed, but for the project charter, high-level information is what should be provided. The ISA project will provide increased security to the company's IT infrastructure and, more specifically, to the company intranet. The ISA project will utilize improved technology in the form of security hardware and software in order to prevent external breaches of the company intranet. All hardware and software will be integrated into the company's current |T platforms in order to establish increased security while allowing all systems and processes to continue without interruption. Project Objectives and Success Criteria Objectives should be SMART: Specific, Measurable, Attainable, Realistic, and Time-bound. The project manager must be able to track these objectives in order to determine if the project is on the path to success. Vague, confusing, and unrealistic objectives make it difficult to measure progress and success. The objectives which mutually support the milestones and deliverables for this project have been identified. In order to achieve success on the ISA project, the following objectives must be met within the designated time and budget allocations: - Develop security solution methodology to present to the VP of Technology within the next 20 days - Complete list of required hardware/software which meets budget allocation within the next 25 days - Create a simulated solution in the IT lab using all purchased hardware and software to test the solution within the next 60 days - Achieve a simulated solution which allows no security breaches and complete testing within the next 90 days - Implement the solution across the organization within the next 120 days Requirements The project team should develop a list of all highlevel project requirements. These requirements are clear guidelines within which the project must conform and may be a result of input from the project sponsor, customer, stakeholders, or the project team. This project must meet the following list of requirements in order to achieve success. - The solution must be tested in the IT lab prior to deployment - Solution must be implemented without disruption to operations Additional requirements may be added as necessary, with project sponsor approval, as the project moves forward. Constraints Constraints are restrictions or limitations that the project manager must deal with pertaining to people, money, time, or equipment. It is the project manager's role to balance these constraints with available resources in order to ensure project success. The following constraints pertain to the ISA project: - All security hardware and software must be compatible with our current IT platforms - All hardware and software must be purchased in accordance with the allocated budget and timeline - Two |T specialists and one security specialist will be provided as resources for this project Assumptions The project team must identify the assumptions they will be working under as the project goes forward. These assumptions are what the project manager/team expect to have or be made available without anyone specifically stating so. The following are a list of assumptions. Upon agreement and signature of this document, all parties acknowledge that these assumptions are true and correct: - This project has the full support of the project sponsor, stakeholders, and all departments - The purpose of this project will be communicated throughout the company prior to deployment - The IT manager will provide additional resources if necessary Preliminary Scope Statement The preliminary scope statement is a general paragraph which highlights what the project will include, any high-level resource or requirement descriptions, and what will constitute completion of the project. This preliminary scope statement is exactly that: preliminary. All of this information will be expanded upon in greater detail as the project moves forward and undergoes progressive elaboration. Assumptions The project team must identify the assumptions they will be working under as the project goes forward. These assumptions are what the project manager/team expect to have or be made available without anyone specifically stating so. The following are a list of assumptions. Upon agreement and signature of this document, all parties acknowledge that these assumptions are true and correct: - This project has the full support of the project sponsor, stakeholders, and all departments - The purpose of this project will be communicated throughout the company prior to deployment - The IT manager will provide additional resources if necessary Preliminary Scope Statement The preliminary scope statement is a general paragraph which highlights what the project will include, any high-level resource or requirement descriptions, and what will constitute completion of the project. This preliminary scope statement is exactly that: preliminary. All of this information will be expanded upon in greater detail as the project moves forward and undergoes progressive elaboration. PROJECT MANAGEMENT DOCS ProjectManage me ntDocs.com The ISA project will include the design, testing, and delivery of an improved intranet security system throughout the organization. All personnel, hardware, and software resources will be managed by the project team. All project work will be independent of daily and ongoing operations and all required testing will be done in the IT laboratory. All project funding will be managed by the project manager up to and including the allocated amounts in this document. Any additional funding requires approval from the project sponsor. This project will conclude when the final report is submitted within 30 days after the intranet security solution is tested and deployed throughout the organization, all technical documentation is complete and distributed to the appropriate personnel, and a list of future security considerations is complete and submitted to the VP of Technology