Consulting Methodology

Seasoned guidance throughout the implementation process, from design through rollout

Mitratech's implementation methodology is designed to:

• Enable clients to design an efficient and effective system for their unique requirements;
• Identify and incorporate process improvement opportunities such as streamlining and standardizing processes;
• Manage project progress, identify and mitigate project risks; and,
• Direct and facilitate change management opportunities.

 Mitratech’s methodology for business process review and requirements gathering follows a standard project management practicum, which includes the following phases:

Project Initiation

Project Initiation is the process by which Mitratech and stakeholders agree to contractual terms on expectations and define a collective roadmap and plan for implementation.

There are distinct events in this phase:

• Drafting Statement of Work and Project Plan
• Reviewing the approach and finalizing the scope and Statement of Work
• Identifying the project team's resources and responsibilities
• Obtaining approval on Statement of Work, Project Plan & Estimated Timeline
• Installing the current design on the development server
• Conducting the Project Kickoff & Team Orientation

Ongoing Project Management

To provide quality project management and leadership during the project, the Mitratech Project Manager will work closely with the Client’s Project Manager on all aspects of the project.

The Mitratech Project Manager’s responsibilities include:

• Creating and maintaining the project plan
• Documenting and addressing project issues and solutions
• Conducting scheduled project review sessions
• Creating and distributing status reports to stakeholders
• Reporting actual costs versus budget
• Managing appropriate resource deployment. 

Business Process Design

The Design phase focuses on both system and process design with requirement definition as central to success. Our methodology focuses on gathering functional and system requirements in the most time-effective manner by identifying the gaps between the Client’s business process and functional needs and TeamConnect’s standard application. All levels of business process and user interaction are reviewed to ensure the design meets the Client’s expectations.

Areas normally reviewed:

• Matter Intake
• Service of Process
• Case/ Matter Assessment
• Matter Management
• Document Management
• Spend Management
• Budgets
• Invoice
• Outside Vendor Engagement, Management and Evaluation
• Financial Reconciliation
• Reports
• Matter Close
• Compliance

Configuration and Custom Build

In this phase, configuration and customization will begin.  Requirements that cannot be configured will be custom built to the Client’s specifications.

Custom work may include interfaces with internal or external applications such as Accounts Payable or Human Resources applications, custom functions such as complex calculations or tools that perform functions specific to the Client’s industry. All work is documented and approved by the Client prior to implementation.

Testing

Mitratech conducts unit, object, and full business cycle testing prior to delivering the system to the client for user acceptance testing. The Mitratech Project team works with the client to ensure that use cases are pre-defined and results meet expectations.

This phase includes:

• Conducting the Testing Planning Meeting
• Reviewing and Approving test plans and test cases
• TeamConnect Functionality / System Testing
• Obtaining approval on Testing and Results

Go Live!

After testing and client approval, TeamConnect is deployed to users. Mitratech works with the client on the implementation schedule depending on number of locations, number and type of users, and training capabilities. Mitratech may also convert data from an existing application into TeamConnect and assist the client in verifying data accuracy and structure.

Standard events in the phase include:

• User and security setup
• Data conversion if needed
• System administration training
• Installation of final system configurations
• Executing the transition plan so that the Client controls the application

Back to top