Project Planning Project Kickoff Project Management Portal Customer Environment Project Management Plan Project Plan Staffing Plan
Working Sessions Current State and Future State Assessment Gap/Fit Analysis Business Process Analysis (BPA)
Configuration Specifications Software Setup Data Integrations Data Conversion Plan System Runbook
Test Cases and Scenarios System Test Plan Client Validation Issue Review and Resolution Customer Operational Guidebook
Training Cycle Testing Issue Resolution Data Conversion System Live Transition to Customer Support
This first phase begins during the sales process and then continues post-sale.
Involves configurations for the new system, defining roles and documenting standard procedures.
The purpose of the Development phase is to prepare the entire system for going live.
Fine-tuning the configuration to the system's functionality aligning with the set requirements from the business
Prior to going live, the final data will be loaded and validated.
Once the ERP system has gone live, the purpose of the project team will shift.
Our implementation approach is combined with our knowledge of business operations gained from our previous engagements. Improved results occur when efforts are made to provide hands-on opportunities for the organization to review and confirm business process areas. It is important the organization develop a comfort level with proposed future business processes so there is a close understanding of the implications of these decisions on the organization. Multiple touch points planned for the project will provide increasing levels of understanding and hands-on opportunities to experience how each business process flow will function within the organization.
Horizon adopts the Waterfall methodology on most system deployment projects. We believe the methodology provides the structure to facilitate a business process-based approach that uses iterations of testing to produce high-quality results and provides the client with hands-on experience with the proposed solution as early in the project as possible. To achieve this hands-on experience, Horizon recommends and incorporates prototyping early in the project lifecycle to proceed through typical early-phase project testing without delay.
The Waterfall methodology provides a way to assign priorities to project activities and tasks, based on the relative impact of select implementation activities on the organization. This prioritization is typically performed when the project plan is defined, and is reflected in sub-task project activities within each phase.
The methodology provides the opportunity for the client to learn in a guided manner, while also providing many long-term advantages as users seek to leverage and maintain their investment into the future.
The Waterfall Methodology provides the platform for the logical progression of steps to be taken throughout the software development life cycle (SDLC).There are six sequential stages in the Waterfall methodology: requirements gathering, analysis, design, development, testing, deployment/operations. Horizon’s experience with the Waterfall Methodology has provided us with the wisdom to use it when a structured, organizational approach is necessary, the design/approach is largely known
The Agile Methodology provides the platform flexibility for teams to respond to the unpredictability of software development.It provides for an iterative, incremental method of managing the design and building activities of information technology software projects that aim to provide new offerings in a highly interactive manner. Although Horizon advocates for the use of the Waterfall Methodology on software projects, we support the use of the Agile Methodology when there is a need or desire for heavy client participat
Horizon recommends and incorporates prototyping early in the project lifecycle to proceed quickly through typical early-phase product testing and adjustment in order to provide hands-on experience for users and stakeholders as early as possible. Combining the highest level of customer service and expert support teams, Horizon Projects Consulting Corp. customizes delivery approach to match unique business, industry and regulatory requirements. We provide our clients with Project Management, Program
| Phase | Description | Production Steps | Man-hours | ||
|---|---|---|---|---|---|
| Discovery and Planning | This first phase begins during the sales process and then continues post-sale. During this period, the project team will be created. There will be initial meetings and documentation developed as the team works to identify current issues and potential solutions. An important part of this phase is constructing the project plan, which will serve as a guide throughout the rest of the project. |
|
|
||
| Design | In the ERP Design phase, the project and implementation teams will work out the various configurations for the new system, defining roles and documenting standard procedures-essentially, identifying what the new enterprise-wide system will look like and how will it be used in the organization. |
|
|
||
| Development | The purpose of the Development phase is to prepare the entire system for going live. This includes activities such as completing any necessary customizations, developing user training initiatives and importing data. The idea behind any custom software development project is: “First, solve the problem, then write the code.” |
|
|
||
| Testing | The Testing and Development phases will often overlap as the implementation and project teams jump between the two, constantly fine-tuning the configuration to determine if the system is in functional alignment with the set requirements for the project. |
|
|
||
| Deployment | The project and implementation team will assess the status of the project and make the final go or no-go decision. Prior to going live, the final data will be loaded and validated. The project team will train other employees who will then start working in the new system. |
|
|
||
| Continuous Support | Once the ERP system has gone live, the purpose of the project team will shift. Over time, as the way the users work within the system evolves, adjustments and changes to the system configuration may be needed |
|
|