JAGGAER Implementation Methodology

The Project Initiation step lays the groundwork for the entire project. During this step, the JAGGAER team conducts an internal hand-off from Sales and begins to understand the project objectives. The team will then assess readiness, perform some preliminary discovery, and establish both project governance and the project team.

The most important part of Project Initiation is confirmation of the client’s business objectives, goals, and strategy. These priorities are the metric by which subsequent decisions can be judged. The goal of Project Initiation is to ensure that all team members fully understand and embrace these priorities.

The JAGGAER methodology includes project team structure, a formal communication plan, business process documentation, acceptance, change control processes, and the escalation matrix.

As part of the overall project communication plan, JAGGAER establishes a communication path for the client team to facilitate coordination of actions and plans.

The client and JAGGAER teams gain alignment around project objectives, goals, timeline, and scope during this step.

During the Introduction and Planning step, the client and JAGGAER conduct a formal handoff from the JAGGAER Sales team to review the project scope, business drivers for the project, and the planned strategy/methodology for achieving them. Project success metrics, project risks, in-scope and out-of-scope business processes, change management strategy, and deployment strategy discussions are initiated at this point.

JAGGAER works with the client to define an initial project plan and confirm that the team has a thorough understanding of standard project operating procedures based on the scope defined in the statement of work. (e.g., acceptance criteria, change control process).

This step is used to align the team members around the objectives of the project, the capabilities of the solution, and the methodology that will be applied to realize the project’s success.

During the Team Alignment step, the official Project Kickoff is conducted including the JAGGAER core team, client core team, client project sponsors and client extended stakeholders. The objective of this event is to communicate the following to the full team:

• Business objectives and business strategy
• Definition of the team roles and responsibilities
• Project timeline outline and when each role will be required during the project
• Metrics that will be used to measure the overall success of the project
• Overall project scope

Members of the core project team collaborate with the JAGGAER team in a workshop to begin configuration of a fully integrated solution.

The client and JAGGAER work together to understand and validate business processes and, if applicable, establish initial connectivity between the various systems and begin integration design.

This workshop is an introduction to the solution for the core project team and a vehicle for understanding business processes.  Upon completion of the workshop, members of the team work together to continue configuration of the solution through functional and technical working sessions.

JAGGAER uses the End-to-End Demonstration to confirm configuration of the application and to gain their feedback. During this event, the JAGGAER consultant or, in many cases, the client, demonstrates client-specific business scenarios to these users and challenges them to imagine using the solution on a day-to-day basis.

Since a new solution introduces new processes, users are introduced to our proposed processes for performing their daily tasks with the End-to-End Demonstration. By walking through these scenarios, we can validate whether these processes will prove successful for your organization.

The project team performs comprehensive testing of the solution to validate the design using actual business scenarios.

Solution Validation testing is an extended period of time that starts immediately after the End-to-End Demonstration. The extended testing period gives the client adequate time to validate all business scenarios and make required adjustments. The following are some key activities performed during this phase:

• Validate configurations through execution of business scenarios based on the test plan
• Conduct regular meetings to ensure the testing of scenarios is tracking to the plan and to review reported issues or questions
• Update the solution based on the testing results
• Update the training documents to reflect the processes utilizing the solution

For some implementations, User Acceptance Testing begins when the Core Team has completed the majority of their testing.  This allows selected end users and other stakeholders to gain access to the solution and understand how their business processes will work.

Depending on the solution(s) being rolled out, the Initial Event Walkthrough will be conducted with the Core Team prior to releasing the system to the larger client base. This can include sending out live orders, hosting a sourcing event, completing contract negotiations and workflow, and so forth.

This controlled event is monitored for success. Once validated, the solution is ready for go-live.

Services following go-live include time for post-production support and additional end user or administrative training services, depending on the size and scope of the engagement.

Once the solution is in production, the client’s focus shifts to deployment and rollout activities to the user community.

JAGGAER’s project team facilitates a formal hand-over from Professional Services to its Global Support team, who provide ongoing maintenance and support. This event signifies closure of the implementation project.

The client is assigned internal support representative(s) who will begin to triage issues for submission to JAGGAER Client Support and continue to build knowledge of the solution.