Trecata Methodology

Each project can be broken down into a series of stages that are critical to the success of the project. Each successive stage builds upon the previous until the project is complete. The Trecata methodology is a structured approach to projects developed with years of real-world experience and best practices. Our deliverable-based methodology is flexible enough to merge with any internal project standards.

By working with you during each phase, we can develop a clear understanding of the scope of the entire project and its deliverables. Trecata's methodology

• Produces consistently high quality results;
• Promotes predictability; and
• Minimizes risk.

Trecata Implementation Methodology

Sample Deliverables:

Phase 1: Analysis and Conceptual Design Deliverables

• Train Project Team
• Detailed Project Work Plan
• Project Team Roles and Responsibilities
• Milestone Dates and Deliverables
• Initial Level of Effort
• Installed Hardware and Software
• User Familiarization of System Functionality
• Initial Integration and Implementation Plan
• "As is" and "To be" Business Process
• Requirements Mapping
• Gap Analysis
• Interface and Conversion Requirements
• Data Integrity Cleanup Plan

Phase 2: Detailed Analysis Deliverables

• Completed Application Prototype (Conference Room Pilot)
• Application Walk-thru and Acceptance
• End-User Training Strategy
• Design Workbook
• Construction/Implementation Work Plan
• Program/Interface/Customization Secifications

Phase 3: Construction - Deliverables

• Completely Configured Application
• Interfaces
• Data Conversions
• Enhancements (if required)
• Operational Environment
• Approved End-User Procedure Manuals
• Revised Implementation Plan

Phase 4: System Test - Deliverables

• User Acceptance on the configured system and customizations
• Approved Training Guides and Plans
• System Test Log
• System Change Requests

Phase 5: Implementation - Deliverables

• Training Schedule and Guides
• Final Cut-over Plan
• Conversion Reconciliations

Phase 6: Implementation Review - Deliverables

• Prioritization of Remaining Requirements
• Project Summary
• Sign-off - User Acceptance
• Lessons Learned