Post Implementation Review of Concur

1. PURPOSE OF PROJECT CHARTER

The purpose of the project charter is to setup the guidelines on which the entire project will go on. Project charter is basically to set the scope, budget, time and technology that will be used in the project after the discussion between client and team members. so, the post implementation review of concur will be done to assess whether extended destinations will meet, to decide how adequately the project will run and to learn lessons for the future, and to ensure that it will be beneficial for concur customers and users to get the conceivable advantage from the project..

Concur was developed by sniff and was further purchased by federation university and they use it for their staff which provides an estimate price for the travel expenses by getting feedbacks from the current users. when it regards to business travel and cost coordination it means everything. So with Concur our business travel and costs are coordinated by giving us a superior client encounter more precise information and wealthier answering to help us to settle on better choices and increment strategy control while sparing time and cash. There travel booking tools gives them arrangement worldwide travel content that is effortlessly open and constantly accessible from any place on the planet. Travelers have an expansive choice of travel decisions in light of corporate arrangement and individual traveler inclinations. Travelers can rapidly book local and global flights and reserve a spot for rental autos, hotels and trains. Once the trip is reserved travelers can oversee trip subtle elements like flight delay, cancellation  and baggage claims.. Individual can do all these things in a single place. Concur also offer an web application to manage the trips. Concur make the record of all the bills like cab fare, air fare, hotel booking and food bills. There are several apps that are partnered with concur like Uber, Starbucks and they send their bill receipts directly to the Concur app which helps the user to take control of their expenses.

1. BUSINESS NEED & IMPACT

Concur system helps the people in making their travel easier by giving them the fair idea of the expenses before making a travel. Concur also helps in booking hotels, cabs, air tickets so that the traveler can travel without any worry and can make the arrangements on the spot. This helps business companies to grow while collaborating with Concur by increasing their customers.

2. STRATEGIC ALIGNMENT

Project goals:

Goal 1: Document the system impact and how it meets the objectives of the relevant stakeholder groups

Goal 2: the major problem faced by concur team to deal with software .It’s very complicated for the workers to work on this software.

Goal 3: Identify the Concur glitches like after the completion of trip, some of the customers are getting e-mails to clear their dues which are already paid by customer.

Goal 4: Update Concur with customer requirements like some customers recommend to stay in 3 star hotel rather than 5 star to save their money and some ask to use new technology updates.

Goal 5: Address stakeholder and end-user needs

1. OBJECTIVES

The objectives of the post implementation review of Concur are as follows:

• Better customer satisfaction in customer requirements, booking services, real time solution , real time updation in increased air fare and more options to select.
• Make required update in Concur
• solutions of problems that are faced by customers
• Data Analysation to get more correct expense estimate for the trip to be travelled in future.

2. HIGH-LEVEL REQUIREMENTS

Req. #	I Requirement Description
1	The project should match stakeholder’s requirements
2	The project should make Concur in control and reduce future risk
3	Identify the impact of Concur implemented
4	Based on the objective facts, judge the system shortfalls
5	Conduct user review and feedback of Concur system
6	Conduct further training and coaching of Concur system

1. TIMELINE

Time	Activity
08/03/2017	Project begins and weekly activity report start
15/03/2017	Meet with client
25/03/2017	Project charter approved
05/04/2017	Meet with client
07/05/2017	Project progress report approved
18/05/2017	Meet with client
27/05/2017	Team presentation
30/05/2017	Final project report approved
06/06/2017	Individual report

2. KEY MILESTONES

Key Milestones	Estimated Completion Timeframe
Project team formed	28/02/2017-07/03/2017
End-user interview	08/03/2017-30/05/2017
Concur system research	08/03/2017-30/05/2017
Project charter approved	12/03/2017-26/03/2017
Project progress report	02/04/2017-07/05/2017
Team presentation	08/05/2017-27/05/2017
Final project report	08/05/2017-30/05/2017
Project released	30/05/2017-04/06/2017

1. ASSUMPTIONS

Projects are actually judged against two parameters:

How it is well defined?

How well defined are methods to achieve it?

Project should be divided in three structures

• Product breakdown structure
• Organization breakdown structure
• Work break down structure

For good objectives it should meet following criteria.

Outcome Oriented: Speaks to important changes in basic threat and opportunity figures that influence project goals.

Measurable: Characterized in connection to some standard scale (numbers, rate, parts, or all/nothing states.

Time Limited: Should be achievable within a  given period.

Specific: Clearly defined so that all people involved in the project have the same knowledge of what the terms in the objective mean .

Practical: Appropriate or achievable within the context of the project and in light of the social and financial context.

2. CONSTRAINTS

• Sometime the roles of team member changes if they can’t handle the problem
• Less training or knowledge of team to understand the project.
• The analysis report given to client not accepted in case demand changes.
• Policies selected for accomplishing the goal not liked by the client.
• Project managers having difficulty to handle team and client because of less experience.

3. RISKS

• Unreal expenses documents submission by the current users.
• Change in government policies.
• Hike in airfares and other traveling aspects.
• A delay in one task deteriorates the quality of project.
• Time and budget management risk.

Risk Category: Requirement Risk

• Requirement not fully known at project start
• Not deliver the expected results to the client

Risk Category: Project Management Risk

• Priorities changes while working on project
• Sometime same resources required at same time
• Success criteria not well defined

Risk Category: Product/Technology Risk

• Market competition with the similar software’s.
• Update in technology may result in budget risk.
• Technology selected to achieve project goal is poor.
• Including extra analysis method that are not required.

Risk Category: Customer Risk

• Customer demand new requirements under the given time.
• Customer not accept the proposal
• Customer force to work different technology rather than previously used.
• Client not supportive.

1. ROLES AND RESPONSIBILITIES

This section describes the key roles supporting the project.

Person	Role	Responsibility
Fiona Bryant (client)	Client	Provide information about concur to the team and share problem faced while working with concur.
Surjeet singh (team member)	Project manager	Deliver the project to client expectations, Monitor and report to client on project progress, Advise client if project appears to be in danger of non delivery, control project scope and time, keep contact with team members for their working progress and difficulties, contact coordinator if client is unavailable; Work on plan and write project report of every part of the project with other team members, provide the report to client and supervisor.
Taiwo Oseni (Supervisor)	Coordinate project	Give advice if client is unavailable, help the team to finish the project, help team members contact client if the team loose contact with client, balance the project requirement between team members and client, get project working process and project report from project manager and give advice.
Harman (team member)	Risk manager, researcher	Control the project risk, support/provide responsive action for every times risk if happen; Work on plan and write project report of every part of the project with other team members, , discuss the project report detail with other team members;
Amrit (team member)	Documenter, Interviewer	Work on plan and write project report of every part of the project with other team members, discuss the project report detail with other team members; discuss the client requirement with other team members and how to achieve the requirement; Interview end-user to get system feedback, check the coaching process and training materials
Xinwen Hu (team member)	Main documenter	Execute issue management process when issues happen, Work on plan and write project report of every part of the project with other team members, discuss the project report detail with other team members, integrate all member’s report and provide it to project manager; Researching and help team members to get useful resources.

2. STAKEHOLDERS (INTERNAL AND EXTERNAL)

Stakeholder	Interest / stake	Importance
Fiona Bryant (Client)	Make Concur able to use	High
Project manager	Manage project , satisfy client ,fix meetings.	Medium
Team members	Work on project, satisfy client	Low
Taiwo Oseni (Supervisor)	Help team member finish the project	Medium
FedUni End-user	Skilled to use Concur easily	High

The undersigned acknowledge they have reviewed the project charter and authorize and fund the post implementation review of Concur project. Changes to this project charter will be coordinated with and approved by the undersigned or their designated representatives.

Signature:	Date:
Print Name:
Title:
Role:

Signature:	Date:
Print Name:
Title:
Role:

Signature:	Date:
Print Name:
Title:
Role: