Project Management IS/IT

Integration & Scope

Management
Modul 2a & 2b

Tiar Anindya Putri, S.Kom., M.MT.

Dosen S1 Bisnis Digital
I T Te l ko m S u r a b a y a
https://bpptik.kominfo.go.id/download/s
kkni-2014-349-ict-project-manager/
10 Knowledge Areas
 Final Project
• Topik dibidang IT/IS(Berbentuk Pengmas) →
10 knowledge area nya di mappingkan ke Template
Tugas Akhir (pilih salah satu)
– Pembuatan Website Profile
– Pembuatan LMS
– Pengelolaan e-Commerce & Social Media
– Pengelolaan Content Marketing
– Pelatihan Content Marketing
– Pelatihan Aplikasi (ex: Ms. Project, TOMPS)
– Dll
• Keluarannya ada 2: Dokumen & hasil pengmasnya
 Final Project
PROJECT DOCUMENT - extended
Project Description and Goals
Deliverables
Integration & Scope
Scope Definition
Assumptions, Constraints & Dependencies
Schedule Project Milestones
Cost Budget Summary
Quality Quality Management Plan
Project Organizational Structure
Resource
Requirement management Plan
Resource Histogram
Communication Communication Management Plan
Risk Risk Management Plan
Procurement Procurement Management Plan
Stakeholder Management Stakeholder Management Plan
 Perubahan Rencana Pembelajaran Semester
S1 Sistem Informasi
Week Materi Ajar Materi Progress Kelompok Presentasi
Week 2 Integration & Scope Management
Week 3 Schedule Management & Praktikum Integration & Scope Kelompok 1
Week 4 Cost Management & Praktikum Schedule Kelompok 2
Week 5 Quiz 1
Week 6 Quality Management Cost Kelompok 3 Kelompok 4
Week 7 Resource Management Quality Kelompok 5 Kelompok 6
Week 8 UTS
Week 9 Communication Management Resource Kelompok 7 Kelompok 8
Week 10 Risk Management Communication Kelompok 1 Kelompok 2
Week 11 Procurement Risk Kelompok 3 Kelompok 4
Week 12 Stakeholder Management Procurement Kelompok 5 Kelompok 6
Week 13 Quiz 2
Stakeholder
Week 14 Agile Kelompok 7 Kelompok 8
Management
Week 15 Presentasi Tugas Besar Hasil Akhir Proyek Kelompok 1 Kelompok 2 Kelompok 3 Kelompok 4
Week 16 Presentasi Tugas Besar Hasil Akhir Proyek Kelompok 5 Kelompok 6 Kelompok 7 Kelompok 8
 Perubahan Rencana Pembelajaran Semester
S1 Teknologi Informasi
Week Materi Ajar Materi Presentasi Kelompok Presentasi
Week 2 Integration & Scope Management
Week 3 Schedule Management & Praktikum Integration & Scope Kelompok 1
Week 4 Cost Management & Praktikum Kelompok 2
Schedule
Week 5 Quiz 1 Kelompok 3
Week 6 Quality Management Cost Kelompok 4 Kelompok 5
Week 7 Resource Management Quality Kelompok 6 Kelompok 7
Week 8 UTS
Week 9 Communication Management Resource Kelompok 8 Kelompok 9
Week 10 Risk Management Communication Kelompok 1 Kelompok 2
Week 11 Procurement Risk Kelompok 3 Kelompok 4
Week 12 Stakeholder Management Kelompok 5 Kelompok 6
Procurement
Week 13 Quiz 2 Kelompok 7
Stakeholder
Week 14 Agile
Management Kelompok 8 Kelompok 9
Week 15 Presentasi Tugas Besar Hasil Akhir Proyek Kelompok 1 Kelompok 2 Kelompok 3 Kelompok 4 Kelompok 5
Week 16 Presentasi Tugas Besar Hasil Akhir Proyek Kelompok 6 Kelompok 7 Kelompok 8 Kelompok 9
Manajemen Integrasi Proyek
• Manajemen Integrasi Proyek adalah tiang penyangga
yang mempengaruhi dan dipengaruhi oleh seluruh
knowledge area dalam Manajemen Proyek.
• Manajemen Integrasi Proyek melibatkan koordinasi
seluruh knowledge area dalam project life cycle.
• Manajemen Integrasi Proyek, merupakan salah satu
kompetensi yang harus dimiliki oleh Manajer Proyek.
 – Siklus hidup proyek. Apa siklus hidup proyek yang sesuai?
Fase apa yang harus terdiri dari siklus hidup proyek?
– Siklus hidup perkembangan. Apa siklus hidup dan
pendekatan pengembangan?sesuai untuk produk, layanan,
atau hasil? Apakah pendekatan prediktif atau adaptif tepat?
Jika adaptif, apakah produk harus dikembangkan secara
PERTIMBANGAN bertahap atau berulang? Apakah pendekatan hybrid terbaik?
– Pendekatan manajemen. Proses manajemen apa yang paling
PENYESUAIAN efektif berdasarkan budaya organisasi dan kompleksitas
proyek?
Manajemen Integrasi Proyek – Manajemen pengetahuan. Bagaimana pengetahuan akan
dikelola dalam proyek untuk mendorong lingkungan kerja
yang kolaboratif?
Karena setiap proyek adalah unik, – Change management. Bagaimana perubahan akan dikelola
manajer proyek mungkin perlu dalam proyek?
menyesuaikan cara penerapan – Pemerintahan (Governance). Apa dewan kontrol, komite, dan
proses Manajemen Integrasi Proyek. pemangku kepentingan lainnya yang merupakan bagian dari
proyek? Apa persyaratan pelaporan status proyek?
Pertimbangan untuk menjahit
– Pelajaran yang didapat (lesson learned). Informasi apa yang
termasuk tetapi tidak terbatas pada: harus dikumpulkan selama dan di akhir proyek? Bagaimana
informasi sejarah dan pelajaran yang dipetik akan tersedia
untuk proyek-proyek masa depan?
– Manfaat. Kapan dan bagaimana seharusnya manfaat
dilaporkan: pada akhir proyek atau pada akhir setiap iterasi
atau fase?
PERTIMBANGAN UNTUK
LINGKUNGAN AGILE/ADAPTIF
• Pendekatan berulang dan tangkas mempromosikan keterlibatan anggota
tim sebagai pakar domain lokal dalam manajemen integrasi. Anggota tim
menentukan bagaimana rencana dan komponen harus diintegrasikan.
• Harapan manajer proyek seperti yang dicatat dalam Konsep Kunci untuk
Manajemen Integrasi tidak berubah dalam lingkungan adaptif, tetapi
kontrol dari perencanaan dan pengiriman produk yang terperinci
didelegasikan kepada tim.
• Fokus manajer proyek adalah membangun lingkungan pengambilan
keputusan yang kolaboratif dan memastikan tim memiliki kemampuan
untuk merespons perubahan. Pendekatan kolaboratif ini dapat lebih
ditingkatkan ketika anggota tim memiliki basis keterampilan yang luas
daripada spesialisasi yang sempit.
Develop Project Charter
• Proses pembuatan dokumen yang secara
formal menyatakan bahwa project berjalan
dan memberikan wewenang kepada Project
Manager untuk menjalankan proyek.
• Dokumen project charter berisi informasi
penting yang mencakup penjelasan ringkas
dari sebuah proyek yang akan dijalankan.
 Project Charters
• A project charter is a document that formally
recognizes the existence of a project and
provides direction on the project’s objectives and
management.

• Key project stakeholders should sign a project

charter to acknowledge agreement on the need
and intent of the project; a signed charter is a
key output of project integration management.
 Develop Project Charter
BUSINESS DOCUMENTS
EXPERT JUDGMENT Project Charter

Tools & Techniques

Outputs
Inputs
• Business case
• Market demand • Organizational strategy • Project purpose
• Organizational need • Benefits management • Measurable project objectives and
• Customer request related success criteria
• Technical knowledge of the industry
• Technological advance • High-level requirements
and focus area of the project
• Legal requirement • High-level project description,
• Ecological impacts • Duration and budget estimation boundaries, and key deliverables
• Social need • Risk identification • Overall project risk
AGREEMENTS
DATA GATHERING • Summary milestone schedule
• Agreements are used to define initial • Preapproved financial resources
intentions for a project • Brainstorming • Key stakeholder list
ENTERPRISE ENVIRONMENTAL FACTORS • Focus groups discussion • Project approval requirements (i.e., what
• Government or industry standards • Interviews constitutes project success, who decides
• Legal and regulatory requirements and/or the project is successful, and who signs
constraints INTERPERSONAL AND TEAM off on the project)
• Marketplace conditions SKILLS • Project exit criteria (i.e., what are the
• Organizational culture and political climate
• Conflict management conditions to be met in order to close or
• Organizational governance framework
to cancel the project or phase)
• Stakeholders’ expectations and risk • Facilitation • Assigned project manager,
thresholds
ORGANIZATIONAL PROCESS ASSETS
• Meeting management responsibility, and authority level
• Organizational standard policies, processes, MEETINGS • Name and authority of the sponsor or
and procedures; other person(s) authorizing the project
• Portfolio, program, and project governance
• Meetings are held with key charter.
framework (governance functions and stakeholders to identify the project ASSUMPTION LOG
processes to provide guidance and decision objectives, success criteria, key
making); deliverables, high-level • The assumption log is used to record all
• Monitoring and reporting methods; requirements, summary milestones, assumptions and constraints
• Templates (e.g., project charter template); and other summary information. throughout the project life cycle.
and
• Historical information and lessons learned
repository (e.g., project records and
documents, information about the results of
previous project selection decisions, and
information about previous project
performance).
Develop Project Management Plan
• Proses mendefinisikan, menyiapkan dan
mengoordinasikan, dan mengintegrasikan
rencana proyek ke dalam rencana
manajemen proyek (Project Management
Plan).
 Project Management Plan
PROJECT CHARTER EXPERT JUDGMENT PROJECT MANAGEMENT

Tools & Techniques

Outputs
Inputs

OUTPUT FROM OTHER PROCESSES • Tailoring the project management process to

meet the project needs, including PLAN
• subsidiary plans and baselines that are an • the dependencies and interactions among those
output from other planning processes processes and the essential inputs and outputs;
ENTERPRISE ENVIRONMENTAL • Developing additional components of the project
FACTORS management plan if needed;
• Determining the tools and techniques to be used
• Government or industry standards for accomplishing those processes;
• Legal and regulatory requirements • Developing technical and management details to
and/or constraints be included in the project management plan;
• Determining resources and skill levels needed to
• Project management body of knowledge perform project work;
for vertical market (e.g., construction) • Defining the level of configuration management
and/or focus area (e.g., environmental, to apply on the project;
safety, risk, or agile software • Determining which project documents will be
development) subject to the formal change control process; and
• Prioritizing the work on the project to ensure the
• Organizational structure, culture, project resources are allocated to the appropriate
management practices, and work at the appropriate time.
sustainability DATA GATHERING
• Organizational governance framework • Brainstorming
• Infrastructure • Checklists
ORGANIZATIONAL PROCESS ASSETS • Focus groups discussion
• Interviews
• Historical information and lessons
learned repository INTERPERSONAL AND TEAM SKILLS
• Project information from previous similar • Conflict management
projects • Facilitation
• Meeting management
• Monitoring and reporting methods, risk
control procedures, and communication MEETINGS
requirements • For small projects, there is usually only one team
that performs the planning and the execution.
• Organizational standard policies,
• In large projects, a project management team
processes, and procedures normally does the majority of the planning, and
• Project management plan template the remainder of the project team is brought on
when the initial planning is complete, at the start
of the development/ implementation.
Direct and Manage Project Work
• Proses memimpin (leading) dan
menjalankan (performing) seluruh rencana
yang sudah dibuat di dalam project
management plan dan melaksanakan
perubahan yang diperlukan untuk
mencapai tujuan proyek
 DIRECT AND MANAGE PROJECT WORK
PROJECT MANAGEMENT EXPERT JUDGMENT DELIVERABLES

Tools & Techniques

Outputs
Inputs

PLAN • Technical knowledge on the industry WORK PERFORMANCE DATA

and focus area of the project
PROJECT DOCUMENTS ISSUE LOG
• Cost and budget management
• Change log • Legal and procurement
• Lessons learned register CHANGE REQUESTS
• Legislation and regulations
• Milestone list • Organizational governance PROJECT MANAGEMENT
• Project communications PLAN UPDATES
PROJECT MANAGEMENT
• Project schedule
• Requirements traceability matrix
INFORMATION SYSTEM (PMIS) PROJECT DOCUMENTS
• Risk register • The PMIS provides access to information UPDATES
• Risk report. technology (IT) software tools, such as
scheduling software tools, work ORGANIZATIONAL PROCESS
APPROVED CHANGE authorization systems, configuration ASSETS UPDATES
REQUESTS management systems, information
collection and distribution systems, as
ENTERPRISE well as interfaces to other online
ENVIRONMENTAL FACTORS automated systems such as corporate
knowledge base repositories
• Organizational structure, culture,
management practices, and MEETINGS
sustainability • Meetings are used to discuss and
• Infrastructure (e.g., existing facilities and address pertinent topics of the project
capital equipment) when directing and managing project
• Stakeholder risk thresholds (e.g., work
allowable cost overrun percentage)
ORGANIZATIONAL PROCESS
ASSETS
MANAGE PROJECT KNOWLEDGE
• Mengelola Pengetahuan Proyek adalah proses menggunakan
pengetahuan yang ada dan menciptakan pengetahuan baru
untuk mencapai tujuan proyek dan berkontribusi pada
pembelajaran organisasi.
• Manfaat utama dari proses ini adalah bahwa pengetahuan
organisasi sebelumnya dimanfaatkan untuk menghasilkan
atau meningkatkan hasil proyek, dan pengetahuan yang
dibuat oleh proyek tersedia untuk mendukung operasi
organisasi dan proyek atau fase masa depan.
 MANAGE PROJECT KNOWLEDGE
Project Management Plans
Expert Lessons
Inputs

Tools & Techniques

Outputs
• All Components
Project Documents
• Lessons learned register
Judgement Learned
• Project team assignments
• Resource breakdown structure Knowledge Register
• Source selection criteria
• Stakeholder register
Deliverables
Management Project
• A deliverable is any unique and verifiable
Information Management
product, result, or capability to perform a
service that is required to be produced
to complete a process, phase, or project. Management Plan UPDATES
Enterprise Environmental
Factors
Interpersonal Organizational
• Organizational, stakeholder, and
customer culture
and Team Skills Process Assets
UPDATES
• Geographic distribution of facilities and
resources
• Organizational knowledge experts
• Legal and regulatory requirements
• Active listening
and/or constraints
ORGANIZATIONAL PROCESS ASSETS
• Facilitation
• Organizational standard policies,
processes, and procedures
• Leadership
• Personnel administration
• Organizational communication
• Networking
requirements
• Formal knowledge-sharing and
• Political Awareness
information-sharing procedures
Monitor and Control Project Work
• Proses pelacakan (tracking), meninjau
(reviewing), dan pelaporan (reporting)
kemajuan proyek terhadap kinerja yang
ditetapkan dalam rencana manajemen
proyek.
 Monitor and Control Project Work
PROJECT MANAGEMENT
Data Analysis Work

Outputs
Inputs

Tools & Techniques

PLAN
• Any component • Alternatives Performance
PROJECT DOCUMENTS
Analysis Reports
• Assumption Log
• Cost-benefit
• Basis of Estimates
• Cost forecsats Analysis Change
• Issue Log • Earned Value Requests
• Lessons Learned register
Analysis Project
• Milestone List
• Root cause
• Quality Reports
• Risk Register Analysis
Management
• Risk Report • Trend Analysis Plan Updates
• Schedule Forecasts
WORK PERFORMANCE • Variance Analysis Project
INFORMATION Expert Documents
AGREEMENTS
ENTERPRISE
Judgement Updates
ENVIRONMENTAL FACTORS
ORGANIZATIONAL PROCESS
Decision Making
ASSETS
Meetings
PERFORM INTEGRATED CHANGE
CONTROL
• Proses meninjau semua permintaan
perubahan; menyetujui perubahan dan
mengelola perubahan pada kiriman, aset
proses organisasi, dokumen proyek, dan
rencana manajemen proyek; dan
mengkomunikasikan keputusan.
 PERFORM INTEGRATED CHANGE CONTROL
Project Management Plan Expert judgment Approved change

Outputs
Tools & Techniques
Inputs

• Change management plan • Stakeholders with expertise requests

• Configuration management may be asked to sit on • Only those change requests
plan Change Control Board (CCB) which are approved by the
• Scope baseline Meetings appropriate authority (such as
• Schedule baseline the Change Control Board) are
• Meetings of Change Control then input back into process
• Cost baseline Board are referred as to as
• Direct and Manage Project
PROJECT DOCUMENTS change control meetings.
Work.
• Basis of estimates Change control tools Change Log
• Requirements traceability • Manual or automated tools
matrix • All change requests, whether
may be used for change or
approved or rejected, get
• Risk report configuration management.
recorded in the change log.
WORK PERFORMANCE Project Management
REPORTS
Plan updates
CHANGE REQUESTS
ENTERPRISE Project Document
ENVIRONMENTAL FACTORS updates
ORGANIZATIONAL PROCESS • All documents that are
ASSETS considered part of the formal
change control process are
updated.
CLOSE PROJECT OR PHASE
• Close project or phase adalah proses
menyelesaikan semua kegiatan untuk proyek,
fase, atau kontrak. Manfaat utama dari proses
ini adalah informasi proyek atau fase
diarsipkan, pekerjaan yang direncanakan
selesai, dan sumber daya tim organisasi
dilepaskan untuk mengejar upaya baru.
 CLOSE PROJECT OR PHASE
PROJECT CHARTER
EXPERT PROJECT

Tools & Techniques

Outputs
Inputs

PROJECT MANAGEMENT
PLAN JUDGMENT DOCUMENTS
PROJECT DOCUMENTS DATA ANALYSIS UPDATES
ACCEPTED DELIVERABLES
• Document analysis FINAL PRODUCT,
BUSINESS DOCUMENTS
• Regression analysis SERVICE, OR
AGREEMENTS
• Trend analysis RESULT
PROCUREMENT
DOCUMENTATION • Variance analysis TRANSITION
ORGANIZATIONAL PROCESS MEETINGS FINAL REPORT
ASSETS
ORGANIZATIONAL
PROCESS ASSET
UPDATES
IMPLEMENT RISK RESPONSES
• Proses Implementasi Respons Risiko adalah proses
untuk mengambil rencana respons proyek dan benar-
benar melakukan pekerjaan untuk mewujudkan
rencana tersebut.
• Tujuan dari proses ini adalah untuk memastikan
bahwa setiap risiko yang teridentifikasi pada Risk
Register memiliki tindakan atau rencana yang tepat
untuk memitigasi atau menghindari risiko sebelum
terjadi atau untuk memberikan respons ketika risiko
terjadi dan berubah menjadi masalah proyek.
CONDUCT PROCUREMENTS
• Mengadakan Pengadaan adalah proses
mendapatkan tanggapan Klien, memilih
Klien, dan memberikan kontrak. Manfaat
utama dari proses ini adalah memberikan
keselarasan harapan pemangku kepentingan
internal dan eksternal melalui kesepakatan
yang ditetapkan.
MANAGE STAKEHOLDER ENGAGEMENT
• Mengelola Keterlibatan Pemangku
Kepentingan adalah proses berkomunikasi
dan bekerja dengan pemangku kepentingan
untuk memenuhi kebutuhan/harapan
mereka, mengatasi masalah yang terjadi, dan
mendorong keterlibatan pemangku
kepentingan yang sesuai dalam kegiatan
proyek sepanjang siklus hidup proyek.
 Managing
Project Scope
 Manajemen Lingkup Proyek
• Manajemen Lingkup Proyek tidak
mengalami perubahan besar dalam hal
proses, koreksi nama, dll. Namun,
perubahan dalam pendekatan siklus
hidup selaras dengan manajemen
lingkup dan perubahan umum pada alat
dan teknik memengaruhi area
pengetahuan ini.
 Key concepts for Project Scope Management
CONCEPT PREDICTIVE LIFECYCLE ADAPTIVE / AGILE LIFECYCLE

Deliverables are developed over multiple

Defined in the beginning of the project and
Project iterations. In each iteration the detaled scope is
changes are managed through progressive
deliverables defined and approved at the beginning of the
elaboration and change control
iteration.

Requirements are termed as product backlog

Collect requirements, Define scope and create
and the three proceeses (Collect requirements,
WBS processes are performed in the
Requirements beginning and updated as needed through
Define scope and create WBS) are performed
in each iteration. Prioritized requirements are
integrated change control
delivered within each iteration

Project Scope statement, WBS and WBS

dictionary form part of scope baseline. This is
Product backlog is used in place of Scope
Scope baseline compared with the deliverables during
baseline
verification ( Control Quality ) and validation (
Validate Scope)
 Tugas
• Setiap kelompok menentukan studi kasus
berbentuk pengabdian masyarakat dan judul
proyek. Kemudian buat dokumen berikut:
– Project Charter
– Project Scope Statement
• Pilih Project Manager dan Project Manager
Assistance pada setiap kelompok.
• Tugas dikumpulkan pada e-learning dalam
bentuk .pdf maksimal Sabtu, 16 Oktober 2021
pukul 23.59.
• Pendahuluan (Project Charter) • Project Scope Statement
– Pendahuluan/ Latar Belakang – Overview
– Tujuan Bisnis • Daftar dokumen output
– Situasi Terkini dan Pernyataan Masalah/ Peluang – Tahap Pembuatan
– Asumsi Kritis dan Batasan – Project scope statement
– Analisa dari Rekomendasi PIlihan – Collect Requirement
– Pendahuluan Kebutuhan Proyek • Requirement Documentation
– Estimasi Anggaran dan Analisa Keuangan* – Requirement Management Plan
– Estimasi Penjadwalan* – Pengkategorian Kebutuhan
– Potensi Resiko – Prioritas Kebutuhan
• Traceability Matrix
*buat perkiraan, detail menyusul setelah dijelaskan pada – Configuration Management
pertemuan selanjutnya. – Scope Statement
– Syarat Penerimaan Produk
– Batasan Finances*
• Rincian Gaji Tim Proyek
• Rincian Hardware

Template Dokumen –
• RINCIAN ADMINISTRASI (PRINT + FOTOCOPI +
KONSUMSI)
Batasan dari pihak Tim Proyek
– Batasan Admin Klien dan User
– Asumsi Tim Proyek
– Kriteria Penerimaan Produk
– Pengecualian Proyek
THANK YOU