At Maginus we have a tried and tested methodology to ensure that all system developments meet our customers’ requirements, are technically sound and future proofed whether they’re developments as part of an implementation project or ongoing ‘business as usual’.
The process is basically the same whether it’s a relatively small development to handle a new business requirement or whether it’s part of a full implementation project.
Phase 1 – Gathering Requirements
Before a decision is made to develop new software, our experienced staff spend time with the customer to understand their goals and consider if this can be achieved by changing the business process to work within best practice within the standard system. Inevitably, there are times when this can’t be achieved and new software development is required.
When this has been identified the Maginus team work with the customer to develop a ‘User Story’ rather than the traditional lengthy specifications document.
Phase 2 – Design & Development
The work is prioritised and developed in short sprints where the customer will see the development at regular intervals in ‘show & tell’ sessions. This phase gives our customers an opportunity to see the software early in the development process so that any issues can be recognised early which allows much quicker issue resolution.
Phase 3 – Customer Acceptance & Go-Live
When the development has been completed and tested by Maginus staff, it passes to User Acceptance Testing and then live into the customer system.