Our Traditional methodology is appropriate for medium to large-sized projects, or where a higher level of customization is anticipated. It involves client and consultant team members working together from the project kick-off to system delivery. It is a proven approach that works well for larger teams and complex implementations.
There are 5 phases to our Traditional methodology:
Just as you would not start building a house without detailed architect drawings and a schedule, we won’t start an ERP project without the same level of planning. We will develop a formal project schedule using Microsoft Project and assign resources to each task. Each team member will then have a clear set of tasks with due dates so it is clear what is required and when it must be complete. Other formal project documents will be prepared such as a project plan, communications plan, development standards, testing plan, training plan, and production support plan to name a few.
Discovery & Design
We listen to you and define together what your specific business requirements are and design the system around them keeping the goal of minimizing customizations so you will have an easier time applying software service packs and performing system upgrades.
Build & Develop
Based upon your needs determined in the Discovery & Design phase, we will configure the system to take advantage of best practices and the many features delivered with PeopleSoft. The newly configured system will be unit tested to confirm the validity of the design. Data Conversion, Interfaces, Customization, Security and Reporting requirements defined during the Design phase will be completed, tested, and promoted to the system test environments.
Test, test, and test again to confirm the configured and customized version of the application operates as desired and meets the business requirements defined in the initial statement of work and the Discovery & Design phase. Types of testing during this phase includes, system testing, integration testing, user acceptance testing, and for larger projects, formal system performance testing may be required.
End user training, cut-over rehearsal, final cut-over, and production support are the major tasks in this final project phase. The quality of the user training cannot be overlooked as it influences the quality of the go-live experience and overall end user satisfaction, which is a key measure of the project success.
Defined Feature Methodology
This is an abbreviated form of our traditional methodology that works best for smaller projects that have little or no customizations. Your teams involvement is limited during more of the project life cycle as we perform most of the project tasks based upon a clear and detailed statement of work and defined project checkpoints to confirm we are on-track in delivering your desired solution. Details of this approach can be obtained by contacting S2 Projects.
Project Success Factors
The project requires a clear statement of work, simply stated, that lists all the software features to be implemented by module, along with required business requirements. The statement of work must be written together so it is clear to both parties what is to be accomplished, who will perform the work, and when the product is to be delivered.
We need to be partners. Over the years, projects have evolved from a strict “arm’s length” fixed price, almost adversarial relationship to a true partnership. The raw truth is every project needs participation from all parties to varying degrees throughout the project life cycle. It is common for customers to change project expectations throughout the project, so both sides need to work together to accommodate scope and schedule changes while minimizing cost impact.
The project needs your best and brightest. We bring product expertise but you know your business better our team ever will. It is only together that tasks can be accomplished in a way to make the project a success. Certainly, our team of consultants will lead your project at every step, but your team’s knowledge cannot be replaced.
“We do it this way”
Yes, but what do you really need?
Start fresh. Think simply. What information do you really need to effectively run your business? Just because you can collect massive amounts of data – refrain from that temptation and collect useful information that provides management with the ability to understand the numbers and act on them.
Remember, for your core functions, the objective is still basic – being paid by your customers, paying your employees and vendors, tracking your assets, projects and employee benefits, and financial reporting. Let’s identify statutory requirements – this is what you must do. Then let’s understand what management really wants to see. Perhaps it’s different from what they get today. If so, why just replicate your current business processes, chart of accounts, and data collection?