Ana səhifə

Microsoft Dynamics crm planning Guide


Yüklə 0.59 Mb.
səhifə5/19
tarix18.07.2016
ölçüsü0.59 Mb.
1   2   3   4   5   6   7   8   9   ...   19

Planning a Microsoft Dynamics CRM implementation


This section describes how to plan a Microsoft Dynamics CRM implementation.

Planning tasks for business managers


During planning, business managers should:

  1. Plan how your business structure maps to Microsoft Dynamics CRM. Take an organization chart for your area, and decide which security roles each user needs. Define the teams and queues and who should be on each.

  2. Decide whether you want to automate any business processes. Microsoft Dynamics CRM is a solution for automating internal business processes by creating workflow rules that describe routine and repetitive tasks involving daily business operations.

To use the workflow feature, you build rules. For each rule, you define the trigger and the resulting action. Rules can be triggered when a record changes state (open to closed, active to inactive), when a record is created, when a record is assigned, or manually.

The following scenarios are examples of how to automate a business process by using workflow.



  • Assign different kinds of cases to specific service representatives.

A workflow rule could determine the category of the case (shipping problem, product problem, or billing problem), and assign it to the appropriate queue. If a case stays in a queue for two days without a resolution, the rule could automatically assign the case to the manager. If after four days, the case is still not resolved, it might be routed to an escalation queue.

  • Communicate with other databases at your organization.

A workflow rule could notify your billing system whenever an invoice is created in Microsoft Dynamics CRM.

  • Notify customers automatically when an order ships.

When the invoice status changes to Fully Shipped, the customer can be automatically notified of the shipment through e-mail, by using a predefined e-mail template.

  • Automatically e-mail a message to new leads.

After a lead is created, depending on the stage that the lead is identified at, different activities can be scheduled. For a stage 1 lead, an introductory e-mail letter can be automatically sent and an activity scheduled with a due date of one month for follow-up. For a stage 2 lead, an activity can be scheduled for a specific salesperson to call the lead and mail a product catalog. For a stage 3 or 4 lead, an activity is scheduled for a specific salesperson to fax promotions and collateral to the customer, with another task activity to follow up in a week.

  • Coordinate handling of dissatisfied customers between sales and support.

After a case is resolved with customer satisfaction set to "dissatisfied," an activity can be automatically scheduled for a salesperson to call the customer. If the satisfaction is set to "very dissatisfied," an activity can be automatically scheduled for a manager to call the customer.

  1. Collect configuration data about your products and competitors.

For more information products and competitor data, see the Microsoft Dynamics CRM Help topics.

  1. Decide whether you have to customize Microsoft Dynamics CRM to meet your business needs.

For more information about customization, see the Microsoft Dynamics CRM Help topics.

  1. Look at the default reports provided with Microsoft Dynamics CRM and determine whether additional reports are needed.

Microsoft Dynamics CRM includes standard reports that you can use to answer common business questions. You can modify these reports or create your own if you have additional reporting needs.

As you design your Microsoft Dynamics CRM system, the managers should review the reports for their areas to make sure that the reports will meet their needs. The Help includes a topic for the default reports in each area of Microsoft Dynamics CRM, with a link to a detailed topic that describes the business questions the report is designed to answer.


Development tasks for business managers


During development, business managers should:

  1. Closely monitor configuration and customization changes to make sure that they meet business needs.

  2. Be available to answer detailed questions as they occur.

  3. Get trained on the management tasks that you can do, such as adding and removing users, and entering configuration changes.



Deployment tasks for business managers


During deployment, business managers should:

  1. Make sure training needs of employees are met.

  2. Listen to the initial experiences of Microsoft Dynamics CRM users and determine additional configuration and customization requirements.



Post-deployment tasks for business managers


During post-deployment, also known as the operation phase in Microsoft Dynamics Sure Step, business managers should:

  1. Learn about the experiences of Microsoft Dynamics CRM users and determine additional configuration and customization requirements.

  2. Use the data in Microsoft Dynamics CRM reports to strengthen your organization's sales, marketing, and service functions.



Managing a Microsoft Dynamics CRM implementation project


As you plan your implementation, the first step is to determine the project scope. Because the tasks depend on the complexity of your implementation project, this section of the documentation divides implementations into two categories:

  • Rapid implementation. Expect to spend 30 work days if you are doing a rapid implementation that requires minimal customization, no migration of source data or integration with other applications, and training up to ten users.

  • Measured or Full implementation. Expect to spend 60 work days for a medium-to-large implementation, with much of the additional time spent in planning. A large business with multiple locations will experience different challenges than a smaller business with one location and only a few users.

Experience has shown that those organizations that use the methods discussed in this section achieve their implementations successfully and in a timely manner. Beyond these two categories, implementations that have extensive data migration and customizations may take more than 60 days.

Tools for project management


The following tables describe tools that you can modify and use for managing your implementation project. For project plans, two versions are provided: one for rapid implementations, and one for measured or full implementations. These tools are available for download at Microsoft Dynamics CRM Planning Tools (http://go.microsoft.com/fwlink/?LinkId=148432).

More information about project management can also be found in the Microsoft Dynamics Sure Step Methodology.



Project planning tools

Tool

Description

Project Plan Rapid (.xls)

An Excel worksheet for creating the implementation schedule for rapid implementations.

Project Plan (.xls)

An Excel worksheet for creating the implementation schedule for measured implementations.

Assessing Implementation Capacity (.doc)

A document that has questions to help you determine whether your organization has sufficient resources for implementing Microsoft Dynamics CRM, or whether a consultant is required.

Estimating Implementation Time (.doc)

A document of guidelines for determining how long an implementation is likely to take.

Project Scope (.doc)

A document that has questions to determine the scope of the project, based on rough estimates of the customization required and the state of your current IT infrastructure.

Rapid Implementation Guidelines (.doc)

A document that contains guidelines for when a rapid implementation is appropriate.

Test Case Template (.doc)

A sample form to use for people testing Microsoft Dynamics CRM before deployment.

Go Live Checklist (.doc)

A checklist for tasks that must be finished before you deploy Microsoft Dynamics CRM.

Server Tracking Form (.doc)

A form for documenting server and network configuration.

Responsibility Checklist (.doc)

A checklist of all areas that need owners, to guarantee that Microsoft Dynamics CRM continues to work well after the implementation.

Project Review Survey (.doc)

An agenda for a project review meeting to be held when Microsoft Dynamics CRM is deployed.

Project status tools

Tool

Description

Project Status (.doc)

A sample project status form that you can use to report on status.

Weekly Summary (.xls)

A sample weekly log sheet.

Change management tools

Tool

Description

Scope Change Log (.doc)

A sample scope change form that you can use to track scope changes.

Scope Change Request Form (.doc)

A sample scope change request form that business managers can use to request scope changes.



1   2   3   4   5   6   7   8   9   ...   19


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©atelim.com 2016
rəhbərliyinə müraciət