My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
AG 1999 03 15
CabarrusCountyDocuments
>
Public Meetings
>
Agendas
>
BOC
>
1999
>
AG 1999 03 15
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/25/2002 5:58:00 PM
Creation date
11/27/2017 11:48:47 AM
Metadata
Fields
Template:
Meeting Minutes
Doc Type
Agenda
Meeting Minutes - Date
3/15/1999
Board
Board of Commissioners
Meeting Type
Regular
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
237
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
02/22/99 11:$0 FAT 17044249895 ]QgANE CBARLO'r~ ~01¢/021 <br /> <br />Cabarrus County <br /> <br />Year 2000 Readiness Audit Proposal <br /> <br />Koane tracks progress against thc project plan through weekly status reports produced internally. Kcauc. <br />will providc a wrlttcn status report weekly. Status rcpor~ will detail thc completion of deliverables, with <br />time and cost to date by activity. In addition to these formal status reports, we will inform Cabarrus <br />County immediately if anticipated changes or other risks threaten to inercam; our estimated costs or <br />schedule. <br /> <br />5.2,2 PRODUCTIVITY MANAGEMI~NT -- THE "3-q 0-3" <br /> <br />Keane's Project Control and Reporting Process Standards (PCILP - a.k.a. "3-I0-3") apply to all product- <br />based, K~me-clireotcd projects. <br /> <br />The following are thc Project Control and Reporting Process Standards for product-based, Keauo- <br />directed projects. <br /> <br />5.2.2.1 Project Initiation: <br />At Project Initiation, tim following thr~c items must be/n pla~c and are the r~sponsibility of thc project <br />manager to complete: <br /> <br />1. A 8tat~mextt of Work must bc completed for ail projeclal. <br />2. A "PreAudit" chcckli~ must bc completed. <br />3. A Project RJ~k~. and Mit/gation or "PRAM" Profile must be completed. <br /> <br />5.2.2.2 Project Execution: <br />During project execution, the following 10 controls must be in place: <br /> <br />1. The project manager must conduct a Weekly Worlc~lan Review with thc Keane projc,t te=m <br />2. A Weekly Status Re~ort must be completed by the project n~mager and submitted to tgranch <br /> Management. <br />3. Thc project manager mu~ conduct a Weeki~ Status Review with the ¢lie~t. <br />4. The projectmanagcr must maintain a PrqiectNotcbook. <br />5. A Prelect Plan in Keanc Fmmework~ format must be updated weekly by tho project <br /> manager. <br />6. A ibrmal C_han~e Control process must be documentrxl by the project manager and followed. <br />7. A formal Acceptance_.Process for deliverables must be do0um~mtecl by the pwje~t manager <br /> and followed. <br />8. Formal ~ must be initiated by Branch Management and conducted at lwt once <br /> per quarter. <br />9. The Project Summary_ Disolav (PSDI will be updated monthly by the project manager and <br /> submiRed to Branch Management. <br />10. Branch Management will conduct a Monthly Branch Proieet Review. For all projects over <br /> $250K and all £med priced projects over $100,000, the updated PSD must then be sent to the <br /> Corpoxate PSD Rc. pository. <br /> <br />5.2.2.3 Post-Project: <br />At the end o£the project, the following thmc actions mu~t bc taken by the project manager: <br /> <br />1. A Post-Project Audit must be oonducted. <br /> <br />Proprietary and Confidential <br /> 02/22/99 <br /> <br />13 <br /> <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.