New Project Approach

Implementing a new technology project can be a time-consuming and complex task that many customers will be unfamiliar with. With numerous potential pitfalls to contend with, it is vital to work with an experienced partner that has a proven, implementation methodology.

 

Our mission is to become a long-term partner that helps you make the most from your technology investment. We focus on addressing the key needs of the business, mitigating overall risk, reducing the amount of customisations and associated costs. We have a great team of people with years of industry expertise who are able to guide you through the implementation process and deliver value from day 1.

 

With the entire cultural, financial and day-to-day management of the business at stake – it’s important that all possible steps are taken to minimise risk, and make the implementation process as smooth as possible.

Getting Everyone on Board

Before a project gets underway, it’s imperative that the entire organisation “from the top-down” understand the reasons, need and strategy behind a business change project.

 

We have developed a methodology which is flexible, collaborative and allows for clear and consistent communication. The result is that everyone (from both Maginus and the customer project team) feels involved, understands their role of the team and buys into the shared vision. 

Outlining a Clear Set of Goals

The first step is to gauge a clear definition of success. Gaining a clear consensus here is vital – it’s important to gain a collective view of the problems that need to be solved, the outcome and financial implications and justifications behind the project.

 

Having a defined set of goals makes it easier to narrow down the business processes involved…Without a clear vision of success, the end point will become a moving target.

Focus on Business Processes

Throughout the configuration stage, the Maginus team will go through each functional area required by the customer to identify configuration / development requirements.  In 2 week sprints, customers will both test and be trained on each functional area. Our consultants will suggest process changes in-line with best practice and identify potential areas for development. The end result is a list of prioritised development requirements.

 

This phase builds confidence within the customer team as the working system they have is getting closer to their requirements, it gives an early opportunity to identify and prioritise new developments, validate changes and test new configuration.

Rapid Configuration & Testing

When schedules get tight, reducing the number of testing cycles is often the first area that gets cut. At Maginus, we prioritise testing as a key, on-going part of the implementation process.The purpose of testing your ERP system isn’t to see if it works but if the system needs and produces the required output. 

 

In traditional project methodologies, configuration often comes into play within the latter stages of the project. Instead, we opt to provide a working system configured for their business as rapidly as possible. This helps staff to familiarise themselves with the new system and gives us an opportunity to gain valuable feedback early on in the project. 

Customisation & Integration

This phase is where the specification and development work for the customisation is completed. The work is prioritised and completed in 2 week blocks of development which is then given to the customer for testing. Once accepted by the customer, the customisation is made live in the configured system.

This phase gives our customers an opportunity to give feedback on development work much earlier in the process than in many methodologies. The 2 week blocks ensure that, if there are any issues they’re identified early which reduces the amount of time taken to produce customisations.

End-to-End Testing

Throughout the implementation process, testing has been carried out on specific elements and functional areas within the system. The aim of this phase is to test the whole system from end-to-end. Because customer testing has been taking place from phase 2 there generally aren’t any major surprises.

 

This phase gives customers the opportunity to see the whole system from end-to-end and gives them confidence that the deployment with be a success.

Deploy in one "Big Bang" or a Phased Approach

There isn’t any right or wrong option for deployment. Following discussions of the benefits of different options, some customers choose a ‘big bang’ deployment, some a phased launch.

  • What our Customers Like About the Maginus Implementation Model:

  • The Team Approach

    Our customers often say they feel comfortable with the cultural fit between our companies.  Whilst this is difficult to quantify it’s important for us all to work well together to ensure a successful implementation and continuing working partnership

  • Clear Project Definition

    The clear documentation of the breadth and vision of the Project helps to ensure that everyone understands what they need to do and the impact it has on the overall project

  • The Flexible Approach

    The iterative nature of the process gives customers early sight of configuration changes and developments which reduces re-work, builds confidence and ultimately reduces costs

  • User Involvement

    End-users get early access to the system, so they feel that their opinions are valued and they are an integral part of the project. 

10 Mistakes to Avoid When Implementing an Enterprise Solution

Download this report to find out: 7 root causes for a failed ERP implementation & 20+ steps you can take to mitigate the risks.

Download: 10 Mistakes to Avoid When Implementing an Enterprise Solution