Project Delivery

Project Delivery is part of the S1 momentum methodology and covers the traditional project lifecycle for implementing ERP systems into a business. Each phase of the lifecycle contain specific themes and key tasks that enable the system to be successfully implemented into the business whilst maximising the benefits and minimising the risk of project failure.

The key differentiator to note from the S1 Momentum project delivery approach is the grouping of Initiate-Define-Design and Build-Prepare-Transfer with clear Quality Assurance checkpoints. Too many projects attempt to crunch the project lifecycle and end up running too many of the project phases together creating a less then desirable outcome and even risking project failure.

S1 Momentum runs a discipline approach around the various phases and the need for quality checks during the project. The 7 key phases of the lifecycle are:

Initiate

The Initiate phase mobilises the project with a common understanding of the project, a well prepared project team, and an overall framework of plans. The various project management processes are defined and put in place as a foundation for moving forward. The key outcome of the Initiate phase is the project charter, a living project document that spells out how the project will be managed.

Define

The Define phase analyses the current business and IT strategies against the aims of the project to ensure the business and the project are properly aligned. The core business processes to be impacted by the project are also identified and discussed with the aim of re-engineering said processes where appropriate. The key outcome from the Define phase is a strategy analysis that validates the commitment to the project, and provides proper foundation for the project around business alignment, KPIs etc.

Design

The Design phase targets the business process and redesigns them to function more efficiently in accordance with the objectives and KPIs of the business. All the processes are mapped and documented to reflect conceptually how the solution will look when the system is implemented. This enables the relevant reports, forms, interfaces and data to be identified and assessed. The key outcome from the Design phase is the conceptual design that enables the key business stakeholders to visualise how the solution will fit into the business.

Build

The Build phase prototypes the conceptual design within the standard system functionality whilst the associated reports, interfaces, and conversion programs are developed. This is an iterative process that looks to avoid customising the application and the expensive maintenance implications that go with developing software in house. The key outcome from the Build phase is a conference room pilot whereby the key stakeholders in the business can see a working draft solution.

Prepare

The Prepare phase takes the working draft solution for system integration testing against the key business scenarios discussed during the Define and Design phases. The aim of testing is to ensure there is a working solution that not only covers the business processes, but also any reporting, interface and data conversion needs. The key outcome from the Prepare phase is signed off acceptance that the system clearly meets the requirements of the business.

Transfer

The Transfer phase is the go-live phase. It runs through a series of activities that will make sure end users are trained whilst closing down the old system to cut over to the new system. The aim of going live is to minimise any disruption to the business whilst maximising the uptake on the new system by the business. The key outcome from the Transfer phase is a new live system with end users able to carry out their day to day activities in an effective and efficient manner.

Sustain

The Sustain phase looks to consolidate the implementation of the new system by providing additional support during the first business cycle following go-live. This may include catch up training for those who missed out during the cut over, fine tuning of some of the system functionality as well as reports and interfaces, or updates to business process documentation. The key outcome from the Sustain phase is a system that is fully operational and, where appropriate, self sustainable. 

< back to S1 momentum