Microsoft Dynamics NAV

Home » Microsoft Dynamics NAV » Navigate Into Success » All Tags » Best practices » ERP

Browse by Tags

Related Posts

  • Blog Post: 5th rule of agile ERP: interface where possible

    Anonymous Anonymous
    One of the biggest absurdities about ERP systems springs from the very word we use so often when describing ERP: integrated . ERP is an integrated system: it integrates all data and processes into a single application. Different modules look over different aspects of data and processes, but a change...
    on 22 Mar 2009

  • Blog Post: 4th rule of agile ERP: avoid heavy customizations

    Anonymous Anonymous
    You can’t avoid customizations. Vanilla ERP is a great first step, and a valuable tool for establishing common language between the customer and the consultant. But in the long run? Probably not. Pristine uncustomized ERP won’t be sufficient, because of the gaps between your way and ERP’s way. Sooner...
    on 19 Mar 2009

  • Blog Post: 3rd rule of agile ERP: focus on value

    Anonymous Anonymous
    - “We need a report which groups our sales by product components.” - “And we need it broken down by cost centers.” - “And it must show comparison with last month, quarter and year, and with budget and forecast, with indexes and trends. In linear regression.” - “And it must let you choose if it...
    on 18 Mar 2009

  • Blog Post: 2nd rule of agile ERP: deploy gradually

    Anonymous Anonymous
    How do you eat an elephant? One bite at a time. Swallowing it all at once might be tempting as it has all the potential you need to get into the next edition of Guinness World Records . Likewise, trying it with an ERP implementation has all the potential you need to get into to the next edition of Chaos...
    on 17 Mar 2009

  • Blog Post: 1st rule of agile ERP: deploy vanilla ERP

    Anonymous Anonymous
    “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” That’s the very first principle of the Agile Manifesto . The problem with ERP is that the first deliveries are all but early: they typically occur only after about twenty months . Twenty...
    on 16 Mar 2009

  • Blog Post: 5 steps to implement ERP the Agile way

    Anonymous Anonymous
    In my previous post I’ve (what, again?) shared some statistics about success and failure rates of software projects in general and ERP projects specifically. It seems that ERP projects fare somewhat worse than generic software projects, which I stated might have a lot to do with how requirements are...
    on 15 Mar 2009

  • Blog Post: Sure Step in action: Architecture Assessment

    Anonymous Anonymous
    Implementing a new Microsoft Dynamics solution doesn’t merely introduce a new piece of software into your environment. Yes, the software is an important part, you need to deploy it successfully, configure it as necessary, probably even customize it and change the business logic under the hood. One...
    on 28 Jan 2009

  • Blog Post: Starting it from scratch – do you dare?

    Anonymous Anonymous
    (Three compelling reasons to reshape your business processes, not your software) Has your computer ever crashed while you were doing something important, causing you to lose all your work? A natural first reaction to this situation is frustration: your work is gone, your effort went in vain, you’ll...
    on 18 Jan 2009

  • Blog Post: Default database approach

    Anonymous Anonymous
    Last Friday, while enjoying a not-at-all healthy Salisbury steak with cheese, I had an interesting discussion with a partner: should NAV consultancies create default databases? A default database (in this context) is a packaged solution built upon standard Microsoft Dynamics NAV, where a consultancy...
    on 11 Nov 2008

  • Blog Post: Diagnostic Phase – a signpost for implementation

    Anonymous Anonymous
    Each phase of Microsoft Dynamics Sure Step methodology is equally important in an implementation project. You could argue that analysis is the most important, or that design is the most important, or that operation is less important. I’ll paraphrase Scott Adams here and ask: how one phase can be...
    on 19 Sep 2008

  • Blog Post: “Our old software” syndrome

    Anonymous Anonymous
    A few days back, while prototyping a new solution for a customer, one of the key users said: “But in our old software it didn’t work like that.” I was about to try to explain why the change, but then the user’s boss said: - We aren’t implementing a new solution so that...
    on 1 Aug 2008

  • Blog Post: Standard enemy

    Anonymous Anonymous
    The biggest jeopardies often lurk where we least expect them. When implementing an ERP system such as Microsoft Dynamics NAV, what should be one of our best allies, turns out to be our mortal enemy. It has a simple name: The Standard. Standard processes, standard functionality, standard documents, standard...
    on 14 May 2008

  • Blog Post: Business case - do I eat it or?

    Anonymous Anonymous
    It’s a well known fact that IT projects fail every so often. Standish Group has been researching the success and failure factors of IT projects for a decade and a half, and they publish their results in their CHAOS report every two years or so. According to their 2006 report, only about 35% of...
    on 8 May 2008