Chapter 4. Implementation Process – Partner's Perspective

In this chapter, we will learn about the Microsoft Dynamics NAV 2018 and Microsoft Dynamics 365 Business Central implementation process from the perspective of a reseller. This chapter will explain the meaning of implementation and show that there are different methodologies that you can apply.

In an implementation process, several actors may get involved, each one playing their own role. We will learn what kind of roles can be found in a Microsoft Dynamics NAV or Microsoft Dynamics 365 Business Central implementation and the job that can be expected from each role.

We will also see that the implementation process can be broken down into phases, and we will learn about the tasks included in each phase.

The main topics discussed in this chapter are as follows:

• Defining what an implementation is
• Using methodology
• Roles involved in an implementation project
• The phases of the project
• Considerations for an implementation of...

What is an implementation?

What is an implementation? To implement means performing a series of steps that usually includes the following:

• Requirements analysis
• Project scope analysis
• Customizations
• Integrations
• Key user training
• Product delivery

These steps are often supervised by a project manager who uses different project management methodologies. Through the plan-do-check-act (PDCA) steps typical of project management (the Deming Cycle), it is possible to keep the project under control.

To implement a system successfully, a large number of interrelated tasks need to be carried out in an appropriate sequence. That is what needs to be done in a Microsoft Dynamics NAV or Microsoft Dynamics 365 Business Central implementation process to get the software (Microsoft Dynamics NAV, Microsoft Dynamics 365 Business Central, be it on-premise or SaaS) to operate properly in its environment (the company that will use these programs as their business management software).

An advantage of Microsoft Dynamics...

Methodology

Each implementation of Microsoft Dynamics NAV is completely different from the others. The reason is because each company, no matter how similar the industry, is run differently. The company that is going to use the ERP software (usually called the customer) is different, the requirements are different, the scope is different, and even the team implementing it might be different. This brings a lot of uncertainty to the process and is the main reason why methodology has to be used.

Implementing Microsoft Dynamics NAV is considered as working in a project environment. By definition, a project is a temporary endeavor undertaken to meet unique goals. The company implementing Microsoft Dynamics NAV (usually called the consultant) is probably used to this kind of environment. On the other hand, the customer is probably used to working in an operational environment, where the same processes are repeated over and over. For the customer, implementing a new ERP system is like running in...

Roles

Implementing an ERP solution, such as Microsoft Dynamics NAV 2018 or Microsoft Dynamics 365 Business Central, in a company is not a trivial task. A lot of things have to be taken into account and a lot of things have to be done. That's why a lot of people have to get involved in the project, both in the company implementing Microsoft Dynamics NAV, that is, the partner, and in the company that will use Microsoft Dynamics NAV as their management software, that is, the customer.

Everyone will have a different and well-defined role in the project. In this section, we will try to explain who should get involved in the project and the tasks that they will be performing.

In the partner team, the following roles exist:

• Salesperson
• Project manager
• Business consultant
• Analyst

• Developer
• Implementer

In the customer team, we find the following roles:

• Project manager
• Key users
• End users

Note that one person can have multiple roles. It's not uncommon for a Microsoft Dynamics NAV partner to have one person that...

Phases

The following section of this chapter will describe each phase in a Microsoft Dynamics NAV implementation, and the tasks each phase includes. In a waterfall environment, you can do one thing after another. In an agile environment, don't forget to loop through all of the phases, especially those of getting the project requirements, analysis, development, and part of the task from the deployment phase.

It's especially important to define how information will flow through all the phases to ensure that important information does not get lost.

Presales

This is the first contact between the partner and the customer—the big lines on which the project will be drawn.

This phase is usually executed by the sales or marketing teams, with the help of a business consultant. Many companies think that at this stage, the project hasn't started yet, so they don't think that this job is part of the project. But it actually plays a very important role.

Selling a project like a Microsoft Dynamics NAV implementation...

Dynamics 365 Business Central implementation considerations

It is possible to use the same tools discussed here for Microsoft Dynamics 365 Business Central as well. The project's effort could be different if it is a new project, or a migration project from old versions of Microsoft Dynamics NAV.

Remember that on-premise is different from SaaS, in the case of a new project, it is important to immediately explain that, in the cloud, there are pros and cons. The cons are some limitations considering the on-premise Business Central version, sometimes it is better to use what is already there, automatic updates are an excellent point in favor of providing added value. In the case of upgrades and use of the Web client only, it is necessary to understand whether there could be limitations before users accept the new cloud-based solution.

Development of a Microsoft Dynamics 365 Business Central solution should also consider the dependencies problem. You should avoid monolithic extension and should...

Summary

In this chapter, we saw that an implementation is a process that gets software operating properly in a company. To do so, we need to use a methodology that will take us from the beginning to the end of the project, not only on the technical part of the project, but also regarding other aspects, such as billing the project, effort estimation, planning, and communication.

We saw different methodological approaches, such as the waterfall approach and the agile approach (with Scrum), and how they are addressed in Microsoft Dynamics Sure Step.

We also saw the phases and the activities included in typical Microsoft Dynamics NAV and Microsoft Dynamics 365 Business Central implementation projects.

In the next chapter, we will learn some tips about the implementation process on the customer's side.