Hi guys,
I'm a very new toward Dynamics NAV. Hope can get some advise on this.
Based on your past experience, how long does your NAV implementation take? (from scratch until it complete)
Because I want to set a timeline for my NAV project.
Thanks.
*This post is locked for comments
Project timeline may depend on many parameters, Such as modules going to implement, complexity of the each module, how the each module integrate with each other, how the application setup been done, how the change management is been handled, how the customizations been implemented to the system, report complexity.. etc.
Addition to above reasons there are lot of dependencies with the customer. Such as how the customer provide the process details, is the customer willing to change his current process to adopt the best practices, or do they need to implement their current process as it is in the system, is the customer has the exact balances for the masters, is the chart of account is accurate, how much time required to prepare the data. (list goes on)..
Apart from above there are many parameters that will affect the project time line. I have involved in some projects which took only about 3 weeks to implement and some projects took more than 2+ years. If I take the average, many NAV projects (not very complex and without manufacturing) can be finish within 6-10 months time period. If the project is only with finance module then it can be able to complete within 3-6 months.
It also depends quite a lot on the customer commitment :-). I've seen many projects that had challenges due to lack of customer participation - not providing detailed requirements, not reading documents, not testing enough. Moreover, in many cases the key users from customer side are identified incorrectly: top managers or leaders of the department are not always (or even practically never) good key users. They could have a good understanding of how the things should go in general, but in fact there might be plenty of non-standard situations and deviations from normal processes that only low-level people know about; not knowing this might ruin your implementation.
Thanks for the advice, Mahesh
Hi Alexander, thanks for your sharing :)
Hi,
As mentioned by Alexander, it depends on a lot of parameters, which includes business requirements, the Customizations (if any) in the functionality, document report changes etc., and also depends on the capability of the implementation team too.
It depends on the scale and modules, and the level of customization needed. Also, local requirements to financial module are very important. If your country has specific localization for accounting and taxation, it can affect the project scope and timelines. Normal project requires requirement analysis, preparation of technical design, setup and development phase, key user trainings, testing, user trainings, go-live and after go-live support.
I had experience of few 3 month NAV projects, which were pretty standard. I also had experience of 3 years projects with many additional phases and change management procedures.
Normally, users (especially accountants) start to feel comfortable after 1 year of go-live, when all the accounting procedures (including annual ones) are done at least one time. I would estimate an average NAV project around 8 months for Russia and post-Soviet countries.
Share
Report
All responses (
Answers (
23,116
