0
Projet Charter
Posted by jujur
on
8:50 PM
Put here the project name
Project Charter
[Note: This document serves as a
guideline. Format/ table of content of this guideline can be modified, as long
as contents of this guideline are covered by the new modified document. In case
the format of this document is altered, the reason of changes should be
documented on separated document. All blue text is optional. Its value can be
changed to any intended value. Change the color to black if you do.]
Prepared By
Put
here full name of document author
Charter
No: Put here the charter number
COMPANY NAME
Put
here issued date
Put
here the version number
Table of Contents
[Do not forget to update TOC after document is developed
or updated.]
[Berisi penjelasan singkat mengenai
keseluruhan proyek. Yang termasuk didalamnya adalah tujuan proyek, tujuan dan
keuntungan bagi bisnis, produk yang dihasilkan dan tanggal-tanggal penting]
1.1. Tujuan Proyek
[Menjelaskan latar belakang proyek dan bagaimana proyek
diinisiasi. Menjelaskan tujuan bisnis secara keseluruhan]
1.2. Ruang Lingkup Proyek
1.2.1. Penjelasan Ruang Lingkup
[Menjelaskan
hal-hal yang termasuk kedalam proyek dan hal-hal yang tidak termasuk kedalam
proyek. Beberapa pertanyaan yang harus dijawab adalah:
·
Fungsi atau layanan yang harus dihasilkan
·
Batasan Proses
·
Fungsi bisnis yang masuk kedalam ruang lingkup
]
1.2.2. Pengelolaan Ruang Lingkup
[Penjelasan
mengenai bagaimana cara mengelola perubahan ruang lingkup proyek]
1.3. Tujuan Proyek
1.3.1. Tujuan Bisnis
[Berisi tujuan bisnis yang ingin dicapai dari
dijalankannya proyek ini]
1.3.2. Tujuan Teknologi Informasi
[Berisi tujuan IT yang ingin dicapai dari dijalankannya
proyek ini]
1.3.3. Tujuan Eksekusi Proyek
[Berisi sasaran eksekusi proyek ini diantaranya:
·
Menjalankan proyek dengan fungs dan kapabilitas
yang diinginkan
·
Mengeksekusi proyek yang tepat waktu
·
Menjalankan proyek yang sesuai anggaran]
2.1. Hasil Pekerjaan Proyek dan Sasaran Kualitas
2.2. Organisasi, Tanggung Jawab dan Pihak yang Berkepentingan
[Menjabarkan daftar tim proyek dan pihak-pihak yang
berkepentingan terhadap proyek ini diantarany:
·
Project sponsor
·
Project Functional Lead
·
Project Technical Lead
·
Project Manager
·
Project Steering Committee
·
Project Team Member
·
Stakeholder]
2.3. Resiko
[Berisi identifikasi resiko proyek, resiko produk/layanan,
dan permasalahan lainnya]
|
No
|
Date
Raised |
Phase of the Project
|
Risks
|
Mitigation Actions
|
PIC
|
|
1
|
19-Aug-05
|
|
Resource
downtime (sick, accident, unprecedented leave, etc)
|
e.g.
1. Make sure all leave request should be submitted 2 weeks before D-Day. 2. Get together all team members about unprecedented leave… |
Project
Leader
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2.4. Jadwal Proyek
[Berisi daftar milestone dari proyek, termasuk
didalamnya tanggal penyelesaian dari setiap fase]
|
No
|
Date
|
Phase of the Project
|
Activity
|
|
1
|
6-Jun-12
|
Project Planning
|
In the
project planning, Company’s team will prepare the resources required and
qualified for the project in term of human resources, hardware, and software.
The formal project kick off will be conducted within this phase in which its
main deliverables is detailed Project Schedule.
|
|
2
|
20-Jun-12
|
Analysis
|
During
analysis phase, Business Analyst will redefine the evolving client’s
requirement into more detailed Software Requirement Specification (SRS). The
requirement will be organized through a Change Management System. The final
SRS will be reviewed by both Project Owner and Project Manager to identify
the feasibility of the client’s requirements. The requirements will also be
analyzed for balance and verifiability using Test Scenarios
|
|
|
|
Design
|
|
|
|
|
dst…
|
|
|
|
|
|
|
2.5. Estimasi Biaya dan Keuntungan
|
Profitabilitas Proyek
|
|
|
Pendapatan keseluruhan untuk Perusahaan:
|
|
|
Pengeluaran Keseluruhan:
|
|
|
Keuntungan sebelum Pajak (Pendapatan dikurang Pengeluaran):
|
|
|
BIAYA LANGSUNG
|
|
|
|
|
|
|
BERDASARKAN POSISI
|
BIAYA
|
||||
|
Project Manager
|
|
||||
|
Project Leader
|
|
||||
|
Business Analyst
|
|
||||
|
Software Designer
|
|
||||
|
Web Designer
|
|
||||
|
Database
Administrator
|
|
||||
|
Software Engineer
|
|
||||
|
Software Tester
Coordinator
|
|
||||
|
Software Tester
|
|
||||
|
Technical Writer
|
|
||||
|
Total Biaya Per Bulan
|
0
|
||||
|
|
|
|
|
|
|
|
BASED ON PHASE
|
Month
|
Total
|
|||
|
<M1>
|
<M2>
|
<M3>
|
<M4>
|
||
|
Project Initiation
|
|
|
|
|
0
|
|
Project Planning
|
|
|
|
|
0
|
|
Analysis
|
|
|
|
|
0
|
|
Design
|
|
|
|
|
0
|
|
Construction
|
|
|
|
|
0
|
|
Validation
|
|
|
|
|
0
|
|
Release & UAT
|
|
|
|
|
0
|
|
Implementation
|
|
|
|
|
|
|
Total Orang per Bulan
|
0
|
0
|
0
|
0
|
0
|
|
|
|
|
|
|
|
|
BIAYA LAINNYA
|
|
|
|
|
|
|
ITEMS
|
Biaya
|
|
|
||
|
Software Investment
|
|
|
|
||
|
Hardware Investment
|
|
|
|
||
|
Traveling
|
|
|
|
||
|
Third Party Fee
|
|
|
|
||
|
Training
|
|
|
|
||
|
Others
|
|
|
|
||
|
Total
|
0
|
|
|
||
[Proyek dikerjakan seringkali melibatkan berbagai macam
pihak, oleh karena itu komunikasi efektif perlu dijalankan. Pada bagian ini
dimasukan mekanisme komunikasi yang digunakan saat menjalankan proyek]
|
No
|
Jenis Komunikasi
|
Mekanisme Pelaksanaan
|
Peserta Yang Hadir
|
|
1
|
Rapat Komite Pengendalian
|
Dilakukan apabila terjadi,…..
|
Project
Sponsor, Project Manager, dsb
|
|
2
|
Rapat Tim Proyek
|
|
|
|
3
|
Rapat Review
|
|
|
|
4
|
….
|
….
|
…
|
[Lampiran berupa dokumen Rencana Proyek dan Jadwal Proyek]
