Typical Microsoft Dynamics NAV Implementation Blunders

May 20 2008

Sometimes a failed implementation threatens to scare off prospective customers, especially if the local market is small, the customer involved large, and the needs especially vertical. In these situations, everybody will know that a project has failed the moment it does, and the solution, be it Microsoft Dynamics NAV or any other for that matter, will be immediately labeled as “bad.”

About Vjekoslav Babic

Vjekoslav Babić is an independent Microsoft Dynamics NAV consultant, trainer, author and blogger, with 10 years of experience in NAV and 16 years of experience in IT.

As a solutions architect and a project manager with a leading Microsoft Dynamics President's Club service provider company, as a Microsoft Dynamics NAV consultant with Microsoft Services, and as an independent consultant, he has been working on Microsoft Dynamics NAV implementations ranging from tiny one-man-bands to international mega-corporations, delivering services and trainings all over the world.

In 2008, Vjekoslav co-authored the acclaimed book "Implementing Microsoft Dynamics NAV 2009". Vjekoslav runs an active blog about NAV implementation, project management and development best practices, acts as a columnist and editorial advisory board member at MSDynamicsWorld.com, and as a columnist in a number of other web or printed periodicals in Croatia and worldwide. Vjekoslav is also a frequent speaker at Microsoft or Microsoft Dynamics conferences.

Since spring 2010, Vjekoslav has been awarded the prestigious Microsoft Most Valuable Professional (MVP) award for Microsoft Dynamics NAV.

More about Vjekoslav Babic

Comments

sonia saxena's picture

I want to create multi branch management in Single company