Microsoft Dynamics NAV

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

Browse by Tags

Related Posts

  • Blog Post: 10 reasons that make design absolutely necessary

    Anonymous Anonymous
    Design is one of a kind. Other phases in Sure Step are understood and accepted as good and necessary. But design, do we really do that? Is it really necessary? Who’s going to pay for it? Does the customer really need all those documents? Instead of writing documents, you could have it developed in the...
    on 13 Sep 2010

  • Blog Post: Setup-dependent requirements

    Anonymous Anonymous
    While designing a custom functionality for a customer, there was an issue with posting groups: the way the custom functionality was designed would result in value entries being always posted to a single posting group, resulting in inventory balances always going to the same inventory account. When I...
    on 8 Sep 2010

  • 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: 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