Project Control Process
To ensure projects are within the defined scope and schedule, we have the following processes in palce:
Version Control
We use VSS tool to ensure that only one writeable version of each component (script, authored module, etc) of a project can be signed out at any given time from a central server location. Until the writeable copy has been signed in, just read-only copies are available to other developers. This allows our developers to avoid overwriting files and losing work. It also enables developers to revert to previous versions of courseware modules, if necessary.
Back-up Procedure
Back-ups of the files stored in the VSS tool are taken at the end of each workweek and saved to disk. Work on individual computer workstations is backed up to the backup server at the end of each workweek.
Change Management
Change management is negotiated between the Client and C&K and is specified in the Contract. The terms of change management will include items such as revisions resulting from reviews (i.e, scripts, authored modules, etc) and degree of project modification allowed after signed off project definition. The change management process will also stipulate possible additional fees for major changes to signed off or completed work. Where changes/modifications are made to a project in progress, the change must be requested and approved using the Change Management Form or by e-mails if agreed upon in the Project Management Plan.
Document Storage
Contractual and financial documents will be stored in C&K Management's business office. Electronic copies of scripts, Signoffs, reviews sheets, and source files (graphics, authored modules, PDFs, etc.) will be stored in the VSS account set up for each project at project commencement. These will be archived on disk one year after project completion. Hard copy working documents, such as process forms (signoffs, project definition, hard copies of scripts, etc.), will be stored in the Quality Assurance Project Archive and, once stored, must be signed out. |