Project Methodology

 

 

 

We actively listen to develop a comprehensive understanding of our client’s organization, corporate responsibility programs, suppliers and subcontractors, manufacturing and testing/certification processes, and enterprise data systems. We take the "discovery phase" of the project seriously because the solution we design can only be as good as the input parameters on which it was based. The duration of this phase depends on the maturity of the client's testing and data management program, project scope of work, resources, timeline, budget, and related variables.
  Improvements are always possible, but the accumulation of even the smallest improvements may result in scope, budget, and timeline creep. To avoid this fate, a usability (UX) expert will be involved in early stages of the project to help validate your understanding of how the solution will be used under realistic conditions. Prototypes will be developed for your review and approval before the first line of code is written. While this phase is very much interactive, we leave the final design considerations to the UX experts and designers.
  Development begins on signoff of the design; depending on the timeline and project complexity, a weekly standing meeting will be conducted with your team to review progress and solicit input on the system. We have budgeted for minor "iterations" following each progress meeting, but we do not anticipate significant refactoring will be necessary unless the scope of work changes mid-stream. This sometimes happens when your team gains experience with the application and you begin to recognize opportunities for further integration with other enterprise business systems. We can always defer these changes until a future project phase if the primary objective is to get the core system into production and benefit through the input of a wider group of stakeholders.
  The project wraps up with the user acceptance testing (UAT) phase, during which your project team exercises the production-ready application and verifies that all requirements identified in the scope of work have been satisfactorily met. Your internal system administrator(s) will be trained by one of our product experts and the system will be commissioned into full production following written system acceptance.