Projects |

JRESINC is a fastest growing chicago,IL based information technology company. Head-quartered in Chicago, our offices are located in california and india.

JR Enterprise Solutions Inc. was founded with the sole intention of amalgamating our varied domain knowledge base into cost-effective and value-oriented industry solutions. With integrated solutions, software development, technical services, training and staffing QA support, we help customers fulfill their technology goals allowing them to focus on their business. We offer customers the choice to have solutions built on-site, off-site, offshore, or a hybrid option of a custom combination thereof. Our experience, coupled with our commitment and synergy, ensures the best value to our customers.

Our mission is to provide customers with unique and most advanced methods of value added services With track record of delivering high quality, cost effective and time oriented services, JRES has established strong relations with its clients.

Project Methodology

At JRES, we understand the multiple factors that can impact project scope, planning and execution and how to mitigate these impacts. We will work with the client team to define a Project Charter that clearly and concisely delineates the project scope, Plan and execution schedules and a stringent change request process to manage any potential modifications to scope..

project-img

Key Activities:

Define as-is process
Identify areas of improvement
Develop a reengineering plan based on mySAP best practices (if required)
Customer solution strategy (if necessary)
Identify the metrics from the ValueSAP KPI database (if required)
Help the customer in setting up benchmarks for the identified KPIs
Help the customer in building a business case

Sample Deliverable:

Business process matrix
Program charter
Business case
Solution strategy map
Program management approach

JRES Approach

We recognize that scope control is a critical success factor for all projects. As the team and end users become familiar capabilities within the project, it is common to want to take immediate advantage of functionality that will provide benefit to the client, losing sight of the project’s objective of a vanilla implementation and opening up the potential for ‘scope creep’. To meet clients timeframe and budget for this project, it is essential that scope be tightly controlled. There are different elements of scope that impact the timing, resourcing and costing of a project.

They are:

Process Scope
Organizational Scope
Functionality Scope
Technical Scope
Infrastructure Scope

One key element of any project’s success is that there exists a shared understanding among all stakeholders of all these elements of project scope what the project will and will not deliver. In order to build this common understanding, it is important to document the components that are within the scope of the project, and those that are beyond its boundaries, for all levers. While it may seem time consuming, comprehensive documentation of these details at the start of the project greatly reduces the risk of wasted time later due to unclear objectives and misaligned expectations.

This documentation is developed during the project Preparation/Planning phase and provides the basis for the project Charter. During the Business Blueprint phase, the Project Charter is created to confirm project scope.

Process Overview

For a change to be considered, a written Change Request must be submitted to project leadership. Project leadership will determine whether the Change Request merits additional investigation. If so, project leadership will assign it to the appropriate members of the SAP project team.

They will evaluate the Change Request, and respond with an assessment of the advisability of proceeding with this change, including an estimate of the time and cost required to implement it. The project leadership will then decide whether to approve, defer or reject the change request.

Escalation procedures for deferred or rejected Change Requests will be included in the Change Request Procedures.

If a Change Request has an impact on budget or schedule, it will be presented to the Steering Committee for approval. The Steering Committee will determine whether the benefits of the proposed change merit the investment, and whether they are willing to provide additional funding.

We recognize that all project team members have a responsibility for managing scope from Day One of the project. We will communicate this, along with our Change Management Procedures, in Project Team Kick-Off training. We will also incorporate information about the Change Request process into project awareness communications to the user community.

Issue Management Process

Our approach to problem/issue resolution focuses on capturing issues through issue tracking tool, assigning a clear owner, setting deadlines, and monitoring issues at a project level. Issue resolution should also be an input into the project scorecard.

IssueManagementProcess-img1 (1)

Issue Escalation Process

In order to resolve issues in a timely manner, priorities will be assigned and a turn around time allocated to each issue. At each checkpoint, if the issue has not been resolved and further assistance is required, the issue will be escalated to the next level

IssueEscalationProcess-img