Ana səhifə

Microsoft Dynamics crm planning Guide


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

Implementation overview


This section expands on the tasks that are required for a successful Microsoft Dynamics CRM implementation.

Planning


Planning is the critical phase that starts with understanding how your organization plans to use Microsoft Dynamics CRM. This includes the following:

  • Developing commitment from key managers.

  • Defining the implementation project team.

  • Deciding whether to hire consultants or to use your own staff.

  • Defining the scope of the project.

  • Writing an implementation plan.

  • Making sure key managers in your organization understand and support the plan.

For a detailed task list, see Planning Tasks in this guide.

Development


There are three tasks in this group:

  1. Installing and configuring the hardware and software

  2. Using the data that is collected in planning to configure Microsoft Dynamics CRM

  3. Using the data that is collected in planning to customize Microsoft Dynamics CRM, if it is necessary

Depending on the options selected for your organization, this may also include the following:

  • Migrating data from source applications

  • Setting up a test or pilot environment

  • Integrating Microsoft Dynamics CRM with an Enterprise Resource Planning (ERP) system, such as Microsoft Dynamics GP

For a detailed task list, see "Development tasks" in this guide.

Deployment


This starts with user training, followed by deployment to the production environment. For a detailed task list, see “Deployment tasks” in this guide.

Post-deployment: operating and maintaining


As your business evolves, post-deployment maintenance makes sure that Microsoft Dynamics CRM continues to support your business practices.

For a detailed task list, see "Post-Deployment Tasks" in this guide.


Planning tasks


This section describes the planning tasks that are essential to a successful Microsoft Dynamics CRM implementation. A good implementation plan includes definitions of the general goals you want to achieve, the system requirements that you have to meet, and the timeframe to complete the plan. Business requirements and processes are also mapped to the application.

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.



Identifying the implementation team


The responsibility for a successful Microsoft Dynamics CRM implementation should be shared by several people and organizations. Some of these include your software vendor, consultant, or other value-added partner, and the people in your own organization who are needed to participate in your implementation team. These people will implement Microsoft Dynamics CRM for your business.

The responsibilities of an implementation team include the following:



  • Develop an installation strategy.

  • Determine who will perform the various tasks.

  • Create an implementation schedule.

  • Define a progress-reporting plan.

Members of the implementation team should include people with organizational and planning skills, a comprehensive knowledge of the day-to-day business operations of your organization, and knowledge of Microsoft Dynamics CRM. The team should also include the system administrators whose technical experience should include Microsoft Windows security, client/server networks, database administration, and Web technology.

The number of people involved in implementing Microsoft Dynamics CRM depends on the size of your organization. To avoid task and time-responsibility conflicts, make sure that members of the implementation team are either full-time resources or can schedule implementation-related tasks as a priority, especially if deployment is to a large number of users. Team members and their managers must understand and accept the commitment required.

Each member of the team must have a well-defined role and set of responsibilities. These roles include the following:


  • Business owners and managers

Business owners and managers provide the leadership necessary for success, and guide decisions about the way Microsoft Dynamics CRM is deployed. Although they do not have to understand the details of installation and configuration, they must be aware of the system configuration and maintenance requirements.

  • Executive sponsor

In small organizations, this role may be the same as the business owner or managers. In larger organizations, this person provides the link between the project manager and upper management. This person must understand the details of the installation and configuration, understand the schedule, and work with outside vendors.

  • Implementation project manager

The project manager is the person who directs the work and makes things happen. This person must understand the details of the installation and configuration, understand the schedule, know the other team members and their contributions, and work with outside vendors.

  • System administrator/database administrator

The system administrator sets up and configures hardware, installs operating systems and supporting software, and installs the Microsoft Dynamics CRM software. In smaller organizations, a Microsoft Partner may handle these tasks.

The database administrator maintains and backs up business data. Depending on the size of your organization, the system administrator or another person (such as someone in operations) might be assigned the database administrator role.



  • Operations personnel

Your operations personnel are responsible for maintaining the system on a day-to-day basis. This ensures good system health and failure recovery. In smaller organizations, these roles may be shared with the system or database administrator.

Creating a schedule


Creating a schedule is one of the important jobs of the implementation team. A schedule should list the steps that you must follow to implement and deploy Microsoft Dynamics CRM, the time requirements for each step, and who is responsible to make sure that the tasks are completed. It may also determine any risks and dependencies. For example, the following list identifies the main tasks associated with deploying (deployment tasks) Microsoft Dynamics CRM:

  1. Hardware and software

  1. Determine requirements and specifications

  2. Obtain, install, and configure

  1. Install Microsoft Dynamics CRM

  2. Customize the Microsoft Dynamics CRM application

  1. Analyze the business process

  2. Determine customization requirements and specifications

  3. Approve and freeze customization specifications

  4. Develop customization

  5. Review customization

  6. Test the system

  7. Get pilot group to use product

  8. Finish customization

  9. Process audit

  1. Training

  1. Schedule administrator training

  2. Schedule user training

  1. Deployment

  1. Deploy Microsoft Dynamics CRM to the organization

  2. Perform the import of legacy data (if importing)

  3. Validate legacy data after installation

  1. Post-deployment follow-up

  1. Hold a post-implementation audit or review (after about 3 months)



Analyzing your business processes


You must have a thorough understanding of how your sales, service, service scheduling, marketing processes, and existing data collection systems work. In addition, you have to have a vision of how you want these processes to work. The best way to analyze your business processes is to use members of your organization who know your business processes. Usually, the experts are the department heads or the people they appoint to do the tasks as part of their job. A successful implementation ultimately depends on its usability and the willingness of users to use it. Therefore, it is very important to engage these experts early in the process.

The tasks to analyze your business processes are as follows:



  • Learn what processes are in place. For example, how are accounts created and managed, how are orders recorded, how is inventory tracked, and how are customers billed?

  • Learn what users think about the current system. For example, is it effective, is it time-consuming, and are there processes that can be streamlined or dropped completely?

  • Learn what expectations users have of Microsoft Dynamics CRM. For example, are they excited about how to use an automated CRM system, or do they have reservations and questions?

  • Examine the current processes and find out whether they stand up to the scrutiny of smart business practices or whether they continue to exist because no one wants change.

  • Learn the features of the Microsoft Dynamics CRM product and how they relate to current organization processes and procedures.

  • Determine what reports are necessary and part of your current business process.

  • Determine the components and features that will be implemented and deployed first and when additional components and features will be added later.

  • Incorporate the processes into Microsoft Dynamics CRM. Determine whether the processes can be re-created as they currently are or whether changes must be made to incorporate the application and use its new functionality.



Defining tasks for development, deployment, and post-deployment


Tasks for development, deployment, and post-deployment include the following:

  • Define a testing or pilot plan.

  • Define deployment support requirements.

  • Deliver an implementation scope document.

  • Prepare a gap analysis document.

  • Prepare an initial UI design guide.

  • Prepare and deliver report design changes.

  • If data migration is required, prepare an initial data migration plan.

  • If integration is required, prepare an initial integration plan.



Identifying optional components


Determine which optional components will be included in your Microsoft Dynamics CRM system:



Identifying hardware and software requirements


An inventory of your current hardware and software will help determine what you already have that can be used as part of your Microsoft Dynamics CRM implementation, and what must be purchased before implementation can continue.

If you have to purchase additional hardware or software, verify availability and delivery dates. These dates, and the time that is required for installation, are external dependencies that affect the schedule. For more information about the hardware and software requirements of the Microsoft Dynamics CRM components, see "System Requirements and Required Components" in this document.


Determining data import requirements


The primary method to put existing data into Microsoft Dynamics CRM is by using the Data Migration Manager. The Data Migration Manager includes tools for importing and migrating data for most entities.

Determining customization needs


For each record type, you must determine:

  • Field-level changes, such as labels to change, fields to add, and drop-down list values to modify.

  • Form-level changes, such as incorporating new fields, removing unused fields, and reordering fields to match business processes.

  • View-level changes, such as incorporating new fields, removing unused fields, and reordering fields to match business processes.

  • Reports that have to change to incorporate field-level changes.

  • New reports that are needed.



Identifying training requirements


One of the keys to a successful implementation is to provide training and support for all users to make sure that everyone can use the system correctly. All users will need training on the general use of Microsoft Dynamics CRM, and on your business processes. An effective method is to schedule hands-on training immediately before organization-wide deployment. In this manner, users will be able to put what they have learned into practice.

The training plan should include training for several groups of people:



  • Business managers

Training should include how to manage users and their access privileges, make changes to department structure, generate reports, review and analyze data, and use any other system features that are relevant to their job responsibilities.

Sales managers should learn how to track sales quotas.

Service manager should learn how to track resources, manage queues, and manage the service subject list.

Marketing manager training should include how to manage lists and campaigns.



Training should include how to create and manage accounts and activities by using the Web and Microsoft Dynamics CRM for Outlook, import lists, manage direct e-mail, create e-mail templates, and generate reports.

  • Service representatives

Training should include how to manage cases and knowledge base articles, and how to use queues.

  • Service schedulers

Training should include how to define resources.

  • Marketing staff

Training should include how to define resources.

  • Other users (such as the accounting department staff)

Training should include how to manage contracts, process commissions, view and access data, and other job responsibilities.

  • Information technology staff

Training should include how to configure Microsoft Dynamics CRM, perform backups and other data maintenance tasks, make changes to organizational structure and business policies, customize drop-down lists, provide support to users, create templates, and create workflow rules.

In addition to knowing the Microsoft Dynamics CRM product, the technology staff may need experience with the following:



  • The Windows operating system

  • Active Directory

  • Internet Information Services (IIS)

  • Microsoft SQL Server 2005. This includes Reporting Services.

  • Microsoft Exchange Server 2003, Microsoft Exchange Server 2007, or POP3-compliant e-mail server (Required if implementing Microsoft Dynamics CRM E-mail Router)

  • Microsoft Office Outlook (Required if implementing Microsoft Dynamics CRM for Outlook)

Training resources

Microsoft Dynamics CRM includes several tools to help users train while on the job:



  • Help has step-by-step instructions on how to do specific tasks.

  • The Microsoft Dynamics CRM Resource Center is an integrated part of the application and provides rich content and links to valuable resources. Much of the content in the Resource Center is created by experts in the Microsoft Dynamics CRM community.

  • Tool Tips are embedded in the interface and have brief descriptions of the various components on the screen. These tips help users learn about the product interface.



Defining ongoing support and maintenance needs


Although users may be given training and job aids to help them become accustomed to a new product, if they do not use the product, the organization will not realize a return on its investment. A successful implementation plan should include change-management efforts and post-deployment follow-up to determine whether your work force is using Microsoft Dynamics CRM.

Development tasks can include any of the following activities, depending on your implementation plan.



  • Communicate progress, and coordinate timing of deployment.

  • Provide required configuration information, such as your organizational structure, and the security role that you want each employee to have.

  • Answer questions from the project manager and the installer. Questions will occur as they start configuring and customizing, regardless of how thorough your planning was.

  • Establish a small group of employees to use Microsoft Dynamics CRM first, who can help determine areas that need changes and then help other users. This group should perform the common activities that their jobs require, such as creating accounts, reviewing data, and sending e-mail. Notice their actions to find out what difficulties may exist and address these issues during training.

  • Install Microsoft Dynamics CRM. If it makes sense for your organization, implement a pilot or test installation.

  • Import or migrate your existing customer data.

  • Configure Microsoft Dynamics CRM.

  • If it is necessary, integrate Microsoft Dynamics CRM into existing systems, such as Microsoft Dynamics GP or Microsoft Dynamics AX

  • Microsoft Dynamics AX.

  • Test the installation.

  • Customize the application and the reporting features.

  • Test the customizations.



Deployment tasks


To deploy Microsoft Dynamics CRM, the following tasks must be performed.

  • Verify that all users are trained, and coordinate the actual date that everyone will start to use Microsoft Dynamics CRM.

  • Turn off old systems, and start using Microsoft Dynamics CRM. You may have to make old systems available in a read-only mode.

  • Verify that you understand what is expected from you for using and managing Microsoft Dynamics CRM, and that your employees know what is expected of them.

  • Train users.

  • Watch users as they start to use Microsoft Dynamics CRM so that you can determine and correct process issues.

  • Use reports to track adoption and usage so that you can remove obstacles for your employees.

  • Verify that all users are set up in Microsoft Dynamics CRM, assigned the needed security roles, and that they have access to Microsoft Dynamics CRM.

Because the Microsoft Dynamics CRM user interface is browser-based, no special software installations are needed on networked desktop computers. However, for client computers that will use Microsoft Dynamics CRM by using Microsoft Office Outlook, installation of Microsoft Dynamics CRM for Outlook is required.

  • Watch users as they start to use Microsoft Dynamics CRM to see whether additional customizations are necessary.



Post-deployment tasks


Deploying a CRM system may involve significant change in process and daily tasks for members of the organization. A successful deployment guarantees that issues and areas of resistance related to this change are identified and addressed through training, coaching, and other change-management practices. As your company uses Microsoft Dynamics CRM, you will likely determine additional areas that need changes in order to match your changing business processes.

Department managers must be available to set an example and support the implementation, both by talking about it and by using it. Executive managers must demonstrate an ongoing commitment to show that using Microsoft Dynamics CRM is a permanent change.


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