Defining the scope of the project
|
|
.gif "Previous Topic")
.gif "Next Topic")
Defining the scope of the project
The project scope section should include the following:
- Identifying the business goals. Determine what the business goals are and calculate the return-on-investment (ROI) and the total cost of ownership (TCO). Define your vision for why you are using Microsoft Dynamics CRM.
- Identifying the risk factors. Make contingency plans to reduce risks and dependencies. These plans might include additional training, internal public relations, and support. Risk factors might include delivery of new hardware and software, dependencies on important personnel or outside vendors, deployment timing, and users' resistance to change.
- Identifying the implementation team. Designate a person who will be responsible for tracking costs, schedules, performance, and risk factors. Determine executive sponsors, project managers, and project team members. This task includes deciding if an outside consultant is needed. Define an escalation process and determine who is responsible for making final decisions.
- Planning usage. Define who will be expected to use Microsoft Dynamics CRM, what tasks will be done by using Microsoft Dynamics CRM, and what old systems will be discontinued (if any).
- Identifying equipment and software needs. Document the state of the current technical infrastructure, and the hardware, software, and network changes that are required for Microsoft Dynamics CRM. Include information about technical risks and constraints.
- Determining the budget and schedule. Include estimates. If you plan a phased deployment by location, functionality, or both, set target dates and budgets for each part.
- Planning for change management. Determine how to request, review, and approve changes during the implementation process.