Tugas 1 Manajemen Proyek ii
TUGAS 1
MATA KULIAH MANAJEMEN PROYEK
Dosen : Rayi Pradono Iswara, Ir., M.Sc
Oleh :
MUHAMAD RAMDANI (1113091000016)
FAKULTAS SAINS DAN TEKNOLOGI
JURUSAN TEKNIK INFORMATIKA
UNIVERSITAS ISLAM NEGERI JAKARTA
2016
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
PROJECT MANAGEMENT PLAN
UNTUK
SISTEM PENGELOLAAN BARANG ONLINES
REVISI 0
22/04/2014
Team Name
Team Member 1
Team Member 2
Team Member 3
Team Member 4
Team Member 5
Team Member 5
: Web Builder Squad (WBS)
: Muhamad Ramdani
: Hamzah dua
: Hamzah tiga
: Hamzah empat
: Hamzah lima
: Hamzah enam
ii
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
SPBO-00
iii
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
RECORD OF CHANGES
*A - ADDED M - MODIFIED D – DELETED
VERSION
NUMBER
1.0
DATE
22/04/2016
NUMBER OF
FIGURE, TABLE
OR PARAGRAPH
A*
M
D
TITLE OR BRIEF DESCRIPTION
CHANGE
REQUEST
NUMBER
-
-
Pembuatan dokumen
-
iv
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
TABLE OF CONTENTS
Section
Page
SECTION 1. OVERVIEW ........................................................................................................................ 1
1.1
Project Summary ........................................................................................................................ 1
1.1.1
Purpose, Scope, and Objectives ........................................................................................... 1
1.1.2
Assumptions and Constraints .............................................................................................. 1
1.1.3
Project Deliverables ............................................................................................................ 2
1.1.4
Master Schedule and Budget Summary ............................................................................... 2
1.2
Evolution of the Plan .................................................................................................................. 2
1.3
Document Structure .................................................................................................................... 2
SECTION 2. REFERENCES..................................................................................................................... 4
2.1
Standards and Documents ........................................................................................................... 4
SECTION 3. DEFINITIONS ..................................................................................................................... 5
SECTION 4. PROJECT ORGANIZATION .............................................................................................. 6
4.1
External Interfaces ...................................................................................................................... 6
4.2
Internal Structure ........................................................................................................................ 6
4.2.1
The Project Manager ...........................................................Error! Bookmark not defined.
4.3
Project Roles and Responsibilities .............................................................................................. 6
SECTION 5. MANAGEMENT PROCESS ............................................................................................... 7
5.1
Start-up ....................................................................................................................................... 7
5.1.1
Estimation ........................................................................................................................... 7
5.1.2
Staffing ................................................................................................................................ 7
5.1.3
Resource Acquisition .......................................................................................................... 7
5.1.4
Staff Training ...................................................................................................................... 7
5.2
Work Planning ............................................................................................................................ 7
5.2.1
Work Activities ................................................................................................................... 7
5.2.2
Schedule Allocation ............................................................................................................ 7
5.2.3
Resource Allocation ............................................................................................................ 7
5.2.4
Budget Allocation ............................................................................................................... 8
5.3
Project Controls .......................................................................................................................... 8
5.3.1
Requirements Control .........................................................Error! Bookmark not defined.
5.3.2
Schedule Control .................................................................Error! Bookmark not defined.
5.3.3
Budget Control ....................................................................Error! Bookmark not defined.
5.3.4
Quality Control ...................................................................Error! Bookmark not defined.
5.3.5
Project Reporting and Communication ...............................Error! Bookmark not defined.
5.3.6
Metrics Collection ...............................................................Error! Bookmark not defined.
5.4
Risk Management ....................................................................................................................... 8
5.5
Project Closeout .......................................................................................................................... 8
SECTION 6. TECHNICAL PROCESS ..................................................................................................... 9
6.1
6.2
6.3
6.4
Process Model............................................................................................................................. 9
Methods, Tools and Techniques ................................................................................................. 9
Project Infrastructure .................................................................................................................. 9
Product Acceptance .................................................................................................................... 9
v
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
SECTION 7. SUPPORTING PROCESSES............................................................................................. 10
7.1
Configuration Management ...................................................................................................... 10
7.2
Independent Verification and Validation .................................................................................. 10
7.3
Documentation.......................................................................................................................... 10
7.4
Quality Assurance ..................................................................................................................... 10
7.5
Reviews and Audits .................................................................................................................. 10
7.6
Problem Resolution .................................................................................................................. 10
7.7
Contractor Management ........................................................................................................... 10
7.7.1
Contracting Process .............................................................Error! Bookmark not defined.
7.7.2
Contractor Performance Monitoring....................................Error! Bookmark not defined.
7.8
Process Improvement ................................................................................................................ 10
7.8.1
Systems/Software Process Improvement Lead ....................Error! Bookmark not defined.
7.8.2
Systems Engineering Process Group ...................................Error! Bookmark not defined.
SECTION 8. ADDITIONAL PLANS ..................................................................................................... 11
APPENDIX A. SPBOMASTER SCHEDULE (MICROSOFT PROJECT) ............................................... 2
APPENDIX B. SPBOFACILITIES PLAN ................................................................................................ 3
APPENDIX C. SPBOPROJECT TRAINING PLAN ................................................................................ 4
APPENDIX D. SPBOMEASUREMENT PLAN ....................................................................................... 5
APPENDIX E. SPBOPRODUCT ENGINEERING AND QUALIFICATION PROCESS ....................... 6
APPENDIX F. SPBOQUALITY ASSURANCE PLAN ........................................................................... 7
APPENDIX G. SPBOCONFIGURATION MANAGEMENT PLAN ....................................................... 8
LIST OF FIGURES
Figure
Page
LIST OF TABLES
Table
Page
Table 7-1. SPBO Documentation ............................................................................................................. 10
vi
SPBO PMP
SPBO 01
23/04/2016
SECTION 1. OVERVIEW
1.1
1.1.1
PROJECT SUMMARY
Purpose, Scope, and Objectives
Pertokoan tidak bisa dipisahkan dari mengirim dan menerima barang, segala
kegiatan suatu produk harus di catat agar tidak terjadi kerugian karena kehilangan data,
barang yang masih ada namun tetap ditambahkan, dan barang sudah kadaluarsa tapi
masih diperjual belikan yang akan mempengaruhi kepercayaan pembeli. Namun, tidak
semua toko menerapkan pengelolaan barang berbasis teknologi dan masih menggunakan
pembukuan manual. Dengan menganalisa gejala tersebut, dapat ditarik kesimpulan
mengenai peluang pengembangan aplikasi pengelolaan barang berbasis web online yang
diterapkan di setiap jenis toko.
Pengembangan sistem ini dimaksudkan untuk meningkatkan kinerja dari
pertokoan biasa menjadi pertokoan yang berbasis teknologi informasi kedepannya.
Objektif dari proyek ini yaitu :
1.1.2
Menambah daftar supplier dan produknya
Menampilkan daftar barang yang dimiliki
Mengedit dan menghapus data barang
Mencetak daftar supplier, barang, dan kegiatan barang yang masuk dan keluar
Assumptions and Constraints
Proyek akan direncanakan dengan beberapa asumsi berikut :
Arsitektur dari produk harus terbuka agar bisa ditambahkan fungsinya
Produk harus user-friendly
Proyek ini dibuat dengan bahasa pemrograman PHP, dan database MySQL
Proyek ini hanya akan memberikan komponen produk dari keseluruhan proyek
Produk ini bisa diakses di semua perangkat yang mendukung internet
Tim harus berkerja sama dalam menyelesaikan proyek
Memungkinkan penambahan sumber daya manusia dalam proyek
Proyek akan direncanakan dengan batasan berikut :
Anggaran
: Rp. 300.000.000
Waktu
: Dua bulan
1
SPBO PMP
SPBO 01
23/04/2016
Staff
: Pihak klien akan dibutuhkan untuk membantu menentukan kebutuhan,
dan detail desain untuk proyek.
Maintenance : Produk dapat di desain kembali saat maintenance sesuai biaya yang
ditentukan yaitu Rp. 50.000.000 /bulan.
1.1.3
Project Deliverables
Tim kami akan memberikan produk yang berupa software dan dokumentasi kepada pihak
klien dua bulan setelah proyek dimulai dan memberikan laporan hardcopy setiap minggu.
Dokumentasi yang berikan berupa instalasi software dan panduan untuk user.
1.1.4
Master Schedule and Budget Summary
Proyek ini memiliki beberapa jadwal:
rancangan proyek dasar
: satu minggu setelah proyek dimulai
prototype proyek pada localhost : lima minggu setelah proyek dimulai
Proyek ini memiliki anggaran sebesar Rp. 300.000.000. Sejak produk diberikan, biaya
maintenance akan dikenakan Rp. 10.000.000 setiap bulan.
Requirement Workflow
(1 minggu, 1 anggota, Rp.40.000.000)
Analysis Workflow
(1 minggu, 1 anggota, Rp.40.000.000)
Design Workflow
(1 minggu, 1 anggota, Rp.40.000.000)
1.2
Implementation Workflow
Testing Workflow
(1 minggu, 1 anggota, Rp.40.000.000)
(1 minggu, 1 anggota, Rp.40.000.000)
EVOLUTION OF THE PLAN
Perencanaan ini dipertimbangkan dengan laporan yang akan diberikan setiap minggu dan
hari yang tidak dijadwalkan jika dibutuhkan. pembaruan jadwal akan muncul setiap minggu.
Pemberitahuan yang terjadwal dan pembaruan tidak terjadwal dari rancangan akan
dikomunikasikan lewat e-mail kepada seluruh peserta proyek.
1.3
DOCUMENT STRUCTURE
This plan is organized as follows:
a. Section 1, Project Overview. This section provides an overview of the scope and objectives
of the project, the project’s assumptions and constraints, reference to the project deliverables,
schedule and budget, and a description of the evolution of the plan.
b. Section 2, References. This section provides a list of all documents, policies, templates,
processes, and other sources of information referenced in the plan.
c. Section 3, Definitions. This section contains the abbreviations and acronyms required to
properly understand this planning document.
d. Section 4, Project Organization. This section identifies interfaces to organizational entities
external to the project, the project’s internal organizational structure, and defines roles and
responsibilities for the project.
2
SPBO PMP
SPBO 01
23/04/2016
e. Section 5, Management Process. This section describes the planning, measurement,
tracking, reporting, risk control mechanisms needed to provide management control over the
technical processes and product quality, and appropriate project initiation and closeout
procedures.
f. Section 6, Technical Process. This section describes the technical solution in terms of a
process model and implementation methods, tools, and techniques to be used to develop the
various work products, plans for establishing and maintaining the project infrastructure, and
the product acceptance.
g. Section 7, Supporting Processes. This section describes processes that are employed to
facilitate and control the technical processes and the state of the product. These include, but
are not limited to, configuration management, verification and validation, documentation,
quality assurance, reviews and audits, problem resolution, and contractor management, and
methods to ensure continuous process improvement.
h. Section 8, Additional Plans. This section addresses the logistic support strategy to be applied
to increase the system’s operational effectiveness.
i. Appendix A. SPBO Master Schedule (Microsoft Project)
j. Appendix B. SPBO Facilities Plan
k. Appendix C. SPBO Project Training Plan
l. Appendix D. SPBO Measurement Plan
m. Appendix E. SPBO Product Engineering and Qualification Process
n. Appendix F. SPBO Quality Assurance Plan
o. Appendix G. SPBO Configuration Management Plan
3
SPBO PMP
SPBO 01
23/04/2016
SECTION 2. REFERENCES
2.1
STANDARDS AND DOCUMENTS
The standards and documents listed below are referenced in this document:
IEEE Standard 1058-1998 template,
Access information http://shop.ieee.org/store/product.asp?prodno=SS94690
IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans, IEEE 1998
Object‐Oriented & Classical Software Engineering, 7th edition, Stephen R. Schach, pg. 590‐594
4
SPBO PMP
SPBO 01
23/04/2016
SECTION 3. DEFINITIONS
SPBO – Sistem Pengelolaan Barang Online
5
SPBO PMP
SPBO 01
23/04/2016
SECTION 4. PROJECT ORGANIZATION
4.1
EXTERNAL INTERFACES
Pihak klien dari proyek ini adalah toko grosir yang dinamakan Toko Maju Jaya, yang
diwakili oleh bapak Bambang. Seluruh komunikasi antara klien dan tim difasilitasi oleh pihak
klien dan bisa juga dilakukan via e-mail.
4.2
INTERNAL STRUCTURE
Struktur internal dari tim dan peran masing-masing. Struktur tim dibuat secara hirarki,
yang pimpin oleh ketua tim, dan sisanya ditugaskan untuk setiap perannya.
Setiap anggota harus menghubungi technical writer dan team mentor yang akan
membantu untuk memproduksi dokumen yang baik dan membantu tim mencapai tujuannya.
Tim akan melakukan pertemuan mingguan dan komunikasi via e-mail sebagai tambahan.
4.3
PROJECT ROLES AND RESPONSIBILITIES
Terbagi menjadi dua, yaitu peran dan tanggung jawab yang di bagikan ke seluruh tim.
Dapat dilihat pada tabel berikut :
Peran
Tanggung jawab
Penanggung jawab
Ketua
Pemenuhan proyek sesuai dengan jadwal dan
anggaran yang ditentukan
Muhamad Ramdani
Requirement Workflow
Mencari kebutuhan sistem yang akan dirancang
Hamzah dua
Analysis Workflow
Menganalisa kebutuhan yang berhubungan
dengan proyek
Hamzah tiga
Design Workflow
Mendesain tampilan produk secara keseluruhan
Hamzah empat
Implementation Workflow
Penyatuan semua komponen produk menjadi
produk yang dapat dijalankan
Hamzah lima
Testing Workflow
Menguji produk dan mencari kesalahan dalam
sistem
Hamzah enam
6
SPBO PMP
SPBO 01
23/04/2016
SECTION 5. MANAGEMENT PROCESS
5.1
5.1.1
5.1.2
START-UP
Estimation
Telah diteapkan sebelumnya, total waktu pengembangan sekitar 2 bulan dan total anggaran
sebesar Rp. 300.000.000. gambaran tersebut di dapatkan oleh expert judgement dari analogi, dan
dibandingkan dengan proyek yang sama.
Staffing
Ketua tim dibutuhkan selama 2 bulan penuh, untuk minggu pertama dibutuhkan
kapasistas pengelolaan, dan minggu kedua dibutuhkan manager dan programmer. Hamzah
dibutuhkan 3 minggu pertama untuk system analysis dan desaigner dan 2 minggu terakhir
dibutuhkan programmer dan tester.
5.1.3
Resource Acquisition
Seluruh kebutuhan hardware, software dan tools yang berhubungan untuk proyek telah
tersedia. Produk akan diberikan kepada klien dan instalasi pada desktop komputer sebagai server.
5.1.4
Staff Training
Tidak ada penambahan latihan staff yang dibutihkan pada proyek ini.
5.2
5.2.1
WORK PLANNING
Work Activities and Schedule Allocation
Minggu 1
Bertemu dengan klien, dan menetapkan kebutuhan produk.
Minggu 2, 3
Produksi hasil analisis untuk produk. Menunjukan rancangan kepada klien. Produksi
software project management.
Minggu 4, 5
Hasil desain produk dan inspeksinya.
Minggu 6, 7, 8
Implementasi dan inspeksi produk, unit testing dan dokumentasi, integrasi setiap fungsi,
integration testing, product testing, dan inspeksi dokumen.
5.2.3
Resource Allocation
Empat anggota tim akan bekerja secara terpisah sesuai dengan tugas masing-masing.
Muhamad Ramdani akan memonitor progses keseharian dan anggota lainnya, dan bertanggung
jawab untuk kualitas keseluruhan, dan komunikasi dengan klien. Anggota tim akan berkumpul
setiap akhir hari dan mendiskusikan masalah dan progres. pertemuan formal akan dilaksanakan
setiap akhir minggu untuk melaporkan progses dan mennentukan jika terdapat perubahan. Risk
management menjadi tanggung jawab M. Ramdani.
Meminimalisir kesalahan dan memaksimalkan user-friendliness akan menjadi top priority
bagi M.Ramdani, dan keseluruhan tanggung jawab untuk dokumentasi dan memastikan itu selalu
up to date.
7
SPBO PMP
SPBO 01
23/04/2016
5.2.4
5.3
Budget Allocation
Requirement Workflow
Rp.50.000.000
Analysis Workflow
Rp.50.000.000
Design Workflow
Rp.50.000.000
Implementation Workflow
Rp.50.000.000
Testing Workflow
Rp.50.000.000
Lain-lain
Rp.50.000.000
Total
Rp.300.000.000
PROJECT CONTROLS
Adanya perubahan besar yang berdampak pada milestones atau anggaran harus disetujui
oleh Ramdani dan didokumentasikan. tidak ada jaminan qualitas personalia dari luar yang
bersangkutan.
Ramdani bertanggung jawab untuk memastikan proyek selesai tepat waktu dan tidak
melebihi anggaran. setiap pertemuan anggota tim akan mempresentasikan progres dan masalah
harian. Ramdani akan menentukan apakah progres mereka seperti yang diharapkan dan apakah
mereka mengikuti spesifikasi dari dokumen dan project management plan. setiap masalah besar
yang dihadapi oleh anggota tim harus secepatnya di laporkan kepada Ramdani.
5.4
RISK MANAGEMENT
Kerena kemungkinan kesalahan besar terdapat pada desain, pengujian ekstensif akan
dilakukan ketika design workflow. dan juga, pada awalnya setiap anggota tim akan menguji
setiap code dan menguji code yang lain. Ramdani bertanggung jawab dalam integration testing
dan product testing.
5.5
PROJECT CLOSEOUT
Tidak dapat digunakan disini.
8
SPBO PMP
SPBO 01
23/04/2016
SECTION 6. TECHNICAL PROCESS
6.1
PROCESS MODEL
Yang akan digunakan adalah Unified Process.
6.2
METHODS, TOOLS AND TECHNIQUES
Workflow akan dilakukan sesuai dengan Unified Process. Produk akan
diimplementasikan dalam pemrograman PHP.
6.3
PROJECT INFRASTRUCTURE
Produk akan dikembangkan dalam format HTML dan berbasis web, berjalan pada semua
perangkat yang dapat terhubung internet.
6.4
PRODUCT ACCEPTANCE
Penerimaan produk oleh klien yang akan dicapai melalui langkah dari Unified Process.
9
SPBO PMP
SPBO 01
23/04/2016
SECTION 7. SUPPORTING PROCESSES
7.1
CONFIGURATION MANAGEMENT
CVS akan digunakan pada semua artifacts.
7.2
INDEPENDENT VERIFICATION AND VALIDATION
Testing workflow akan dilakukan sesuai Unified Process.
7.3
DOCUMENTATION
Dokumentasi akan di produksi secara spesifik pada Unified Process.
TABLE 7-1. SPBODOCUMENTATION
Document Type
7.4
QUALITY ASSURANCE
7.5
REVIEWS AND AUDITS
Format Standard
Estimated
Page Count
Peer Review Type
Setiap Hamzah satu sampai lima akan menguji code satu sama lain, dan Ramdani akan
memimpin dalam integration testing. Pengujian produk ekstensif akan dilakukan oleh semua tim.
7.6
PROBLEM RESOLUTION
Setiap masalah besar yang dihadapi oleh anggota tim secepatnya dilaporkan pada Ramdani.
7.7
CONTRACTOR MANAGEMENT
Tidak dipergunakan disini.
7.8
PROCESS IMPROVEMENT
Semua aktivitas akan di diselenggarakan dalam persetujuan dengan klien untuk kemajuan dalam
1 bulan.
10
SPBO PMP
SPBO 01
23/04/2016
SECTION 8. ADDITIONAL PLANS
Komponen tambahan:
Keamanan
: Dibutuhkan password untuk menggunakan produk.
Pelatihan
: Pelatihan akan dilakukan oleh Ramdani pada waktu pemberian produk.
karena produk ini adalah penggunaan straight forward, 1 day mungkin cukup untuk
pelatihan. Ramdani akan menjawab pertanyaan tanpa biaya untuk penggunaan bulan
pertama.
Maintenance
: Perbaikan pemeliharaan akan dilakukan oleh tim tanpa biaya pada
bulan pertama. Kontrak yang berbeda akan di tarik mengenai perbaikan peningkatan.
11
SPBO PMP
SPBO 01
23/04/2016
APPENDICES
IEEE Std 1058-1998 Guidance
Annexes may be included, either directly or by reference to other documents, to provide supporting
details that could detract from the document if included in the body.
General Guidance
In this template, the following appendices are used for reference purposes only. It should not be assumed
that the referenced documents exist as an example.
Appendices -1
SPBO PMP
SPBO 01
23/04/2016
APPENDIX A. SPBOMASTER SCHEDULE (MICROSOFT PROJECT)
Guidance
The objective of the SPBOmaster schedule is to provide management with the task map and tracking tool
needed to guide the project in the performance of its mission.
The SPBOmaster schedule’s Microsoft Project representation of the WBS would be tailored from the
templates available from the SSC Pacific Process Asset Library (PAL) in the “SW-CMM Archive”. Draft
Microsoft Project templates are found under the “Process Assets by SW-CMM KPA”, “Software Project
Planning (SPP)” in the “Tools” section. These templates can be tailored up or down to meet specific
project needs.
Appendices -2
SPBO PMP
SPBO 01
23/04/2016
APPENDIX B. SPBOFACILITIES PLAN
Guidance
The objective of the SPBOFacilities Plan is to document the environmental needs of the project. These
needs include space, equipments, security, safety, support tools, and the staff necessary to maintain and
operate an environment needed for project operations.
The facilities requirements for projects vary broadly, often with several projects sharing both facilities
and computer resources. There currently are no templates available from the SSC Pacific PAL to assist
in developing a facilities plan. However, recommended issues to address in a Facilities Plan would
include, but not be limited to, the following list:
1. Facility Objectives/General Description
2. Facility Locations (i.e., Building Locations)
3. Facility Diagrams
a. Floor Plans (i.e., lab, work cubicles)
b. Environmental Requirements i.e. Heating, Lighting
4. Facilities Equipment Requirements
a. Equipment Lists (i.e., work stations, development, test)
b. Equipment Interface Diagrams
c. Space Equipment Layouts
d. Inspections and Records Requirements
5. Facilities Software Requirements
a. Software by Development/Test Host Equipment
b. Software by Workstation
6. Facilities Operating Personnel Requirements
7. Facilities Operating Personnel Training Requirements
8. Security Measures
a. Internal
b. External
9. Safety Measures
10. Maintenance Requirements (i.e., spaces, per equipment)
11. Facilities Performance Measurements
Appendices -3
SPBO PMP
SPBO 01
23/04/2016
APPENDIX C. SPBOPROJECT TRAINING PLAN
Guidance
The objective of the SPBOProject Training Plan is to develop the skills and knowledge of the project staff
so they can perform their roles effectively and efficiently.
The SPBOProject Training Plan would be tailored from the Department/Project Training Plan Template
available from the SSC Pacific Process Asset Library (PAL). The template is located in the “Process
Assets” sub-page under the “Organizational Training” PA in the “Plans” section. The template can be
tailored up or down to meet specific project needs.
Appendices -4
SPBO PMP
SPBO 01
23/04/2016
APPENDIX D. SPBOMEASUREMENT PLAN
Guidance
The objective of the SPBOMeasurement Plan is to develop and present the data needed to support project
management information needs necessary to ensure objective decision-making.
The SPBOMeasurement Plan would be tailored from the Software Measurement Plan Template available
from the SSC Pacific Process Asset Library (PAL) in the “SW-CMM Archive”. This template can be
found under the ”Process Assets by SW-CMM KPA”, “Software Project Tracking and Oversight
(SPTO)” KPA in the “Tools” section. The template can be tailored up or down to meet specific project
needs.
Appendices -5
SPBO PMP
SPBO 01
23/04/2016
APPENDIX E. SPBOPRODUCT ENGINEERING AND QUALIFICATION
PROCESS
Guidance
The objective of the SPBOProduct Engineering and Qualification (PE&Q) Process is to document the
processes comprising a technical solution for development, maintenance, test, and product qualification.
The SPBOPE&Q Process would be tailored from the Product Engineering and Qualification Process
available from the SSC Pacific Process Asset Library (PAL). The process is located in the “Process
Assets” sub-page under the “Technical Solution” PA in the “Process” section. The PE&Q Process can
be tailored up or down to meet specific project needs.
Appendices -6
SPBO PMP
SPBO 01
23/04/2016
APPENDIX F. SPBOQUALITY ASSURANCE PLAN
Guidance
The objective of the SPBOQuality Assurance Plan is to provide staff and management with objective
insights into processes and associated work products, ensuring their conformance to documented
requirements.
The SPBOQuality Assurance Plan would be tailored from the Quality Assurance Plan Template available
from the SSC Pacific Process Asset Library (PAL). The process is located in the “Process Assets” subpage under the “Process and Product Quality Assurance (PPQA)” PA in the “Plans” section. The
template can be tailored up or down to meet specific project needs.
Appendices -7
SPBO PMP
SPBO 01
23/04/2016
APPENDIX G. SPBOCONFIGURATION MANAGEMENT PLAN
Guidance
The objective of the SPBOConfiguration Management Plan is to establish and maintain the integrity of
SPBOwork products using configuration identification, configuration control, configuration status
accounting, and configuration audits.
The SPBOConfiguration Management Plan would be tailored from the Configuration Management Plan
Template available from the SSC Pacific Process Asset Library (PAL). The template is located in the
“Process Assets” sub-page under the “Configuration Management (CM)” PA in the “Plans” section.
The template can be tailored up or down to meet specific project needs.
Appendices -8
DOCUMENT CHANGE REQUEST (DCR)
Document Title: [[Project]] Project Management Plan
Tracking Number:
Name of Submitting Organization:
Organization Contact:
Phone:
Mailing Address:
DCR Description:
Date:
Change Location:
(use section #, figure #, table #, etc.)
Proposed change:
Rationale for Change:
Note: For the appropriate authority to take appropriate action on a change request, please provide a clear
description of the recommended change along with supporting rationale.
Send to: Commanding Officer, Space and Naval Warfare Systems Center, Code [[xxx]], 53560 Hull Street, San
Diego, CA 92152-5001
Fax to: indicate appropriate fax number
Email to: indicate appropriate email
Submit online: indicate appropriate URL
DCR Form 1/2009
MATA KULIAH MANAJEMEN PROYEK
Dosen : Rayi Pradono Iswara, Ir., M.Sc
Oleh :
MUHAMAD RAMDANI (1113091000016)
FAKULTAS SAINS DAN TEKNOLOGI
JURUSAN TEKNIK INFORMATIKA
UNIVERSITAS ISLAM NEGERI JAKARTA
2016
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
PROJECT MANAGEMENT PLAN
UNTUK
SISTEM PENGELOLAAN BARANG ONLINES
REVISI 0
22/04/2014
Team Name
Team Member 1
Team Member 2
Team Member 3
Team Member 4
Team Member 5
Team Member 5
: Web Builder Squad (WBS)
: Muhamad Ramdani
: Hamzah dua
: Hamzah tiga
: Hamzah empat
: Hamzah lima
: Hamzah enam
ii
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
SPBO-00
iii
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
RECORD OF CHANGES
*A - ADDED M - MODIFIED D – DELETED
VERSION
NUMBER
1.0
DATE
22/04/2016
NUMBER OF
FIGURE, TABLE
OR PARAGRAPH
A*
M
D
TITLE OR BRIEF DESCRIPTION
CHANGE
REQUEST
NUMBER
-
-
Pembuatan dokumen
-
iv
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
TABLE OF CONTENTS
Section
Page
SECTION 1. OVERVIEW ........................................................................................................................ 1
1.1
Project Summary ........................................................................................................................ 1
1.1.1
Purpose, Scope, and Objectives ........................................................................................... 1
1.1.2
Assumptions and Constraints .............................................................................................. 1
1.1.3
Project Deliverables ............................................................................................................ 2
1.1.4
Master Schedule and Budget Summary ............................................................................... 2
1.2
Evolution of the Plan .................................................................................................................. 2
1.3
Document Structure .................................................................................................................... 2
SECTION 2. REFERENCES..................................................................................................................... 4
2.1
Standards and Documents ........................................................................................................... 4
SECTION 3. DEFINITIONS ..................................................................................................................... 5
SECTION 4. PROJECT ORGANIZATION .............................................................................................. 6
4.1
External Interfaces ...................................................................................................................... 6
4.2
Internal Structure ........................................................................................................................ 6
4.2.1
The Project Manager ...........................................................Error! Bookmark not defined.
4.3
Project Roles and Responsibilities .............................................................................................. 6
SECTION 5. MANAGEMENT PROCESS ............................................................................................... 7
5.1
Start-up ....................................................................................................................................... 7
5.1.1
Estimation ........................................................................................................................... 7
5.1.2
Staffing ................................................................................................................................ 7
5.1.3
Resource Acquisition .......................................................................................................... 7
5.1.4
Staff Training ...................................................................................................................... 7
5.2
Work Planning ............................................................................................................................ 7
5.2.1
Work Activities ................................................................................................................... 7
5.2.2
Schedule Allocation ............................................................................................................ 7
5.2.3
Resource Allocation ............................................................................................................ 7
5.2.4
Budget Allocation ............................................................................................................... 8
5.3
Project Controls .......................................................................................................................... 8
5.3.1
Requirements Control .........................................................Error! Bookmark not defined.
5.3.2
Schedule Control .................................................................Error! Bookmark not defined.
5.3.3
Budget Control ....................................................................Error! Bookmark not defined.
5.3.4
Quality Control ...................................................................Error! Bookmark not defined.
5.3.5
Project Reporting and Communication ...............................Error! Bookmark not defined.
5.3.6
Metrics Collection ...............................................................Error! Bookmark not defined.
5.4
Risk Management ....................................................................................................................... 8
5.5
Project Closeout .......................................................................................................................... 8
SECTION 6. TECHNICAL PROCESS ..................................................................................................... 9
6.1
6.2
6.3
6.4
Process Model............................................................................................................................. 9
Methods, Tools and Techniques ................................................................................................. 9
Project Infrastructure .................................................................................................................. 9
Product Acceptance .................................................................................................................... 9
v
Sistem Pengelolaan Barang Online PMP
Revisi 0
22/04/2016
SECTION 7. SUPPORTING PROCESSES............................................................................................. 10
7.1
Configuration Management ...................................................................................................... 10
7.2
Independent Verification and Validation .................................................................................. 10
7.3
Documentation.......................................................................................................................... 10
7.4
Quality Assurance ..................................................................................................................... 10
7.5
Reviews and Audits .................................................................................................................. 10
7.6
Problem Resolution .................................................................................................................. 10
7.7
Contractor Management ........................................................................................................... 10
7.7.1
Contracting Process .............................................................Error! Bookmark not defined.
7.7.2
Contractor Performance Monitoring....................................Error! Bookmark not defined.
7.8
Process Improvement ................................................................................................................ 10
7.8.1
Systems/Software Process Improvement Lead ....................Error! Bookmark not defined.
7.8.2
Systems Engineering Process Group ...................................Error! Bookmark not defined.
SECTION 8. ADDITIONAL PLANS ..................................................................................................... 11
APPENDIX A. SPBOMASTER SCHEDULE (MICROSOFT PROJECT) ............................................... 2
APPENDIX B. SPBOFACILITIES PLAN ................................................................................................ 3
APPENDIX C. SPBOPROJECT TRAINING PLAN ................................................................................ 4
APPENDIX D. SPBOMEASUREMENT PLAN ....................................................................................... 5
APPENDIX E. SPBOPRODUCT ENGINEERING AND QUALIFICATION PROCESS ....................... 6
APPENDIX F. SPBOQUALITY ASSURANCE PLAN ........................................................................... 7
APPENDIX G. SPBOCONFIGURATION MANAGEMENT PLAN ....................................................... 8
LIST OF FIGURES
Figure
Page
LIST OF TABLES
Table
Page
Table 7-1. SPBO Documentation ............................................................................................................. 10
vi
SPBO PMP
SPBO 01
23/04/2016
SECTION 1. OVERVIEW
1.1
1.1.1
PROJECT SUMMARY
Purpose, Scope, and Objectives
Pertokoan tidak bisa dipisahkan dari mengirim dan menerima barang, segala
kegiatan suatu produk harus di catat agar tidak terjadi kerugian karena kehilangan data,
barang yang masih ada namun tetap ditambahkan, dan barang sudah kadaluarsa tapi
masih diperjual belikan yang akan mempengaruhi kepercayaan pembeli. Namun, tidak
semua toko menerapkan pengelolaan barang berbasis teknologi dan masih menggunakan
pembukuan manual. Dengan menganalisa gejala tersebut, dapat ditarik kesimpulan
mengenai peluang pengembangan aplikasi pengelolaan barang berbasis web online yang
diterapkan di setiap jenis toko.
Pengembangan sistem ini dimaksudkan untuk meningkatkan kinerja dari
pertokoan biasa menjadi pertokoan yang berbasis teknologi informasi kedepannya.
Objektif dari proyek ini yaitu :
1.1.2
Menambah daftar supplier dan produknya
Menampilkan daftar barang yang dimiliki
Mengedit dan menghapus data barang
Mencetak daftar supplier, barang, dan kegiatan barang yang masuk dan keluar
Assumptions and Constraints
Proyek akan direncanakan dengan beberapa asumsi berikut :
Arsitektur dari produk harus terbuka agar bisa ditambahkan fungsinya
Produk harus user-friendly
Proyek ini dibuat dengan bahasa pemrograman PHP, dan database MySQL
Proyek ini hanya akan memberikan komponen produk dari keseluruhan proyek
Produk ini bisa diakses di semua perangkat yang mendukung internet
Tim harus berkerja sama dalam menyelesaikan proyek
Memungkinkan penambahan sumber daya manusia dalam proyek
Proyek akan direncanakan dengan batasan berikut :
Anggaran
: Rp. 300.000.000
Waktu
: Dua bulan
1
SPBO PMP
SPBO 01
23/04/2016
Staff
: Pihak klien akan dibutuhkan untuk membantu menentukan kebutuhan,
dan detail desain untuk proyek.
Maintenance : Produk dapat di desain kembali saat maintenance sesuai biaya yang
ditentukan yaitu Rp. 50.000.000 /bulan.
1.1.3
Project Deliverables
Tim kami akan memberikan produk yang berupa software dan dokumentasi kepada pihak
klien dua bulan setelah proyek dimulai dan memberikan laporan hardcopy setiap minggu.
Dokumentasi yang berikan berupa instalasi software dan panduan untuk user.
1.1.4
Master Schedule and Budget Summary
Proyek ini memiliki beberapa jadwal:
rancangan proyek dasar
: satu minggu setelah proyek dimulai
prototype proyek pada localhost : lima minggu setelah proyek dimulai
Proyek ini memiliki anggaran sebesar Rp. 300.000.000. Sejak produk diberikan, biaya
maintenance akan dikenakan Rp. 10.000.000 setiap bulan.
Requirement Workflow
(1 minggu, 1 anggota, Rp.40.000.000)
Analysis Workflow
(1 minggu, 1 anggota, Rp.40.000.000)
Design Workflow
(1 minggu, 1 anggota, Rp.40.000.000)
1.2
Implementation Workflow
Testing Workflow
(1 minggu, 1 anggota, Rp.40.000.000)
(1 minggu, 1 anggota, Rp.40.000.000)
EVOLUTION OF THE PLAN
Perencanaan ini dipertimbangkan dengan laporan yang akan diberikan setiap minggu dan
hari yang tidak dijadwalkan jika dibutuhkan. pembaruan jadwal akan muncul setiap minggu.
Pemberitahuan yang terjadwal dan pembaruan tidak terjadwal dari rancangan akan
dikomunikasikan lewat e-mail kepada seluruh peserta proyek.
1.3
DOCUMENT STRUCTURE
This plan is organized as follows:
a. Section 1, Project Overview. This section provides an overview of the scope and objectives
of the project, the project’s assumptions and constraints, reference to the project deliverables,
schedule and budget, and a description of the evolution of the plan.
b. Section 2, References. This section provides a list of all documents, policies, templates,
processes, and other sources of information referenced in the plan.
c. Section 3, Definitions. This section contains the abbreviations and acronyms required to
properly understand this planning document.
d. Section 4, Project Organization. This section identifies interfaces to organizational entities
external to the project, the project’s internal organizational structure, and defines roles and
responsibilities for the project.
2
SPBO PMP
SPBO 01
23/04/2016
e. Section 5, Management Process. This section describes the planning, measurement,
tracking, reporting, risk control mechanisms needed to provide management control over the
technical processes and product quality, and appropriate project initiation and closeout
procedures.
f. Section 6, Technical Process. This section describes the technical solution in terms of a
process model and implementation methods, tools, and techniques to be used to develop the
various work products, plans for establishing and maintaining the project infrastructure, and
the product acceptance.
g. Section 7, Supporting Processes. This section describes processes that are employed to
facilitate and control the technical processes and the state of the product. These include, but
are not limited to, configuration management, verification and validation, documentation,
quality assurance, reviews and audits, problem resolution, and contractor management, and
methods to ensure continuous process improvement.
h. Section 8, Additional Plans. This section addresses the logistic support strategy to be applied
to increase the system’s operational effectiveness.
i. Appendix A. SPBO Master Schedule (Microsoft Project)
j. Appendix B. SPBO Facilities Plan
k. Appendix C. SPBO Project Training Plan
l. Appendix D. SPBO Measurement Plan
m. Appendix E. SPBO Product Engineering and Qualification Process
n. Appendix F. SPBO Quality Assurance Plan
o. Appendix G. SPBO Configuration Management Plan
3
SPBO PMP
SPBO 01
23/04/2016
SECTION 2. REFERENCES
2.1
STANDARDS AND DOCUMENTS
The standards and documents listed below are referenced in this document:
IEEE Standard 1058-1998 template,
Access information http://shop.ieee.org/store/product.asp?prodno=SS94690
IEEE Std 1058-1998, IEEE Standard for Software Project Management Plans, IEEE 1998
Object‐Oriented & Classical Software Engineering, 7th edition, Stephen R. Schach, pg. 590‐594
4
SPBO PMP
SPBO 01
23/04/2016
SECTION 3. DEFINITIONS
SPBO – Sistem Pengelolaan Barang Online
5
SPBO PMP
SPBO 01
23/04/2016
SECTION 4. PROJECT ORGANIZATION
4.1
EXTERNAL INTERFACES
Pihak klien dari proyek ini adalah toko grosir yang dinamakan Toko Maju Jaya, yang
diwakili oleh bapak Bambang. Seluruh komunikasi antara klien dan tim difasilitasi oleh pihak
klien dan bisa juga dilakukan via e-mail.
4.2
INTERNAL STRUCTURE
Struktur internal dari tim dan peran masing-masing. Struktur tim dibuat secara hirarki,
yang pimpin oleh ketua tim, dan sisanya ditugaskan untuk setiap perannya.
Setiap anggota harus menghubungi technical writer dan team mentor yang akan
membantu untuk memproduksi dokumen yang baik dan membantu tim mencapai tujuannya.
Tim akan melakukan pertemuan mingguan dan komunikasi via e-mail sebagai tambahan.
4.3
PROJECT ROLES AND RESPONSIBILITIES
Terbagi menjadi dua, yaitu peran dan tanggung jawab yang di bagikan ke seluruh tim.
Dapat dilihat pada tabel berikut :
Peran
Tanggung jawab
Penanggung jawab
Ketua
Pemenuhan proyek sesuai dengan jadwal dan
anggaran yang ditentukan
Muhamad Ramdani
Requirement Workflow
Mencari kebutuhan sistem yang akan dirancang
Hamzah dua
Analysis Workflow
Menganalisa kebutuhan yang berhubungan
dengan proyek
Hamzah tiga
Design Workflow
Mendesain tampilan produk secara keseluruhan
Hamzah empat
Implementation Workflow
Penyatuan semua komponen produk menjadi
produk yang dapat dijalankan
Hamzah lima
Testing Workflow
Menguji produk dan mencari kesalahan dalam
sistem
Hamzah enam
6
SPBO PMP
SPBO 01
23/04/2016
SECTION 5. MANAGEMENT PROCESS
5.1
5.1.1
5.1.2
START-UP
Estimation
Telah diteapkan sebelumnya, total waktu pengembangan sekitar 2 bulan dan total anggaran
sebesar Rp. 300.000.000. gambaran tersebut di dapatkan oleh expert judgement dari analogi, dan
dibandingkan dengan proyek yang sama.
Staffing
Ketua tim dibutuhkan selama 2 bulan penuh, untuk minggu pertama dibutuhkan
kapasistas pengelolaan, dan minggu kedua dibutuhkan manager dan programmer. Hamzah
dibutuhkan 3 minggu pertama untuk system analysis dan desaigner dan 2 minggu terakhir
dibutuhkan programmer dan tester.
5.1.3
Resource Acquisition
Seluruh kebutuhan hardware, software dan tools yang berhubungan untuk proyek telah
tersedia. Produk akan diberikan kepada klien dan instalasi pada desktop komputer sebagai server.
5.1.4
Staff Training
Tidak ada penambahan latihan staff yang dibutihkan pada proyek ini.
5.2
5.2.1
WORK PLANNING
Work Activities and Schedule Allocation
Minggu 1
Bertemu dengan klien, dan menetapkan kebutuhan produk.
Minggu 2, 3
Produksi hasil analisis untuk produk. Menunjukan rancangan kepada klien. Produksi
software project management.
Minggu 4, 5
Hasil desain produk dan inspeksinya.
Minggu 6, 7, 8
Implementasi dan inspeksi produk, unit testing dan dokumentasi, integrasi setiap fungsi,
integration testing, product testing, dan inspeksi dokumen.
5.2.3
Resource Allocation
Empat anggota tim akan bekerja secara terpisah sesuai dengan tugas masing-masing.
Muhamad Ramdani akan memonitor progses keseharian dan anggota lainnya, dan bertanggung
jawab untuk kualitas keseluruhan, dan komunikasi dengan klien. Anggota tim akan berkumpul
setiap akhir hari dan mendiskusikan masalah dan progres. pertemuan formal akan dilaksanakan
setiap akhir minggu untuk melaporkan progses dan mennentukan jika terdapat perubahan. Risk
management menjadi tanggung jawab M. Ramdani.
Meminimalisir kesalahan dan memaksimalkan user-friendliness akan menjadi top priority
bagi M.Ramdani, dan keseluruhan tanggung jawab untuk dokumentasi dan memastikan itu selalu
up to date.
7
SPBO PMP
SPBO 01
23/04/2016
5.2.4
5.3
Budget Allocation
Requirement Workflow
Rp.50.000.000
Analysis Workflow
Rp.50.000.000
Design Workflow
Rp.50.000.000
Implementation Workflow
Rp.50.000.000
Testing Workflow
Rp.50.000.000
Lain-lain
Rp.50.000.000
Total
Rp.300.000.000
PROJECT CONTROLS
Adanya perubahan besar yang berdampak pada milestones atau anggaran harus disetujui
oleh Ramdani dan didokumentasikan. tidak ada jaminan qualitas personalia dari luar yang
bersangkutan.
Ramdani bertanggung jawab untuk memastikan proyek selesai tepat waktu dan tidak
melebihi anggaran. setiap pertemuan anggota tim akan mempresentasikan progres dan masalah
harian. Ramdani akan menentukan apakah progres mereka seperti yang diharapkan dan apakah
mereka mengikuti spesifikasi dari dokumen dan project management plan. setiap masalah besar
yang dihadapi oleh anggota tim harus secepatnya di laporkan kepada Ramdani.
5.4
RISK MANAGEMENT
Kerena kemungkinan kesalahan besar terdapat pada desain, pengujian ekstensif akan
dilakukan ketika design workflow. dan juga, pada awalnya setiap anggota tim akan menguji
setiap code dan menguji code yang lain. Ramdani bertanggung jawab dalam integration testing
dan product testing.
5.5
PROJECT CLOSEOUT
Tidak dapat digunakan disini.
8
SPBO PMP
SPBO 01
23/04/2016
SECTION 6. TECHNICAL PROCESS
6.1
PROCESS MODEL
Yang akan digunakan adalah Unified Process.
6.2
METHODS, TOOLS AND TECHNIQUES
Workflow akan dilakukan sesuai dengan Unified Process. Produk akan
diimplementasikan dalam pemrograman PHP.
6.3
PROJECT INFRASTRUCTURE
Produk akan dikembangkan dalam format HTML dan berbasis web, berjalan pada semua
perangkat yang dapat terhubung internet.
6.4
PRODUCT ACCEPTANCE
Penerimaan produk oleh klien yang akan dicapai melalui langkah dari Unified Process.
9
SPBO PMP
SPBO 01
23/04/2016
SECTION 7. SUPPORTING PROCESSES
7.1
CONFIGURATION MANAGEMENT
CVS akan digunakan pada semua artifacts.
7.2
INDEPENDENT VERIFICATION AND VALIDATION
Testing workflow akan dilakukan sesuai Unified Process.
7.3
DOCUMENTATION
Dokumentasi akan di produksi secara spesifik pada Unified Process.
TABLE 7-1. SPBODOCUMENTATION
Document Type
7.4
QUALITY ASSURANCE
7.5
REVIEWS AND AUDITS
Format Standard
Estimated
Page Count
Peer Review Type
Setiap Hamzah satu sampai lima akan menguji code satu sama lain, dan Ramdani akan
memimpin dalam integration testing. Pengujian produk ekstensif akan dilakukan oleh semua tim.
7.6
PROBLEM RESOLUTION
Setiap masalah besar yang dihadapi oleh anggota tim secepatnya dilaporkan pada Ramdani.
7.7
CONTRACTOR MANAGEMENT
Tidak dipergunakan disini.
7.8
PROCESS IMPROVEMENT
Semua aktivitas akan di diselenggarakan dalam persetujuan dengan klien untuk kemajuan dalam
1 bulan.
10
SPBO PMP
SPBO 01
23/04/2016
SECTION 8. ADDITIONAL PLANS
Komponen tambahan:
Keamanan
: Dibutuhkan password untuk menggunakan produk.
Pelatihan
: Pelatihan akan dilakukan oleh Ramdani pada waktu pemberian produk.
karena produk ini adalah penggunaan straight forward, 1 day mungkin cukup untuk
pelatihan. Ramdani akan menjawab pertanyaan tanpa biaya untuk penggunaan bulan
pertama.
Maintenance
: Perbaikan pemeliharaan akan dilakukan oleh tim tanpa biaya pada
bulan pertama. Kontrak yang berbeda akan di tarik mengenai perbaikan peningkatan.
11
SPBO PMP
SPBO 01
23/04/2016
APPENDICES
IEEE Std 1058-1998 Guidance
Annexes may be included, either directly or by reference to other documents, to provide supporting
details that could detract from the document if included in the body.
General Guidance
In this template, the following appendices are used for reference purposes only. It should not be assumed
that the referenced documents exist as an example.
Appendices -1
SPBO PMP
SPBO 01
23/04/2016
APPENDIX A. SPBOMASTER SCHEDULE (MICROSOFT PROJECT)
Guidance
The objective of the SPBOmaster schedule is to provide management with the task map and tracking tool
needed to guide the project in the performance of its mission.
The SPBOmaster schedule’s Microsoft Project representation of the WBS would be tailored from the
templates available from the SSC Pacific Process Asset Library (PAL) in the “SW-CMM Archive”. Draft
Microsoft Project templates are found under the “Process Assets by SW-CMM KPA”, “Software Project
Planning (SPP)” in the “Tools” section. These templates can be tailored up or down to meet specific
project needs.
Appendices -2
SPBO PMP
SPBO 01
23/04/2016
APPENDIX B. SPBOFACILITIES PLAN
Guidance
The objective of the SPBOFacilities Plan is to document the environmental needs of the project. These
needs include space, equipments, security, safety, support tools, and the staff necessary to maintain and
operate an environment needed for project operations.
The facilities requirements for projects vary broadly, often with several projects sharing both facilities
and computer resources. There currently are no templates available from the SSC Pacific PAL to assist
in developing a facilities plan. However, recommended issues to address in a Facilities Plan would
include, but not be limited to, the following list:
1. Facility Objectives/General Description
2. Facility Locations (i.e., Building Locations)
3. Facility Diagrams
a. Floor Plans (i.e., lab, work cubicles)
b. Environmental Requirements i.e. Heating, Lighting
4. Facilities Equipment Requirements
a. Equipment Lists (i.e., work stations, development, test)
b. Equipment Interface Diagrams
c. Space Equipment Layouts
d. Inspections and Records Requirements
5. Facilities Software Requirements
a. Software by Development/Test Host Equipment
b. Software by Workstation
6. Facilities Operating Personnel Requirements
7. Facilities Operating Personnel Training Requirements
8. Security Measures
a. Internal
b. External
9. Safety Measures
10. Maintenance Requirements (i.e., spaces, per equipment)
11. Facilities Performance Measurements
Appendices -3
SPBO PMP
SPBO 01
23/04/2016
APPENDIX C. SPBOPROJECT TRAINING PLAN
Guidance
The objective of the SPBOProject Training Plan is to develop the skills and knowledge of the project staff
so they can perform their roles effectively and efficiently.
The SPBOProject Training Plan would be tailored from the Department/Project Training Plan Template
available from the SSC Pacific Process Asset Library (PAL). The template is located in the “Process
Assets” sub-page under the “Organizational Training” PA in the “Plans” section. The template can be
tailored up or down to meet specific project needs.
Appendices -4
SPBO PMP
SPBO 01
23/04/2016
APPENDIX D. SPBOMEASUREMENT PLAN
Guidance
The objective of the SPBOMeasurement Plan is to develop and present the data needed to support project
management information needs necessary to ensure objective decision-making.
The SPBOMeasurement Plan would be tailored from the Software Measurement Plan Template available
from the SSC Pacific Process Asset Library (PAL) in the “SW-CMM Archive”. This template can be
found under the ”Process Assets by SW-CMM KPA”, “Software Project Tracking and Oversight
(SPTO)” KPA in the “Tools” section. The template can be tailored up or down to meet specific project
needs.
Appendices -5
SPBO PMP
SPBO 01
23/04/2016
APPENDIX E. SPBOPRODUCT ENGINEERING AND QUALIFICATION
PROCESS
Guidance
The objective of the SPBOProduct Engineering and Qualification (PE&Q) Process is to document the
processes comprising a technical solution for development, maintenance, test, and product qualification.
The SPBOPE&Q Process would be tailored from the Product Engineering and Qualification Process
available from the SSC Pacific Process Asset Library (PAL). The process is located in the “Process
Assets” sub-page under the “Technical Solution” PA in the “Process” section. The PE&Q Process can
be tailored up or down to meet specific project needs.
Appendices -6
SPBO PMP
SPBO 01
23/04/2016
APPENDIX F. SPBOQUALITY ASSURANCE PLAN
Guidance
The objective of the SPBOQuality Assurance Plan is to provide staff and management with objective
insights into processes and associated work products, ensuring their conformance to documented
requirements.
The SPBOQuality Assurance Plan would be tailored from the Quality Assurance Plan Template available
from the SSC Pacific Process Asset Library (PAL). The process is located in the “Process Assets” subpage under the “Process and Product Quality Assurance (PPQA)” PA in the “Plans” section. The
template can be tailored up or down to meet specific project needs.
Appendices -7
SPBO PMP
SPBO 01
23/04/2016
APPENDIX G. SPBOCONFIGURATION MANAGEMENT PLAN
Guidance
The objective of the SPBOConfiguration Management Plan is to establish and maintain the integrity of
SPBOwork products using configuration identification, configuration control, configuration status
accounting, and configuration audits.
The SPBOConfiguration Management Plan would be tailored from the Configuration Management Plan
Template available from the SSC Pacific Process Asset Library (PAL). The template is located in the
“Process Assets” sub-page under the “Configuration Management (CM)” PA in the “Plans” section.
The template can be tailored up or down to meet specific project needs.
Appendices -8
DOCUMENT CHANGE REQUEST (DCR)
Document Title: [[Project]] Project Management Plan
Tracking Number:
Name of Submitting Organization:
Organization Contact:
Phone:
Mailing Address:
DCR Description:
Date:
Change Location:
(use section #, figure #, table #, etc.)
Proposed change:
Rationale for Change:
Note: For the appropriate authority to take appropriate action on a change request, please provide a clear
description of the recommended change along with supporting rationale.
Send to: Commanding Officer, Space and Naval Warfare Systems Center, Code [[xxx]], 53560 Hull Street, San
Diego, CA 92152-5001
Fax to: indicate appropriate fax number
Email to: indicate appropriate email
Submit online: indicate appropriate URL
DCR Form 1/2009