MANAJEMEN PROYEK FRAMEWORK

Ukuran: px

Mulai penontonan dengan halaman:

Download "MANAJEMEN PROYEK FRAMEWORK"

Teguh Hermanto
8 tahun lalu
Tontonan:

1 MANAJEMEN PROYEK FRAMEWORK

2 PROJECT MANAGEMENT FRAMEWORK

3 Kelompok Proses dalam PMBOK KNOWLEDGE AREA PROJECT MANAGEMENT PROCESS GROUPS INITIATING PLANNING EXECUTING MONITORING & CONTROLLING CLOSING Integration Management Membuat Piagam Proyek Membuat Rencana Proyek Melaksanakan Rencana Proyek Mengendalikan proyek secara menyeluruh Scope Inisiasi Rencana ruang-lingkup Verifikasi Ruang- Lingkup Definisi Ruang-Lingkup Pengendalian perubahan ruanglingkup Time Definisi Aktivitas Pengendalian jadwal Pengurutan aktivitas Perkiraan Lama Aktivitas Pembuatan Jadwal Cost Perencanaan Resource Pengendalian Biaya Estimasi Biaya Pengalokasian Biaya Kualitas Perencanaan Kualitas Penjaminan Kualitas Pengendalian Kualitas

4 Human Resources Perencanaan Organisasi Pembentukan Tim Akuisisi Staff Communications Perencanaan Komunikasi Risks Perencanaan Manajemen Resiko Distribusi Informasi Laporan Performansi Penutupan secara Administratif Pengendalian dan Pengawasan Resiko Identifikasi Resiko Analisis Resiko Kualitatif Analisis Resiko Kuantitatif Perencanaan Tanggapan Thd Resiko Procurement Perencanaan Procurement Perencanaan Permintaan Permintaan Penutupan Kontrak Seleksi sumber

5 SCOPE MANAGEMENT

6 What is Project Scope Management? Scope refers to all the work involved in creating the products of the project and the processes used to create them. It defines what is or is not to be done Deliverables are products produced as part of a project, such as hardware or software, planning documents, or meeting minutes The project team and stakeholders must have the same understanding of what products will be produced as a result of a project and how they ll be produced

7 Project Scope Scope refers to all the work involved in creating the products of the project and the processes used to create them Provides a boundary so that what needs to get done gets done. Otherwise, schedule and budget are increased for no reason Project scope management includes the processes involved in defining and controlling what is or is not included in a project Defines what is part of the project team s work and what is not. This also sets expectations for all of the project s stakeholders A deliverable is a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes

8 Project Scope Management Processes Scope planning: Deciding how the scope will be defined, verified, and controlled. Scope definition: Reviewing the project charter and preliminary scope statement and adding more information as requirements are developed and change requests are approved. Creating the WBS: Subdividing the major project deliverables into smaller, more manageable components. Scope verification: Formalizing acceptance of the project scope. Scope control: Controlling changes to project scope.

9 Scope Planning and the Scope Management Plan The scope management plan is a document that includes descriptions of how the team will prepare the project scope statement, create the WBS, verify completion of the project deliverables, and control requests for changes to the project scope. Key inputs include the project charter, preliminary scope statement, and project management plan.

10 Sample Project Charter

11 Sample Project Charter (cont d)

12 Scope Definition and the Project Scope Statement The preliminary scope statement, project charter, organizational process assets, and approved change requests provide a basis for creating the project scope statement. As time progresses, the scope of a project should become clearer and more specific.

13 Further Defining Project Scope

14 Scope Management Example

15 P r o j e c t S c o p e E x a m p l e

16 P r o j e c t C h a r t e r E x a m p l e

17 Defining Scope Example

18 Scope Change Request Form Scope Change Request Log

19 Best Practices for Avoiding Scope Problems 1. Keep the scope realistic: Don t make projects so large that they can t be completed; break large projects down into a series of smaller ones 2. Involve users in project scope management: Assign key users to the project team and give them ownership of requirements definition and scope verification 3. Use off-the-shelf hardware and software whenever possible: Many IT people enjoy using the latest and greatest technology, but business needs, not technology trends, must take priority

20 Requirement Engineering Requirements engineering adalah cabang dari software engineering yang mengurusi masalah yang berhubungan dengan tujuan, fungsi, dan batasan-batasan pada sistem software. Termasuk hubungan faktor-faktor tersebut dalam menetapkan spesifikasi yang tepat dari suatu software, proses evolusinya baik berhubungan dengan masalah waktu maupun dengan software lain. Requirements engineering adalah fase terdepan dari proses rekayasa perangkat lunak, dimana software requirements (kebutuhan) dari user (pengguna) dikumpulkan, dipahami dan ditetapkan.

22 Faktor Kegagalan Ketidakkonsistenan (Inconsistent) Ketidaklengkapan (Incomplete) Ketidakbenaran (Incorrect) Dari Spesifikasi Kebutuhan

23 a. Kebutuhan user pada saat wawancara menurut analis sistem b. Kebutuhan user yg cukup direalisasikan menurut analis sistem APA YANG DIINGINKAN USER??? c. Pemrograman melakukan penyederhanaan d. Sistem yg sebenarnya diinginkan oleh user

25 Q&A?

26 REFERENSI Materi Komsi Materi MTI Dari berbagai sumber di Internet

dokumen-dokumen yang mirip

STUDI KASUS : KELOMPOK PROSES MANAJEMEN PROYEK PROJECT MANAGEMENT, THIRD EDITION 1

STUDI KASUS : KELOMPOK PROSES MANAJEMEN PROYEK IT PROJECT MANAGEMENT, THIRD EDITION 1 KELOMPOK PROSES MANAJEMEN PROYEK Manajemen Proyek bisa dipandang sebagai kumpulan proses-proses yang saling terkait/berhubungan