Working with Epimatic

We pride ourselves on being flexible – flexible in how we treat our employees, partners and customers. This is important as so many companies that are looking to Microsoft Dynamics NAV to help them are coming at it from very different perspectives and with a varying background of existing infrastructure. As NAV is such a flexible product and offers so many customization options and capabilities it’s important that we work with our customers to deliver them the right solution they need in a way that is right for them.

We have experience working within all of these methodologies.

Waterfall (Typical Software Development Life Cycle)

This approach requires a lot of up front analysis and the steps (in order) are: Gather Requirements, Document the Design, Implement the Design, Test and Verify, and finally Maintain and Support the application. In order to successfully implement an application using this approach a very thorough requirements gathering and design phase is needed.

Sure Step Methodology

Microsoft further developed the waterfall method and defined the key steps, key documents, milestones and who is responsible for key deliverables. The Sure Step methodology provides a set of templates which can be used during the different phases of the implementation. For more information look here.

Rapid Implementation Methodology

The Rapid Implementation Methodology is commonly employed through the use of the RIM Toolkit that is released by Microsoft. This set of data migration and setup tools is highlighted towards the end of the Sure Step process and is designed to help customers get up and running with a base configuration of Microsoft Dynamics NAV using their own data and an industry specific configuration in a short period of time.

Agile Development

We have worked on various projects where a SCRUM or Agile Development methodology has been used. This allows for very rapid application development with a minimum of up front documentation. These projects may require iterative steps to review development and slowly add functionality. This can help reduce the risk of delivering customizations and functionality which does not match with a customer’s expectation.