Project Charter

xxxxxxxxxxxxxxxxxxxxxxxx
Version 1.0 )

Mei 2xxx

This document contains proprietary information that is confidential to xxx. Disclosure of this document in full or in part, may result in material damage to xxxxxx. Written permission
must be obtained from xxxxxxxxx prior to the disclosure to a third party.
 Document Information & Revision History

File Name Project Charter

Original Author(s) xxxxxxxxxxxxxxxxxxxxxxxx

Current Revision Author(s) xxxxxxxxxxxxxxxxxxxxx

Version Date Author Revision Notes

0.0.0.0 dd-mm-yyyy Draft Project Charter

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Draft Copy (Mar 2006) Page 2 Private & Confidential

11/4/2018 8:33 AM
 Table of Contents

1. Background
2. Goals & Objectives
3. Project Scope
4. Project Approach
5. Project Deliverables
6. Key Assumptions
7. Key Risks & Management Strategies
8. Project Organisation
9. Key Roles and Responsibilities
10. High Level Project Plan
11. External Dependencies
12. Milestones Summary
13. Budget
14. Cost & Benefit Analysis

Draft Copy (Mar 2006) Page 3 Private & Confidential

11/4/2018 8:33 AM
 1. Background

STRATEGIC BUSINESS VALUE

Berisi strategis bisnis yang akan di capai

SOLUTION CHARACTERISTICS

Karakteristik proyek yang akan dicapai

Draft Copy (Mar 2006) Page 4 Private & Confidential

11/4/2018 8:33 AM
 2. Goals & Objectives

Goal:
– Melakukan perubahan, perbaikan dan penyesuaian penjualan lewat internet
– Meminimalisir permasalah yang mungkin timbul dalam administrasi pergudangan
– Mempermudah support teknis

Objectives:
Tujuan pengembangan sistem
1.
2.
3.

Draft Copy (Mar 2006) Page 5 Private & Confidential

11/4/2018 8:33 AM
 3. Project Scope

No PRODUCT FEATURES SERVICES

1 Nama module 1. Asal data

2. Pelayanan yg akan dicapai
3. Waktu pelayanan
4. Kegiatan lainnya

Draft Copy (Mar 2006) Page 6 Private & Confidential

11/4/2018 8:33 AM
 3. Project Scope (Cont’d)

No Product Features Services

Datawarehouse

Draft Copy (Mar 2006) Page 7 Private & Confidential

11/4/2018 8:33 AM
 3. Project Scope - Exclusions

The scope of the project EXCLUDES:

EXCLUSION COMMENTS
Perubahan, perbaikan dan penyesuaian Apabila terdapat perubahan ketentuan aplikasi xxxxx
program Aplikasi xxxxx berpedoman perlu di sampaikan secara tertulis
ketentuan yang berlaku saat ini dan belum
termasuk perubahan yang disebabkan adanya
ketentuan aplikasi xxxxx yang baru

Draft Copy (Mar 2006) Page 8 Private & Confidential

11/4/2018 8:33 AM
 4. Project Deliverables

Draft Copy (Mar 2006) 9

 4. Project Deliverables (cont’d)

Functional Specifications Document (FSD)

Documentation of both functional and non-functional requirements of the application module to support the intended business area
needs. It describes the overall processes supported by the application module and its detail requirements covering functional, data,
security & controls, interfaces, general ledger entries, agreed gaps resolution and etc. This document will form baseline input for
subsequent implementation activities such as design, customization, and testing of the application module.

Technical Specification Document (TSD)

This Technical Specification Document (TSD) provides a documentation of the technical specification, which derived from FSD. It
describes the overall technical design for development, which cover the technical attribute, technical architecture, technical flow
diagram, technical logic, security and control design, user interface, operating specification, and reporting.
Testing Management Plan
Testing Management Plan contains all the activities planned in order to ensure quality testing that ensures fulfillment of the
Requirements (FSD & TSD). Testing Management Plan will be reviewed for impact on the completion of Requirement definition and
design stage and shall be updated accordingly. The solution tested by nominated user representatives to ensure that the delivered
solution is as per the agreed FSD & TSD, incorporating all system agreed customizations and interfaces requirements. SIT & UAT is to
ensure that the project’s User Requirements are validated through testing of the system online, batch, reporting and interfaces
functionality using actual business scenarios on an end-to-end manner

Draft Copy (Mar 2006) 10

 4. Project Deliverables (cont’d)

Test Design
Identifying Test conditions and Design Test Cases

Train the Trainers

Nominated trainers from the users group will be trained by the project team on the solution.

Documentation (e.g. PTO, Operations Manual, etc)

Petunjuk Teknis Operasional (PTO) describes and explain in detail the functionalities provided by the system for each banking
application. The UIM will guide the users how to setup the parameters tables to generate the banking products that the xxxx wishes to
market to the customers.

Operations Manual provides the information necessary for the xxxx users to understand and operate the business processes in the
new environment. The manual will cover all operational procedures including the xxxx’s policies, transaction workflows, security and
control procedures, reporting requirements, etc.
“Migration Ready” Environment
The vendors/developer solution have been fully tested and is ready for migration to the xxxx’s production environment.

Draft Copy (Mar 2006)

11 Project Charter
 4. Project Deliverables
Responsibility Assignment Matrix Chart

RAM CHART ROLE

Related Program Product PMO Service IT Service Project Co-Project Reviewer Unit Kerja
NO DELIVERABLE Committee Manager Owner Manager Owner Owner Manager Manager Terkait

A. Solution Definition

Project Charter A R C C C R C C

Procurement
A C C C R C
Management Plan

Functional
Specifications C A C C C R C C
Document (FSD)

Technical
Specifications C C A C R
Document (TSD)

Keterangan:
R = Responsible A = Accountable C = Consult

Draft Copy (Mar 2006) 12

 5. Key Assumptions

1. Jadwal proyek telah disepakati oleh seluruh pihak yang berkepentingan dan dilengkapi dengan tanggal
mulai dan berakhirnya aktifitas.
2. Bank memastikan infrastruktur tersedia pada waktu integrated testing dan production.
3. Adanya variasi dan perubahan dalam scope product dan service yang telah ditawarkan akan berpengaruh
kepada keseluruhan timeframe waktu project dan biaya.

Draft Copy (Mar 2006) Page 13 Page 13

 6. Key Risks & Management Strategies

Risk Identification Risk

Risk Trigger Preventive Contingency Due Date PIC
Statement Cause Impact Score

• Risiko kegagalan •Baru pertama kali •Hasilnya tidak •Sedang Requiremen •Memastikan •Melakukan dd/mm/yyyy •Project
/kelemahan dalam menggunakan sesuai dengan t tidak sesuai requirement dalam enhancement Manager
system aplikasi sistem yang IR telah diakomodir sistem / aplikasi
Traffic
sesuai kebutuhan
diharapakan padat / tinggi •Backup &
•Risiko kegagalan •Belum dilakukan •sedang •Melakukan
System proses migrasi PTR •Rollback
penambahan
upgrade/penamba kapasitas server
•Kegagalan han kapasitas
bandwidth
interface

Risiko kesalahan Kurang informasi Terjadi •sedang Kesalahan Tersedianya PBI, •Memberikan dd/mm/yyyy •Project
dalam dalam kesalahan penggunaan SOM,petunjuk pelatihan, Manager
Process / mengoperasikan mengoperasikan dalam aplikasi pelaksanaan modul bimbingan &
aplikasi pengawasan
Procedures module aplikasi aplikasi mengoperasika
langsung
n aplikasi

•Risiko tidak •Kekurangan •Waktu •sedang Sumber •Melakukan analisa •Menambah dd/mm/yyyy •Project
tersedianya/kurang sumber daya pengerjaan daya mengenai sumber daya Manager
nya resources manusia karena menjadi lebih berkurang, kebutuhan manusia
waktu lebih manning dalam
untuk menjalankan efisiensi lama •Memberikan
lama project
project •sedang arahan &
People Perkemban •Memberikan petunjuk
•Risiko gan project training/sosialisasi kewenangan
•Kurangnya •Tidak
pelanggaran/pelam terhambat kepada user lebih jelas
kerjasama antara terkoordinasi
pauan kewenangan
unit kerja
dalam memutus

Risiko terjadinya Kejadian Kehilangan •sedang Bencana Tersedianya •Melakukan dd/mm/yyyy •Project
kebakaran atau alam/bencana data alam Backup system restore data dari Manager
bencana alam alam sebagai pedoman backup harian /
operational dalam bulanan
External Factor lainnya
keadaan Disaster
Risiko terjadinya
perubahan
ketentuan BI

Draft Copy (Mar 2006) Page 14

 7. Project Organization

Steering Committee

Program Manager Service Owner

Release Control Board

Product Owner Reviewer

Project Manager

Co Project Manager
PMO Manager IT Service Owner
)

Functional Team Technical Team

Testing Team
Support Team

Vendor

Draft Copy (Mar 2006) Page 15

 8. Key Roles and Responsibilities

Related Committee Product /Service Owner

• Sets high-level direction of the Program/Project accordance with • Appointed senior representative of the products and services
Bank Mandiri portfolio (Wholesale Banking Committee, Retail implemented in the Program/Project
Banking Committee, Corporate Center & Shared Service • Approves project deliverables as defined in Key Project
Committee) Milestone Signoff
• Ensures the objectives of the Program/Project are aligned to the • Provides expert products and services understanding of the
business priorities defined in the Strategic Business Plan organization
• Periodically reviews progress towards achievement of program • Takes ownership for the functional quality of the products and
and business objectives services implemented
• Resolve any major conflicts or policy changes that the • Provides high-level direction for the business aspects of the
Program/Project Committee cannot resolve project
• Provides business justification for the project and for any
Program Manager subsequent changes to its scope
• Has overall day to day basis responsibility for ensuring the • Helps resolve conflicts over policies and procedures relating to
success of the overall program/project the product/services
• Controls the day to day aspects of the Program/Project • Makes user resources available
• Confirms project deliverables
• Performs program management processes
• Develops Program/Project Charter and Plan
• Participates in formal review and management review
presentations
• Tracks Program/Project action items and issues.
• Provides accurate and timely reporting of the Program/Project
• Responsible for administrative coordination of Program/Project

SDF1.1-16

Draft Copy (Mar 2006)

 8. Key Roles and Responsibilities
Reviewer
• Internal Audit , Review the project deliverables to ensure it comply
with bank Policy & Procedure
• Compliance Group, Review the project deliverables to ensure it
comply with bank Policy & Procedure, provide Compliance Opinion
and signoff project deliverables as defined in Key Project Milestone
Project as Reviewer.
• Operasional Mgmnt, Review the operational risk identification and
mitigation of project implementation, carried out advocacy to
increase risk awareness and operational risk management
capabilities when required and sign off project deliverables as
stated in the Key Project Milestone Project
• Operasional Risk Coordinator as facilitators for the Unit of Work
to identify and mitigate operational risk IT projects end-to-end in
accordance with applicable regulations.
• Unit of Policy, System and Procedures, ensuring alignment of
technology and operational systems that are used / developed in
line with the applicable regulations.
Project Manager
• Controls the day to day aspects of the project
• Responsible for timely and quality delivery of project deliverables
• Approve project deliverables as defined in Key Project Milestone
Signoff
• Performs project management processes
• Develops Project Charter and Project Plans
• Executes formal reviews and management reviews
• Tracks and disposes of issues
• Tracks action items
• Provides timely and accurate reporting of the project status and
project performance
Draft Copy (Mar 2006)
Co Project Manager
• Assist PM in responsible for the delivery of project deliverables
• Controls the day to day aspects for IT content in the project
• Approve project deliverables as defined in Key Project Milestone
Signoff
• Develops Technical Specifications Document, responsible for System
Integration Test readiness and Migration readiness
• Support on System Integration Test and User Acceptance Test
• Tracks and disposes of issues
IT Service Owner
• Owner and approval authority of policy on any IT issue include Security,
Testing along with Deployment.
• Approves project deliverables as defined in Key Project Milestone
Signoff
• Review and final approval on IT policy (include Security, Testing along
with Deployment) as needed for the project implementation
• Review and final approval at risk acceptance level
• Validate the solution
• Assign representative
PMO Manager
• Monitor and Coordinate all project deliverable to comply with bank
Standards.
• Review all project progress and recommend appropriate actions to
respective parties.
• Ensure the Project Management comply with Bank Standards.
• Approve project deliverables as defined in Key Project Milestone
Signoff
 8. Key Roles and Responsibilities

Technical Team Testing Team

• Provide technical solutions and communicate the user requirement to • Evaluate project requirements and identify testing requirements
developer. • Create Test Management Plan (TMP) to address the testing
• Provide and setup IT infrastructure needs of the project
• Support testing activities • Present the TMP to project team (stakeholders, PM, Co-PM,
• Migrate existing solution and data source from 3rd party (if Any). Vendor, PMO) and finalize the TMP
• Setup production user profile • Produce test cases in order to functionally test a software
• Support post production activities in command center development.
• Carry out test activity in accordance with the plans and
Support Team schedules established
• Support project activities • Provide accurate and complete records of testing activity with
associated evidence
Functional Team/ Business Analyst • Monitor & control the design & execution phase of Functional
• Collect & confirm user requirements and documenting the status of and Non Functional --if exist -- testing to ensure testing is
development solution conducted as per the agreed TMP
• Monitor documentation on Training , UIM & SOM • Assist in the resolution of issues and problems encountered
• Provide deployment plan during test execution that impact the quality and efficiency of the
• Workshop testing process.
• Support testing activities • Identify and report on defects found during test execution
• Support Training & Rollout activity.
• Identify, evaluate and mitigate operational risk assessment • Produce Testing Report
• Support environment testing set up

Draft Copy (Mar 2006)

 8.Key Roles and Responsibilities
Program Manager Functional Team/Business Analyst
• Senior representative dari IT • Me-monitor dokumentasi status
• Memberi arahan manajemen untuk pemilihan dan • Menyedikan deployment plan
implementasi solusi yang memenuhi kebutuhan bisnis. • Workshop and SIT
• Memberi arahan untuk IT architecture dan rencana • Support Training
implementasi Solusi berdasar kebutuhan bisnis dan prioritas • Mengumpulkan dan mengkonfirmasikan “ User
• Koordinasi implementasi Solusi dengan Group lain di dalam Requirements
perusahaan dan dengan Vendor External
Project Manager
Product Owner • Mengatur aktivitas project
• Owner dan otoritas persetujuan solusi • Konfirmasi Solusi atas user requirements
• Persetujuan final untuk user requirements yang perlu • Validasi keseluruhan project berkaitan dengan
diimplementasikan pada project. dokumentasi dan solusi.
• Validasi solusi
PMO Manager
• Menunjuk perwakilan • Koordinasi team project Team untuk memenuhi
Service Owner kebutuhan project (deliverables, UAT, etc)
• Owner and otoritas persetujuan untuk menyetujui kebijakan • Monitoring project status progress dan sign-off.
perusahaan Technical Team
• Review and persetujuan final kebijakan bank yang perlu • Mempersiapkan IT Infrastructure
diimplementasikan pada project • Memindahkan solusi yang sudah ada dan sumber data
• Validasi solusi dari pihak ketiga ( jika ada )
• Menunjuk perwakilan • Membuat profile dari production user
IT Service Owner • Mendukung aktivitas produksi di Command Centre
 Bertindak sebagai Owner dan mempunyai kekuasaan untuk Business Reviewer
menyetujui segala macam bentuk peraturan dan IT Issue • Mereview business process dan memberikan
 Memeriksa dan menyetujui segala macam bentuk kebijakan rekomendasi perbaikannya dalam Blue Print serta
IT yang diperlukan untuk implementasi project mengkomunikasikan kepada Product Owner terkait
 Memeriksa dan menyetujui pada level Risk Acceptance
• Bekerja sama dengan Project Manager untuk
 Memeriksa ulang segala solusi yang ada
 Menunjuk perwakilan mengendalikan issue project dan resiko yang terkait
dengan perbaikan Business process
Draft Copy (Mar 2006) Page 19 Private & Confidential
11/4/2018 8:33 AM
 9. High Level Project Plan
Proposed by Pengembang for Release 1
Mei’06 Juni’06 July’06 Agst ’06 Sept 06

Joint Discussion

01/03 07/03
Develop RFP

04/04
08/03 Project Charter

05/04 20/04
Develop FSD

21/04 04/05
Development

05/05 09/06
SIT & UAT

12/06 23/06
SE & SOM

12/06 30/06
Implementation

26/06 30/06
Draft Copy (Mar 2006) Page 20 Private & Confidential
11/4/2018 8:33 AM
 10. External Dependencies

• External vendors’ capability in readying …… infrastructure, including, but not limited

to, physical processing infrastructure, resource capability, telecommunications
network and security infrastructure, policies and procedures, audit and controls, etc.
• External vendors’ capability in providing system interfaces and fulfill other system
functions and requirements (as per agreed and stated in the FSD) to …. Systems.

Draft Copy (Mar 2006) Page 21 Private & Confidential

11/4/2018 8:33 AM
 11. Milestone Summary

Milestones Components Signatories Target Date

Project Charter Project Charter Sign-Off MD related dd/mm/yyyy

Program Manager
Product/Service Owner
Reviewer
IT Service Owner
PMO Manager
Project Manager

Request for Proposal Request for Proposal Program Manager dd/mm/yyyy

Sign-off Product Owner
IT Service Owner
PMO Manager
Project Manager

Procurement Procurement Management Plan Program Manager dd/mm/yyyy

Management Plan Sign-off Product Owner
IT Service Owner
Project Manager

Draft Copy (Mar 2006) Page 22

 11. Milestone Summary
Milestones Components Signatories Target Date

Procurement Copy of Contract / SPK As per xxxxx ‘s Procurement Circular dd/mm/yyyy

Letter

Functional Specifications Functional Specifications Program Manager dd/mm/yyyy

Document (FSD) Document (FSD) Sign-Off Product Owner
Service Owner
Reviewer
IT Service Owner
PMO Manager
IT Planning – IT Security
Project Manager

Technical Specification Technical Specification IT Service Owner dd/mm/yyyy

Document (TSD) Document (FSD) Sign-Off PMO Manager
IT– Security
Project Manager

Testing Management Plan TMP, QQMP, DMP Sign-off IT Service Owner dd/mm/yyyy
Quality Management Plan Project Manager

Deployment Management Plan

Draft Copy (Mar 2006) Page 23

 11. Milestone Summary
Milestones Components Signatories Target Date

SI Tested Solution System Integration Tested Solution Sign- Program Manager dd/mm/yyyy
Off by IT Service Owner
Project Manager
PMO Manager

UAT Tested Solution UAT Tested Solution Sign-Off Program Manager dd/mm/yyyy
(Full System Delivery Product/Service Owner
for UAT) Reviewer
IT Service Owner
IT SAP- Security
PMO Manager
Project Manager

Training Training Material Program Manager dd/mm/yyyy

Product Owner
PMO Manager
IT Service Owner
Project Managers

Draft Copy (Mar 2006) Page 24

 11. Milestone Summary

Milestones Components Signatories Target Date

“Migration Ready” “Migration Ready” Environment Sign- Program Manager dd/mm/yyyy

Environment Off Product Owner
IT Service Owner
IT Operations – IT Data Center &
DRC
PMO Manager
Project Manager
Live Implementation Live Implementation Sign Off Director of TOP + MD/SEVP related dd/mm/yyyy
Confirmation note that all necessary Program Managers
milestones have been completed: Product Owner
Charter, FSD, SI Tested Solution, Services Owner
UAT Tested Solution, Updated Services Owner -
SUG, Migration Ready
IT Service Owner
Environment
Reviewer
PMO Manager
Project Manager

Draft Copy (Mar 2006) Page 25

 12. Budget

Rencana Anggaran Investasi ( Dalam USD atau Rupiah Penuh)

No Jenis USD Rupiah

1 Hardware

2 System Software

3 Application Software

4 Peripheral

5 Lain-lain

Total

Draft Copy (Mar 2006) Page 26 Private & Confidential

11/4/2018 8:33 AM
 12. Budget

Rencana Anggaran Eksploitasi ( Dalam USD atau Rupiah Penuh)

No Jenis USD Rupiah

1 Maintenance Hardware
2 Maintenance System Software
3 Maintenance Application Software
4 Maintenance Peripheral
5 Sewa Hardware/ Peripheral
6 Sewa Software
7 Sewa Jaringan

8 Hosting

9 Konsultan

10 Training & Sosialisasi

11 Perjalanan Dinas

12 Lain-lain

Total

Draft Copy (Mar 2006) Page 27 Private & Confidential

11/4/2018 8:33 AM
 14. Cost & Benefit Analysis

Benefit/ Cost (Dalam USD atau Rupiah Penuh)

Keterangan
Thn 1 2 3 4 5 dst TOTAL
1. Benefit (revenue/ cost saving)

2. Cost (expenditure)

a. Capital Expenditure

b. Operating (exl. depreciation)

Net Cash Flow ( 1 – 2 )

Discount Factor **)

Net Present Value Cash Flow

Draft Copy (Mar 2006) Page 28 Private & Confidential

11/4/2018 8:33 AM