Laserfiche WebLink
Final project costs are established through the development of a detailed Scope of Work — one that <br />establishes what products and sewices will be delivered as well As those th,_ i' will flflr"' e provided <br />part of the established nee. A level of open and honest communication among all stakeholders is <br />required such that system functionality can be balanced with available funding, and appropriate and <br />reasonable expectations set. Once these elements have been addressed, cost control becomes a multi- <br />tiered effort involving effective project management, clear communication among stakeholders (especially <br />the Project Managers), schedule management, and quality control. To protect both parties, client and <br />consultant, a Change Control Process must be developed and adhered to throughout all phases of the <br />project <br />Any modifications or deviations from the agreed upon Scope of Work, including system functionality, <br />service delivery, technical documentation, or project schedule or budget will be subject to CHANGE <br />CONTROL procedures: <br />Any project team member may initiate a CHANGE REQUEST whenever there is a perceived need for a <br />change that will affect the desired or anticipated outcome of the work or any element of the project. The <br />project team member should use a CHANGE CCNTROL.No ICE (C CM form as appropriate for the change: <br />Project team <br />member identifies <br />need for change. <br />PM's review change request <br />and determine if change <br />should be considered. <br />Proceed <br />with <br />change? <br />NO <br />YES <br />Initiating PM Prepares <br />and Subits CCN Form <br />PMs review CCN <br />Changes <br />required <br />to CCN? <br />Initiating PM <br />updates CCN <br />as needed <br />No <br />Timmons Group PM <br />updates PMP and <br />SD&C as needed <br />Updated project <br />documents approved by <br />PMs and distributed to <br />project team members <br />Project team <br />implements <br />changes <br />1. Agreement to a CHANGE REQUEST signifies agreement to a change in overall costs, functionality, <br />time scales, or other identified project impact. <br />2. Changes will be identified and communicated by / to the respective Project Managers by any of <br />the prescribed communication channels. CHANCE. REQUESTS may be introduced via verbal <br />conversation or other form of communication but must be supported by the appropriate CCN <br />document. <br />3. All C OV's will be signed by both the Timmons Group and the Gity's Project Managers to indicate <br />acceptance of the changes. <br />7 <br />