|
|
For each application we implement with a customer, we follow a general project plan. The project plan is refined with each customer to ensure a good fit with the customer's environment, resources, time and budget constraints, and other factors. One of our project managers oversees the project on behalf of Canam, and the customer typically assigns a counterpart from their organization to manage their resources. Regular communication and weekly progress reports at the project management level ensure everyone is aware of progress, issues, and milestones, and adjustments can be made quickly to deal with changes. Typically, the project plans take shape as follows.
 Project Plan Structure:
- Definition
- Implementation
- Customization
- Closing
1. Definition
Phase 1 – Identify Client Requirements
Phase 2 – Project Planning
Phase 3 – Resources Planning
Phase 4 – Project Initiation
These phases are achieved through the following meetings:
- Demonstration meeting
- Informative meetings
- Technical meetings
- Conference calls and email communications
- Kick off meeting
2. Implementation
Phase 5 – Systems Requirement Analysis
Phase 6 – Applications Set Up and Configuration
These phases are achieved through a series of cycles from:
- System Analysis
- ETL Customization
- Application set up and configuration
3. Customization
Phase 7 – Customization Analysis
Phase 8 – Application(s) Customization
These phases are achieved through a series of cycles from:
- Dealer Business Analysis
- Applications Customization
- Quality Assurance processes
4. Closing
Phase 9 – Knowledge Transfer
Phase 10 – Project Review |
|
|
|
|