Project Management Plan Of JAMES Project

qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopa
sdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghj
klzxcvbnmqwertyuiopasdfghjklz
xcvbnmqwertyuiopasdfghjklzxcv
bnmqwertyuiopasdfghjklzxcvbn
mqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwe
rtyuiopasdfghjklzxcvbnmqwerty
Analyzing and Evaluating James
Project development of prototypical
service applications for use with a
smart card

Executive Summary
This report aims to critically analyze and evaluate the project management plan of JAMES
project which has been created to develop prototypical service applications for use with a
smart card. This project is responsible for producing a running system on smart cards
which will interact with the automobiles and an external client/server environment
without any platform in between.
This project was initiated on 26th August, 1997 and the complete system was ready by first
week of December which was then sent for client acceptance. This report will be
responsible for providing an overall view of the project including budget plan and schedule
plan.
On completion, drivers of Mercedes Benz and other automotive service facilities will be
able to use prototypical service applications with the use of a smart card.
1 | P a g e

Table of Contents
1. Introduction......................................................................................................................................................... 4
2. Analysis of PMP.................................................................................................................................................. 4
2.1 Introduction.................................................................................................................................................. 4
2.1.1 Project Name........................................................................................................................................ 4
2.1.2 Project Description............................................................................................................................ 4
2.1.3 Sponsor’s details................................................................................................................................. 5
2.1.4 Project Manager and Team Details............................................................................................. 5
2.1.5 Deliverables.......................................................................................................................................... 6
2.1.6 Reference Details............................................................................................................................... 7
2.1.7 Definitions............................................................................................................................................. 7
3. Organization Section.................................................................................................................................... 7
3.1 Organization Charts.............................................................................................................................. 7
3.2 Project Responsibilities....................................................................................................................... 8
4. Management and Technical Approach Section................................................................................. 9
4.1 Management Objectives...................................................................................................................... 9
4.2 Project Controls...................................................................................................................................... 9
4.3 Risk Management.................................................................................................................................. 9
4.4 Project Staffing..................................................................................................................................... 11
4.5 Technical processes........................................................................................................................... 12
5. Work to perform Section......................................................................................................................... 12
5.1 Major Work Packages........................................................................................................................ 12
5.2 Key Deliverables.................................................................................................................................. 12
5.3 Other........................................................................................................................................................ 12
2 | P a g e

6. Schedule.......................................................................................................................................................... 12
6.1 Summary................................................................................................................................................ 12
6.2 Detailed................................................................................................................................................... 12
............................................................................................................................................................................ 14
6.3 Other........................................................................................................................................................ 14
7. Budget.............................................................................................................................................................. 14
References............................................................................................................................................................... 15
Appendices............................................................................................................................................................. 17
Appendix A......................................................................................................................................................... 17
Appendix B......................................................................................................................................................... 18
Appendix C......................................................................................................................................................... 19
3 | P a g e

1. Introduction
Smart cards which are usually a plastic card with some embedded programming chip used
for storing and transacting data through it, is now the trend of our society. People of every
class, higher, middle and even lower middle are using smart cards for vast range of
applications such as parking, mobile communications, shopping, and membership of some
brand or private vendor (Kristoffer, Grude & Hague ,2007). These smart cards are this
much popular because of its easy portability and high security. Every card is secured with a
password and even if a card is theft or stolen, it doesn’t result in any loss of value for the
owner of the card (Kristoffer, Grude & Hague ,2007).
2. Analysis of PMP
2.1 Introduction
This project analyses a management plan which will evaluate design and development of a
similar smart card which can be used by the drivers of Mercedes Benz and other
automotive service facilities as a value added service. The aim of the project is to add a
running system to the smart card via which it can interact with car and the client (Ralph,
Irwin, Ludin, & Robertson, 2009).
2.1.1 Project Name
The project has been named as JAMES project, here JAMES stands for Java Architecture for
Mobile Extended Services and the name is perfectly genuine as the project is related to
development of as java system that can add value added services for the car drivers. The
project has been developed using java architecture and hence the name (Kristoffer, Grude
& Hague ,2007).
2.1.2 Project Description
JAMES project had been aimed to develop an application that could add value added
services to the luxury cars such as Mercedes Benz via smart card which is easily portable.
The goal of the project is clearly identifiable in the controlling document and is written in
an easily understandable language (Silverman, 2013). The document also tasks about the
4 | P a g e

project planning which includes identifying and scheduling of tasks. All the project
responsibilities had been handled along with managerial process and risk management
plan. There is also a criterion for overall project plan which incorporates work elements,
cost and budgeting plan (Silverman, 2013).
2.1.3 Sponsor’s details
The sponsor persons of the JAMES project are identified as:
Diamler Benz, Brigitte Pihulak and Dieter Hege.
In case any discussion is to be done with the client person, the back-up support had been
provided through Client Board. If something urgent was to be discussed then few specific
consultants of the client organization specified by the client board can be contacted
through an email or via phone (Ralph, Irwin, Ludin, & Robertson, 2009).
2.1.4 Project Manager and Team Details
The Project Managers for the JAMES project are:
 Torres-Yebra
 Sam Perman
 Guerrero-Galan
 Alfonso
 Allen Dutoit
 Brian Cavalier
 Malcolm Bauer and
 Bernd Bruegge
And the other team members responsible for overall-different tasks are:
Infrastructure team whose members are:
Stephan Schoenig responsible for java support and case tools, also for communication
infrastructure and Joyce Johnstone responsible for Website mastering and Lab
management.
5 | P a g e