You are on page 1of 9

Project Charter Document

Project Name:

Swimmers Team Web Sites

Department:

R&D

Focus Area:

Development

Product/Process: Website / Web Development

Prepared By
Document Owner(s)

Project/Organization Role

Johannes Santoso

Project Manager

Project Charter Version Control


Version

Date

Author

Change Description

27/9/2015

Johannes Santoso

Document created

Confidential
332378270.doc
Last printed on 3/23/2004 11:48:00 AM

Project Charter

TABLE OF CONTENTS
1

PROJECT CHARTER PURPOSE.......................................................................................... 3

PROJECT EXECUTIVE SUMMARY.......................................................................................3

PROJECT OVERVIEW........................................................................................................... 3

PROJECT SCOPE.................................................................................................................. 4

4.1

Goals and Objectives................................................................................................. 4

4.2

Departmental Statements of Work (SOW)..................................................................4

4.3

Organizational Impacts............................................................................................... 4

4.4

Project Deliverables.................................................................................................... 4

4.5

Deliverables Out of Scope.......................................................................................... 5

4.6

Project Estimated Costs & Duration...........................................................................5

PROJECT CONDITIONS........................................................................................................ 5
5.1

Project Assumptions................................................................................................... 5

5.2

Project Issues............................................................................................................. 5

5.3

Project Risks.............................................................................................................. 6

5.4

Project Constraints..................................................................................................... 6

PROJECT STRUCTURE APPROACH...................................................................................6

PROJECT TEAM ORGANIZATION PLANS...........................................................................8

PROJECT REFERENCES...................................................................................................... 8

APPROVALS.......................................................................................................................... 8

10 APPENDICES......................................................................................................................... 9
10.1

Document Guidelines................................................................................................. 9

10.2

Project Charter Document Sections Omitted..............................................................9

Confidential

Page 2

10/6/2016

Project Charter

PROJECT CHARTER PURPOSE


The project charter defines the scope, objectives, and overall approach for the work to be
completed. It is a critical element for initiating, planning, executing, controlling, and
assessing the project. It should be the single point of reference on the project for project
goals and objectives, scope, organization, estimates, work plan, and budget. In addition, it
serves as a contract between the Project Team and the Project Sponsors, stating what will
be delivered according to the budget, time constraints, risks, resources, and standards
agreed upon for the project.

2 PROJECT EXECUTIVE SUMMARY


Points of this project charter are:
Project goals
Objectives
Scope
Risks
Costs
Timeline
Approach
Organization

3 PROJECT OVERVIEW
A local swim team wants to expand the team members and invite the newcomers to join
them. Based on that statement, they want to make a project which can supply the
information about the swim team. Further, they also want the website can provide a report
if they have a meeting. To make it more attractive, they also want the website to include
the pictures of the three assistant coaches and of the different swimmers at swim meets
and practice.

Confidential

Page 3

10/6/2016

Project Charter

4 PROJECT SCOPE
4.1

4.2

4.3

4.4

Goals and Objectives


Goals

Objectives

Finishing a development
of the website, including
basic feature and added
feature.

Objectives :
1. Develop a system until the end of November 2015.
2. Added a feature of the system with an information of
the members in the swim team, included coach,
assistant, and technical helper. So, newcomers can
choose the coach or the assistant that they want.

Departmental Statements of Work (SOW)


Departmental SOW

Owner/Prime

Due Date/Sequence

Organizational Impacts
Organization

Impact to and Participation of


Organization

Project Deliverables
Milestone

Deliverable

1. Development of system

2. Design User Interface

Confidential

Basic feature feature that the swim team request,


such as: registration, show meet result, pictures.
Added feature Information about members, coach,
assistant, etc.
Basic UI including login page, registration, and
gallery page
Added UI information page of team members,
coach, assistant, etc.

Page 4

10/6/2016

Project Charter

4.5

Deliverables Out of Scope


This project will not provide a feature such as:
Payment: the project will not give an online payment feature. Every members must
pay the fee directly to the marketing office every the end of the month.

4.6

5.1

Project Estimated Costs & Duration


Project
Milestone

Date
Estimate

Development of
system
Design UI

Deliverable(s) Included

Confidence Level

12 November
2015

Basic feature

High

30 November
2015

Basic UI

Added feature
High

Added UI

PROJECT CONDITIONS

Project Assumptions
The development will be finished before the end of the November.
The basic feature should be completed, including the basic UI.
Added feature and added UI will be added if we still have a time.

5.2

Project Issues
Priority Criteria
1 High-priority/critical-path issue; requires immediate follow-up and resolution.
2 Medium-priority issue; requires follow-up before completion of next project milestone.
3 Low-priority issue; to be resolved prior to project completion.
4 Closed issue.
#

Date

15/10/2015

Confidential

Priority
4

Owner

Description

Status & Resolution

Rena

The error will


occur when
newcomer
register with the
same name
with the

Closed. This issue has


been fixed.

Page 5

10/6/2016

Project Charter

Date

Priority

Owner

Description

Status & Resolution

registered
member.
2

5.3

5.4

20/11/2015

Cindy

The information
of the team
members arent
displayed
correctly. This
because a
mismatch in UI
code.

Open. This issue will be


fixed soon after the UI for
basic feature is completed.

Project Risks
#

Risk Area

Likelihood

Risk Owner

Project Impact-Mitigation Plan

Developme
nt

Medium

Johannes

If we face some problems/issues in


development, we will have an
additional time to fix this, outside
the planned schedule.

Resource &
Team

Medium

Johannes

Because we have less resource of


the team, theres a possibility the
project will not be finished as the
schedule.

Project Constraints
Must use 100% HTML and PHP for programming language.
Better using high speed connection to load websites because it contain high quality
images and some animations/videos.

Project Structure Approach


Project will be structured and use this following approach:
The project use the combination workflow between Project Manager, Developer, and
Designer.
Developer must inform the progress every week to Project Manager and Designer.
Designer will wait until one feature (or one phase) is done, then she can start to design
it. We use the combination of the serial and parallel workflow. The Project Manager will
update the status of the development and design every week.

Confidential

Page 6

10/6/2016

Project Charter

Dev

Dev

Dev

Design

PM

Phase 1

Design

PM

PM

Phase 2

Phase 3

Design

PM

Phase 4

Notes:

Phase 1 : Dev Development step 1, reporting


PM Calculated estimate timeline, make summary report

Phase 2 : Dev Development step 2, reporting


Design Design step 1, reporting
PM make summary report

Phase 3 : Dev Development step 3 (final), final report


Design Design step 2, reporting
PM make summary report

Phase 4 : Design Design step 3 (final), final report


PM make summary report

Confidential

Page 7

10/6/2016

Project Charter

Project Team Organization Plans


Project Team Role

Project Team Member(s)

Responsibilities

Project Manager

Johannes Santoso

Managing timeline project,


give a brief description about
the project.

Development

Rena

Develop the basic feature


and the added feature of the
project.

Design (Graphic Artist)

Cindy

Design a user interface for


basic feature and added
feature of the project.

8 PROJECT REFERENCES
Milestone
-

Deliverable
-

9 APPROVALS
Prepared by

Johannes Santoso
Project Manager

Approved by

__________________________________
Project Sponsor

__________________________________
Executive Sponsor

__________________________________
Client Sponsor
Confidential

Page 8

10/6/2016

Project Charter

10 APPENDICES

10.1 Document Guidelines

10.2 Project Charter Document Sections Omitted

Confidential

Page 9

10/6/2016