Let us start our discussion on what methodology is by defining the Microsoft Dynamics NAV implementation process. Generally, it is close cooperation between a customer and an implementing partner, which is aimed at starting Microsoft Dynamics NAV in the customer’s organization. No matter what the scope of implementation is, and what specific solutions are implemented, three parties are always involved, namely: the Client (with its specific requirements), Partner and the Microsoft Dynamics NAV system.

In this system, methodology is an element which combines the three parties. For example, it enables the client and the partner to exchange information by such means and at such a level in order to transform this information into system, setup and work schedule modifications.

Specifically, methodology determines and even imposes the terminology to be used in the course of implementation. Methodology is also assumed to specify subsequent steps in implementation as well as guidelines to be used in predicted situations and to be applied when something unpredictable happens.

Methodology also determines the structure of the implementation team, scope of responsibilities and responsibilities of individual team members. It proves to be extremely important when implementation involves several company departments at the same time. In such a case all bottlenecks and events and decisions to be made have to be handled by more staff members.

Ideally, the project is completed on time and all requirements are met within the allocated budget. However, attempts to achieve this ideal are rarely successful, unfortunately. Therefore, to make the most of the guidelines related to schedule, requirements and budget, it is important to monitor the implementation project; both for timing, quality and budget. For all of this, methodology provides all required procedures and tools.

What does methodology mean physically? Generally, it is a set of written guidelines, documentation templates and tools such as On Target Modeller, which can be used for business process modeling in a graphic form using UML.
It is also worth remembering that methodology means not only documentation and tools, but also – expertise and practice. This is why we train implementation team members on specific issues before implementation is started. Mostly, we receive positive feedback from our customers who appreciate this approach to implementation.

Examining methodology, you may have an impression that the whole additional work due to compiling documentation, holding meetings etc. is firstly, needed exclusively for large implementation projects and secondly, generates high costs. The practice, however, shows that methodology can be applied in implementation projects of any size. Moreover, we attempt to apply some methodology elements for smaller implementation projects which are limited to developing extensions or functional modifications for existing systems.

What makes it work? Methodology does not imply the obligation to use all procedures, documents and tools. The extent to which implementation is documented and monitored depends on the implementation complexity level and size, as well as customer requirements such as the one to provide detailed modification projects. As the Microsoft Dynamics NAV development environment is extremely efficient, developing modifications or new, simple modules is simplified, and thus precise customer instructions on requirements are sufficient to start programming. It takes less time to just discuss possible ambiguities with the customer than to plan the project, obtain the acceptance for it and record all modifications made in the course of the project and etc.
Obviously, some methodology elements cannot be ignored.

Main stages of fulfilling the Microsoft Dynamics NAV project
Assuming that there are two points – beginning and end of implementation, the Microsoft Dynamics NAV implementation methodology assumes that there are 5 stages of project fulfillment.

The first stage involves analyzing customer requirements for the projected system. In the second stage, these requirements are verified and the concept on how the project is to be fulfilled is developed.
The third stage is planned as a programming and testing stage. Modifications, however are developed only if specific requirements have to be met. Implementation is the stage before the last, and it involves final training sessions and preparing the system for import of historical data.
The system is started, which is followed by the system maintenance stage. Parallelly with all implementation stages, training is delivered, project plans are updated and information is communicated between project participants.

Practical effects resulting from the methodology

Applying mutually agreed and accepted methodology in implementation projects allows us to diagnose early whether requirements are feasible. This means also the ability to allocate budget accurately and specify the duration of implementation. The figure above shows that the duration of implementation becomes shorter contrary to what might be expected. This is due to the fact that badly managed implementation projects require long term support after the system is started. Applying the methodology is also positively evaluated by staff involved in the implementation. The tasks and responsibilities they are assigned are clearly defined and predictable. The practice also shows that using the methodology does not result in a substantial increase of the implementation budget, and the budget can be precisely controlled as all deadlines are met.