<Project Name> Project Charter Version: .

Project Charter
for

<MapApp Project>
Version .1

Prepared by <Donghoon Kwon >

<Mobile Professional Inc.>

<January 21th, 2016>

Creation Date: 1/21/2016 Page 1 of 11

Project charter sample
<Project Name> Project Charter Version: .1

VERSION HISTORY

Version Implemented Revision Approved Approval

Reason
# By Date By Date
Initial Project Charter
0.1 Donghoon Kwon 01/26/2016 01/26/2016
draft

Creation Date: 1/21/2016 Page 2 of 11

Project charter sample
<Project Name> Project Charter Version: .1

TABLE OF CONTENTS
1 INTRODUCTION .................................................................................................................... 4
1.1 Purpose of Project Charter ........................................................................................ 4

2 PROJECT AND PRODUCT OVERVIEW ........................................................................... 4

3 ALTERNATIVES .................................................................................................................... 4

4 SCOPE ...................................................................................................................................... 4
4.1 PROJECT SCOPE..................................................................................................... 4
4.2 High-Level Requirements ......................................................................................... 5
4.3 Major Deliverables/Milestones ................................................................................. 6
4.4 Assumptions .............................................................................................................. 7
4.5 High Level Risks ....................................................................................................... 7

5 DURATION .............................................................................................................................. 7
5.1 Estimated Timeline ................................................................................................... 7

6 BUDGET ESTIMATE ............................................................................................................. 8

PROJECT CHARTER APPROVAL.......................................................................................... 9

APPENDIX A: REFERENCES ................................................................................................. 10

APPENDIX B: KEY TERMS .................................................................................................... 11

Creation Date: 1/21/2016 Page 3 of 11

Project charter sample
<Project Name> Project Charter Version: .1

1 INTRODUCTION
1.1 PURPOSE OF PROJECT CHARTER
The MapApp Project Charter documents and tracks the necessary information required by
decision maker(s) to approve the project.
The intended audience of this Charter is the project sponsor and senior leaders.

2 PROJECT AND PRODUCT OVERVIEW

The mobile phone market is rapidly evolving to accommodate mainstream needs.
Currently, many cell phones makes and models have the power of and functionality of a
personal computers and laptops; these are known as smartphones. Because smartphones
are compact and versatile, the user can carry it to assist in everyday activities. As with
most computers, smartphone have the capability to download and operate software
applications where wireless services exist.
According to research conducted by Kantar WorldPanel[1], the Android OS is the most
popular open source mobile operating system, which is gaining popularity compared to all
other mobile Operating Systems. Other mobile Operation Systems include iOS, Blackberry,
and Windows Mobile. Since the trend of the mobile phone market is changing to an
Android OS-enteric platform, the demand for innovative Android applications is in high.
For this reason, the proposed project intends for developing Android application for the
user requiring public transportation and parking services in MD area. The application shall
be named MapApp.

3 ALTERNATIVES
Prior to initiating this project, Maryland Transit Administration (MTA) system was
reviewed and a gap analysis conducted to verify if they would be candidates for use.
a. MTA system – MTA system provided transportation information in conjunction with
Google map as well as a purchasing functionality, but it did not provide parking
information so that this application cannot be used.

4 SCOPE
4.1 PROJECT SCOPE
 MapApp shall be designed to timely respond to the user’s request to access multiple
public transportation routes, schedules, stops and public parking. The application shall
interface with existing systems to display Maryland Transit Administration
(abbreviated as MTA) bus routes, schedules, stops, and public parking relative to the
user’s current location and end destination. The existing systems are the MTA
database, payment processing system, e-ticket system, and Google Maps. The system
shall be have the ability to download via wireless Internet or cellular connections. A
high level project scope based on a Context Diagram is illustrated as Figure 1.

Creation Date: 1/21/2016 Page 4 of 11

Project charter sample
<Project Name> Projeect Charter Version: .1

Figure 1 Conntext Diagraam for MapA

App

4.2 H
HIGH-LEVE
EL REQUIIREMENTS
Thhe following table pressents the higgh-level funnctional requuirements thhat the project’s final
appplication m
must meet inn order for thhe project obbjectives to be satisfiedd.
R
Req. # R
Requirementt Descriptions
Thee ability to search destination: T The start icoon shall be labeled “Seearch
Desstination”. AAfter users cliick the icon,, they shall hhave to type their destination
nam
me or addresss in the destiination box. Next, MapA App shall dispplay their cuurrent
1
locaation relative to all MT TA locations and publiic parking lots. Then, other o
funcctions shall be availablee. The appliccation will be b developedd for open uusers;
therrefore, the usser shall not bbe required too login or siggn out.
Thee ability to sselect bus rooute: Users sshall easily fiigure out direections and trravel
timees relative too their location. The screeen shall dispplay all posssible directionns in
2 ordeer for users tto select the bbest route. T
There shall bee a history fuunction, whicch all
userrs shall be aable to save ttheir selectedd routes, schhedules, stopss and parkinng lot
seleections.
Thee ability to sselect parkin ng lots: The feature shalll display all Park & Ridee and
3 freee-of-charge ppublic parkinng public loocations withhin the locaal vicinity off the
seleected public ttransportationn routes, schedules, and sstops.
Thee ability to select
s bus schedule: The “Select bus schedule” shhall display pprices
4 baseed from the user’s seleccted bus stopp or stops aand the e-Ticcket system. The
seleected bus schhedule shall bbe automaticcally saved inn the e-Tickeet system in case
Creation Date: 1/21/20016 P
Page 5 of 11
Project ch
harter samplee
<Project Name> Project Charter Version: .1

the user decides to choose the selected schedule for future use, illustrated in Figure
1
The ability to purchase bus ticket: This application will be interfaced with the
MTA system so that users shall type their credit / debit card number, Card
5 Validation Code (CVC) number, and expiration date. Once transaction is
completed, users shall download an e-Ticket, and a copy of the transaction shall
be saved to the e-Ticket system.

4.3 MAJOR DELIVERABLES/MILESTONES

The following table presents the major deliverables / milestone related to this proposed
project.
Major Deliverables / Milestones Descriptions
Identifies the project need, cost, duration and creates
Project Charter
acceptance to begin project
Provides the stakeholders with risk, issue and other
Project Management Plan
project information related to their project
Provides the business solution for a project including
the documentation of customer needs and
expectations. The main objectives of the BRD is to
gain agreement with stakeholders, provide a
foundation to communicate to a technology service
Business Requirement Document provider what the solution needs to do to satisfy the
(BRD) customer’s and business’ needs, provide input into
the next phase for this project, and describe what not
how the customer/business needs will be met by the
solution. Walkthrough conducted by Business
Analyst to achieve approval from Business as to the
proposed project requirements
Provides a comprehensive list of steps that will be
taken during the project is developed. It also provides
detailed information on how business needs and
Functional Requirement goals will be delivered through a specific project
Document (FRD) focusing on application functionalities and UML
diagrams. Walkthrough conducted by Business
Analyst to achieve approval from Business as to the
proposed project design
Indicates that the developers have each and every
thing that they need to develop the application. This
Technical Design Document
document should be written in a language which
(TDD)
developers can understand, and walkthrough
conducted by a tech lead and solution architects
Describes the scope, approach, resources and
Test Plan schedule of intended test activities. This document
identifies test items, the features to be tested, the
testing tasks, who will do each task, degree of tester

Creation Date: 1/21/2016 Page 6 of 11

Project charter sample
<Project Name> Project Charter Version: .1

independence, the test environment, the test design

techniques and entry and exit criteria to be used, and
the rationale for a choice, and any risks requiring
contingency planning
Specify inputs, predicted results, and a set of
execution conditions for a test item. The major
objective of this document is to decompose the
Test Case
application functionalities into smaller units which is
testable with input and to produce a result that is
measurable.
Conducted in conjunction with PM, BA, and QA that
User Acceptance Testing
constitutes business acceptance of the product
Identifies to the stakeholders and project team tasks
Deployment Plan
necessary to move application into production
Provides the latest information about new features,
Release Notes
enhancements to existing features, and defects fixed

4.4 ASSUMPTIONS
a. All end users must have Android OS-based smartphone so that they are able to
download and install the application.
b. Executive support will continue throughout the lifecycle of the project.
c. The application shall interface with the MTA system.
d. The application shall only transmit and receive from a cell phone carrier or by a
wireless internet connection.
e. The application shall perform all external connections via interface subsystem.
4.5 HIGH LEVEL RISKS
a. New technology may be made available during the life cycle potentially resulting in
delays or increased cost if additional functionality is added
b. The application fails testing phasing and does not meet requirements of stakeholders
c. Payment information from end users is not secured
d. End users dislike the application and resist and/or refuse to use the system.
e. Project exceeds budget impeding the completion of the project.

5 DURATION
5.1 ESTIMATED TIMELINE
The estimated project schedule is 12 months. However, the project must be completed by
the end of the next fiscal year – September 30th, 2016 (Not to exceed 13 months). Detailed
project schedule will be created by Microsoft Project 2010 and critical paths will be also
identified.

Creation Date: 1/21/2016 Page 7 of 11

Project charter sample
<Project Name> Project Charter Version: .1

Major Deliverables / Milestones Expected Completion Date

Project Charter TBD
Project Management Plan TBD
Business Requirement Document (BRD) TBD
Functional Requirement Document (FRD) TBD
Technical Design Document (TDD) TBD
Test Plan TBD
Test Case TBD
User Acceptance Testing TBD
Deployment Plan TBD
Release Notes TBD

6 BUDGET ESTIMATE
The rough guess of the total project budget is $119,000(+100% -50%) as follows:
Labor: $100,000
Software and Licenses: $8,000
Misc. and Contingency Reserved: $11,000
$119,000 has been initially and roughly budgeted for this project. However, more funds
may be required as unexpected risks are arisen even if a contingency fund is assigned.
Additionally, detailed budget will be estimated and calculated by the COCOMO II cost
estimation model.

Creation Date: 1/21/2016 Page 8 of 11

Project charter sample
<Project Name> Project Charter Version: .1

PROJECT CHARTER APPROVAL

The undersigned acknowledge they have reviewed the MapApp Project Charter and
authorize the MapApp project. Changes to this MapApp Project Charter will be
coordinated with and approved by the undersigned or their designated representatives.

Signature: Date: 08/06/2015

Print Name: Donghoon Kwon
Title: Business System Analyst
Role:

Signature: Date:
Print Name: John Doe
Title: Project Manager
Role:

Signature: Date:
Print Name: Jane Doe
Title: Project Sponsor
Role:

Signature: Date:
Print Name:
Title:
Role:

Creation Date: 1/21/2016 Page 9 of 11

Project charter sample
<Project Name> Project Charter Version: .1

APPENDIX A: REFERENCES
The following table summarizes the documents referenced in this document.
Document Name Description Location
and Version
Apple market Global smartphone OS Sales Section 2 PROJECT AND
share grows Share (%) PRODUCT OVERVIEW
across Europe,
US, and China

Creation Date: 1/21/2016 Page 10 of 11

Project charter sample
<Project Name> Project Charter Version: .1

APPENDIX B: KEY TERMS

The following table provides definitions for terms relevant to this document.
Term Definition
Assumption A factor that, for planning purposes is considered to be true,
real or certain without proof or demonstration.
Deliverable Any unique and verifiable product, result or capability to
perform a service that must be produced in order to complete
a process, phase or project.
Milestone A significant accomplishment or event in the project scope,
such as completion of a major deliverable (e.g., product
releases, user acceptance).
Project An endeavor to create a unique product or service.

Risk An uncertain event or condition that, if it occurs, has a

positive or negative affect on a project’s objectives.
MTA (Maryland Transit MTA is a provider of transportation services such as Local
Administration) Buses, Metro Subway, Light Rail, and MARC Train.
COCOMO II Standards for Constructive Cost Model, and it is used to
estimate the cost of software development.
Contingency Reserved The amount of quantity of funds or other financial resources
that is required to be allocated at and above the previously
designated estimate amount to reduce the risk of overruns to
an acceptable level for the financially responsible
organization.
Context Diagram A diagram that defines the boundary between the system, or
part of a system, and its environment, showing the entities
that interact with it.
Microsoft Project 2010 Software for creating project schedule

Critical path The sequence of project network activities which add up to

the longest overall duration, regardless if that longest
duration has float or not.

Creation Date: 1/21/2016 Page 11 of 11

Project charter sample