Pito Sumarno
Setiap proses bisa melibatkan usaha dari satu atau lebih orang atau group
individu (tergantung kebutuhan proyek). Setiap terjadi proses minimal sekali
pada setiap proyek dan terjadi dalam sekali atau lebih pada fase proyek jika
proyek dibagi menjadi beberapa fase.
Terminologi Scope pada proyek dapat mengacu pada :
Product Scope :
Project Scope :
Fitur dan fungsi yang memiliki karakteristik suatu produk, jasa, atau hasil.
2
PMBOK p. 103
PMBOK p. 107-108
PMBOK p. 109-112
PMBOK p. 112-118
PMBOK p. 118-119
PMBOK p. 119-122
Pito Sumarno
PMBOK p. 103
PROJECT SCOPE
MANAGEMENT
5.1 Scope Planning
1 Inputs
.1. Enterprise environmental factors
.2. Organizational process assests
3. Project Charter
4. Preliminary Project scope statement
.5. Project Management Plan.
2 Tools and Technniques
.1. Expert Judgment
.2. Templates, Forms, standards
3 Outputs
.1. Project scope management plan
1 Inputs
.1. Organizationals process assests
.2. Project charter
.3. Preliminary project scope statement
.4. Project scope management plan
.5. Approved change requests
2 Tools and Technniques
.1. Product Analisys
.2. Alternative identification
.3. Expert judgment
.4. Stakeholder analysis
.3 Outputs
.1. Project scope statement
.2. Requested changes
.3. Project scope management plan
(updates)
Overview
5.3 Create WBS
1 Inputs
.1. Organizational process assets
.2. Project scope statement
.3. Project scope management plan
.4. Approved change requests
2 Tools and Technniques
.1. Work breakdown structure
templetes
.2. Decomposition
3 Outputs
.1. Project scope statement
(updates)
.2. Work breakdown structure
.3. WBS dictionary
.4. Scope baseline
.5. Project scope management plan
(updates)
.6. Requested changes
3 Outputs
.1. Project scope statement (update)
.2. WBS (updates)
.3. WBS dictionary (updates)
.4. Scope baseline (updates)
.5. Requested changes
.6. Recommended corrective action
.7. organizational process assets
(updates)
.8. Project management plan (updates)
Pito Sumarno
PMBOK p. 103
Develop Project
Charter 4.1
Project Charter
(3.2.1.1)
Dvelop Preliminary
Project Scope
Statement 4.2
(3.2.1.2)
Performance
Reporting
Create WBS
5.3
(3.2.2.4)
4.7
(3.2.5.1)
Performance Reports
Requested Changes
Deliverables
Scope
Verification
5.4
(3.2.4.3)
Accepted Deliverables
10.3
(3.2.4.9)
Close Project
Organizational
Process Assets
4.4 (3.2.3.1)
Develop Project
Management Plan
4.3
(3.2.2.1)
Scope
Definition
5.2
(3.2.2.3)
Enterprise
Environmental
Factors
Scope
Planning
5.1
(3.2.2.2)
Scope Control
5.5
(3.2.4.4)
Pito Sumarno
Requested Changes
Recommended Corrective Actions
Project Management Plan (updates)
Project Scope Statement (updates)
WBS (updates)
WBS Dictionary (updates)
Integrated
Scope Baseline (updates)
Change
Control
4.6
(3.2.4.2)
PMBOK p. 106
5. 1. SCOPE PLANNING
Penjelasan dan pengelolaan Scope proyek yang akan mempengaruhi
kesuksesan proyek secara keseluruhan.
Setiap proyek memerlukan kehati hatian dalam menyeimbangkan
penggunaan peralatan, sumber data, metodologi, prosedur dan proses, dan
lain faktor untuk memastikan bahwa usaha yang telah dilakukan dalam
kegiatan scoping adalah setaraf dengan ukuran proyek, kompleksitas, dan
kepentingannya.
PMBOK p. 107
5. 1. SCOPE PLANNING
.1. Enterprise environmental factors
INPUTS
.1.
.2.
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
Existing human resources (e.g., skiils, disciplines, and knowledge, such as design,
development, legal, contracting, and purchasing)
Personnel administration (e.g., hiring and firing guidelines, employee performance
reviews, and training records)
Company work authorization system
Marketplace conditions
Stakeholder risk tolerances
Commercial databases (e.g., standardized cost estimating data,
industry risk study information, and risk databases)
Project management information systems (e.g., an automated tool suite, such as a
scheduling sofware tool, a configuration management system, an information
collection and distribution system,Pito
or Sumarno
webinterface
to other online automated 7
PMBOK p. 83
system)
5. 1. SCOPE PLANNING
INPUTS
.1.
.2.
3.
Organizational standard processes, such as standards,
4.
policies(e.g., safety and health policy, and project
management policy), standard product and project life
cycles, and quality policy and procedurs (e.g., process audits, .5.
improvement targets, checklists, and standardized process
definitions for use in the organization).
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
Guideline and criteria for tailoring the organizations set of standard processes to
satisfy the specific needs of the project.
Organization communication requirements (e.g., specific communication
technology available, allowed communication media, record retention, and
security requirements).
Pito Sumarno
PMBOK p. 84
5. 1. SCOPE PLANNING
.2. Organizational process assests (2-4)
Project closure guidelines or requirements (e.g., final
project audits, project evaluations, product validations,
and acceptance criteria)
Financial controls procedures (e.g., time reporting,
required expenditure and disbursement reviews,
accounting codes, and standard contract provitions)
INPUTS
.1.
.2.
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
Issue and defect management procedures defining issue and defect controls,
issue and defect identification and resolution, and action item tracking.
Change control procedures, including the steps by which official company
standards, policies, plans, and procedurs or any project documents will be
modified, and how any changes will be approved and validated.
Risk control procedurs, including risk categories, probability definition and impact,
and probability and impact matrix.
Procedures for approving and issuing work authorizations.
Pito Sumarno
5. 1. SCOPE PLANNING
.2. Organizational process assests (3-4)
INPUTS
.1.
.2.
3.
4.
.5.
retrieving information:
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
10
PMBOK p. 85
5. 1. SCOPE PLANNING
.2. Organizational process assests (4-4)
INPUTS
.1.
.2.
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
Pito Sumarno
11
5. 1. SCOPE PLANNING
.3. Project Charter ( 4.1)
INPUTS
(1-2)
Manajer Proyek.
Dikeluaran sebelum proyek mulai perencanaan
.1.
.2.
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
Pito Sumarno
PROJECT
CHARTER
12
PMBOK p. 81
5. 1. SCOPE PLANNING
.3. Project Charter ( 4.1)
INPUTS
(2-2)
.1.
.2.
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
13
PMBOK p. 82
5. 1. SCOPE PLANNING
.3. Project Charter ( 4.1)
(2-2)
.1.
.2.
Business need :
INPUTS
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
Pito Sumarno
14
5. 1. SCOPE PLANNING
INPUTS
.1.
.2.
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
Approval Requirements
15
PMBOK p. 86
5. 1. SCOPE PLANNING
INPUTS
.1.
.2.
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
16
PMBOK p. 86
5. 1. SCOPE PLANNING
.5. Project Management Plan (4.3):
INPUTS
.1.
.2.
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
17
PMBOK p. 88
5. 1. SCOPE PLANNING
.5. Project Management Plan (4.3):
Project Management Plan bisa diringkas atau dibuat rinci, dan bisa
INPUTS
.1.
.2.
3.
4.
.5.
Inputs :
Enterprise
environmental factors
Organizational process
assests
Project Charter
Preliminary Project
scope statement
Project Management
Plan.
Pito Sumarno
18
PMBOK p. 89
5. 1. SCOPE PLANNING
Expert Judgment
adalah Pertimbangan dari tenaga ahli sebagai (masukan) yang sering
digunakan untuk menilai pada suatu proses seperti halnya keahlian. Mungkin
berasal dari kelompok lain atau secara individu dengan pendidikan atau
pengetahuan khusus dan tersedia dari banyak sumber daya.
Pertimbangan terkait dengan bagaimana kesetaraan proyek yang telah mengelola
scope tersebut digunakan untuk pengembangan project scope management
plan.
Pito Sumarno
19
PMBOK p. 108
5. 1. SCOPE PLANNING
OUTPUTS
Outputs
.1. Project scope
management plan
control process.
Pito Sumarno
Scope
Definition
20
5. 2. SCOPE DEFINITION
Persiapan yang sangat kritis dalam merinci project scope statement
terhadap kesuksesan proyek dan membangun sepanjang hasil proyek,
asumsi, dan batasan batasannya di dokumentasikan dari initiasi proyek
didalam preliminary project scope statement.
Sepanjang perencanaan, project scope digambarkan dan diuraikan
dengan ketegasan yang lebih besar sebab informasi tentang project
lebih dikenal. Kebutuhan, keinginan, dan ekspektasi stakeholder
dianalisis dan diubah menjadi persyaratan.
Asumsi dan batasan batasan dibutuhkan dan dianalisis untuk
melengkapinya.
Pito Sumarno
21
PMBOK p. 109
5. 2. SCOPE DEFINITION
.1. Organizationals process assests
INPUTS
4.1.1.4 p 84
.1.
.2.
.3.
.4.
.5.
Inputs :
Organizationals process
assests
Project charter
Preliminary project scope
statement
Project scope management
plan
Approved change requests
p.108
4.4.1.4 p. 92
Didokumentasikan, diberikan hak atas perubahan untuk memperluas
contract project scope.
Approved change requests dapat juga merubah kebijakan, project
management plan, procedures, quality, costs, budgets atau merevisi
schedule. Perubahan sering diidentifikasi dan disetujui pada
pekerjaan yang sedang berjalan.
Pito Sumarno
22
PMBOK p. 109
5. 2. SCOPE DEFINITION
.1. Product Analysis
p 110
.1.
.2.
.3.
.4.
functional analysis.
Pito Sumarno
23
PMBOK p. 110
5. 2. SCOPE DEFINITION
.2. Alternatives Identification
p. 110
.1.
.2.
.3.
.4.
lateral thingking
p.110
Pito Sumarno
24
PMBOK p. 110
5. 2. SCOPE DEFINITION
.4. Stakeholder Analysis
p.110
.1.
.2.
.3.
.4.
Pito Sumarno
25
PMBOK p. 110
5. 2. SCOPE DEFINITION
OUTPUTS
Outputs
.1. Project scope
statement
.2. Requested changes
.3. Project scope
management plan
(updates)
Fund limitation
Cost estimate
Project configuration management requirements
Project specifications
Approval Requirements
Pito Sumarno
26
PMBOK p. 110
5. 2. SCOPE DEFINITION
OUTPUTS
ASSUMPTIONS
Outputs
.1. Project scope
statement
.2. Requested changes
.3. Project scope
management plan
(updates)
Rp
yaitu faktor yang akan membatasi
tim manajemen proyek dalam
menentukan pilihan; sebagai
contoh adalah penentuan
maksimum jangka waktu kegiatan
yang diinginkan.
27
PMBOK p. 111
5. 2. SCOPE DEFINITION
.2. Requested changes p.112
OUTPUTS
Outputs
.1. Project scope
statement
.2. Requested changes
.3. Project scope
management plan
(updates)
Create
WBS
Pito Sumarno
28
PMBOK p. 112
5. 3. CREATE WBS
WBS adalah suatu hirarki dari susunan komponen Proyek/total lingkup
proyek yang dipecah dengan mengelompokkan menjadi lebih kecil
yang menggambarkan suatu deliverable proyek yang dilaksanakan oleh
tim proyek.
WBS menyajikan pekerjaan yang ditetapkan pada project scope
statement yang telah disetujui.
Beberapa komponen WBS membantu stakeholder didalam mengamati
deliverable proyek ( 4.4.3.1)
Pekerjaan yang tidak termasuk di dalam WBS adalah di luar lingkup
proyek.
Biasanya ditunjukkan dalam bentuk Chart/ bagan.
Jenis pada tingkatan terendah dari WBS adalah dikenal sebagai paket
pekerjaan (work package)
Pito Sumarno
29
PMBOK p. 112
5. 3. CREATE WBS
.1. Organizationals Process Assests 4.1.1.4
INPUTS
.1.
.2.
.3.
.4.
Inputs :
Organizational process
assets
Project scope statement
Project scope management
plan
Approved change requests
Pito Sumarno
30
PMBOK p. 113
5. 3. CREATE WBS
31
PMBOK p. 113
5. 3. CREATE WBS
TOTAL PROGRAM
MANAGERIAL
LEVEL
PROJECT
TASK
TECHNICAL
LEVEL
WORK
PACKAGE
PROJECT
TASK
PROJECT
TASK
SUB TASK
SUB TASK
WORK
PACKAGE
WORK
PACKAGE
LEVEL OF
EFFORT
LEVEL OF
EFFORT
Pito Sumarno
LEVEL 1
PROJECT
LEVEL 2
LEVEL 3
SUB TASK
LEVEL 4
LEVEL 5
LEVEL OF
EFFORT
LEVEL 6
32
5. 3. CREATE WBS
.2. Decomposition
Adalah merinci proyek deliverables ke dalam komponen lebih
kecil, yang dapat dikendalikan sampai ke pekerjaan dan
deliverables ditetapkan ke tingkatan paket pekerjaan.
Paket pekerjaan adalah tingkatan yang paling rendah dalam
WBS, dan yang pokok di mana biaya dan jadwal pekerjaan
dapat diperkirakan secara realistis.
Step decomposisi :
WBS
Level
3
WBS
Level
3
WBS
Level 1
WBS
Level 2
WBS
Level
3
Pito Sumarno
WBS
Level
3
WBS
Level
3
WBS
Level 2
WBS
Level
3
WBS
Level
3
WBS
Level
3
WBS
Level
3
33
PMBOK p. 115
5. 3. CREATE WBS
OUTPUTS
MEKANIKAL &
ELEKTRIKAL
01.02
BANGUNAN
01.01
SUBSTRUKTUR
01.01.01
STRUKTUR
ATAS
01.01.02
LEVEL 1
FINISHING
01.01.03
ELEKTRIKAL
ARUS KUAT
01.02.01
ELEKTRIKAL
ARUS LEMAH
01.02.02
MEKANIKAL
UMUM
01.02.03
SITE
01.03.01
SAFETY
01.03.02
KOLOM
LT.1-40
01.01.02.01
DINDING
LT.1-40
01.01.03.01
EL.STD
LT.1-40
01.02.01.01
TLP.LT.1-40
01.02.02.01
PLUMBING
LT.1-40
01.02.03.01
SITE
CLEARING
01.03.01.01
ACC.ROAD
01.03.02.01
PONDASI
01.01.01.02
PLAFOND
LT.1-40
01.01.03.02
EL.N0NSTD
LT.1-40
01.02.01.02
T.SUARA
LT.1-40
01.02.02.02
HVAC
LT.1-40
01.02.03.02
SITE
FACILITIES
01.03.01.02
GEDUNG
01.03.02.02
URUGAN
KEMBALI
01.01.01.03
TANGGA
LT.1-40
01.01.02.03
LANTAI
LT.1-40
01.01.03.03
EL.KUSUS
LT.1-40
01.02.01.03
MATVCCTV
LT.1-40
01.02.02.03
LIFT/ESC
LT.1-40
01.02.03.03
EQUIP.
01.03.01.03
GALIAN &
DEWATERING
01.01.01.01
DIAFR.WLL
01.01.01.02.
01
FW.BLK&PL
LT.1-40
01.01.01.02.
01
PL.ACUS
LT.1-40
01.01.03.02.
01
COND
LT.1-40
01.02.01.01.
STRT
01.01.01.02.
02
BS.BLK&PL
LT.1-40
01.01.01.02.
02
BALANC.
01.01.01.02.
03
PR.BLK&PL
LT.1-40
01.01.01.02.
03
01
COND
LT.1-40
01.02.02.01.
01
AIR BERSIH
LT.1-40
01.02.03.01.
01
TC
01.03.01.03.
01
PL.GYP
LT.1-40
01.01.03.02.
02
KABEL
LT.1-40
01.02.01.01.
02
KABEL
LT.1-40
01.02.02.01.
02
AIR KOTOR
LT.1-40
01.02.03.01.
02
LIFT ORG
01.03.01.03.
02
PL.MET
LT.1-40
01.01.03.02.
03
ARMATUR
LT.1-40
01.02.01.01.
03
PABX&UNIT
LT.1-40
01.02.02.01.
03
HYDRAN
LT.1-40
01.02.03.01.
03
SCHAFF
01.03.01.03.
03
Pito Sumarno
LEVEL 2
Outputs
.1. Project scope
statement (updates)
.2. Work breakdown
structure
.3. WBS dictionary
.4. Scope baseline
.5. Project scope
management plan
(updates)
.6. Requested changes
LEVEL 3
LEVEL 4
LEVEL 5
WBS
SAMPLE
34
PMBOK p. 117
Manufacturing
Engineering
General
Manager
Procurement
Organizational
Breakdown Structure
(OBS) :
Work Breakdown
Structure (WBS) :
Resources Breakdown
Structure (RBS) :
Project
Activity
Short by
Row Mat
Bill of
Quantity
(BOQ)
Noahs Ark
Project
Project
Activity
Ship
Structure
Navigation
equipment
Short by
Site
Short by
Fab/Sub
Bill of
Material
(BOM)
Crew
Training
Project
Activity
Multifunctional Team
Control Account Plans
(CAPs)
Pito Sumarno
35
Technical
Organizational
Project
management
Requirements
Subcontractor
& Suppliers
Project
Dependencies
Estimating
Technology
Regulatory
Resources
Planning
Complexity
& Interface
Market
Founding
Controlling
Performance
& Reliability
Customer
Prioritization
Communication
Quality
Weather
Pito Sumarno
36
PMBOK p. 244
5. 3. CREATE WBS
.3. WBS dictionary :
OUTPUTS
Outputs
.1. Project scope
statement (updates)
.2. Work breakdown
structure
.3. WBS dictionary
.4. Scope baseline
.5. Project scope
management plan
(updates)
.6. Requested changes
Approved detail project scope statement dan yang terkait dengan WBS dan WBS
dictionary adalah scope baseline untuk proyek.
Jika hasil Change request disetujui dari proses Create WBS, kemudian Project scope
management plan perlu di update meliputi persetujuan perubahan.
PMBOK p. 117
37
5. 4. SCOPE VERIFICATION
Adalah proses dari memperoleh persetujuan secara
formal terhadap lingkup proyek dari stakeholders. Hal ini
memerlukan me review deliverables untuk memastikan
bahwa semua telah diselesaikan dengan tepat dan
dengan memuaskan.
Utamanya adalah perhatian terhadap persetujuan
deliverables
Pito Sumarno
PMBOK p. 117
38
5. 4. SCOPE VERIFICATION
.1. Project scope statement
.3. WBS dictionary
INPUTS
.1.
.2
.3.
.4.
Inputs :
Project scope statement
WBS dictionary
Project scope management
plan
Deliverables
Pito Sumarno
PMBOK p. 117
39
5. 4. SCOPE VERIFICATION
.1. Inspection
Pito Sumarno
PMBOK p. 119
40
5. 4. SCOPE VERIFICATION
.1. Inspection
Audit berbasis risiko :
41
5. 4. SCOPE VERIFICATION
.1. Accepted deliverables
OUTPUTS
Outputs
.1. Accepted
deliverables
.2. Requested changes
.3. Recommended
corrective acctions
Pito Sumarno
PMBOK p. 119
Scope
Control
42
5. 5. SCOPE CONTROL
Project Scope Control adalah terkait dengan pengaruh faktor yang
menciptakan perubahan project scope dan pengendalikan dampak dari
perubahan tersebut.
Pito Sumarno
PMBOK p. 119
43
5. 5. SCOPE CONTROL
.1. Project scope statement
Sepanjang terkait dengan WBS dan WBS Dictionary
5.3, menggambarkan projects scope baseline dan
product scope.
INPUTS
Inputs :
.1. Project scope statement
.2. WBS
.3. WBS dictionary
.4. Project scope management
plan
.5. Performance reports
.6. Approved change requests
.7. Work performance
information
PMBOK p. 120
44
5. 5. SCOPE CONTROL
INPUTS
Inputs :
.1. Project scope statement
.2. WBS
.3. WBS dictionary
.4. Project scope management
plan
.5. Performance reports
.6. Approved change requests
.7. Work performance
information
Schedule activities that have started and those that have been
finished
Extent to which quality standards are being made
Cost authorized and incurred
Estimates to complete the schedule activities that have started
Percent physically complete of the in-progress schedule activities
Documented lessons learned posted to the lessons learned
knowledge base
Resource utilization detail
Pito Sumarno
PMBOK p. 94
45
5. 5. SCOPE CONTROL
PMBOK p. 121
46
5. 5. SCOPE CONTROL
.3. Replanning
Persetujuan permintaan perubahan yang berdampak
pada project scope dapat dilakukan modifikasi WBS
dan WBS dictionary, project scope statement, dan
PMBOK p. 121
47
5. 5. SCOPE CONTROL
.1. Project scope statement (updates)
OUTPUTS
Outputs
.1. Project scope statement
(update)
.2. WBS (updates)
.3. WBS dictionary
(updates)
.4. Scope baseline (updates)
.5. Requested changes
.6. Recommended corrective
action
.7. organizational process
assets (updates)
.8. Project management
plan (updates)
PMBOK p. 121
48
5. 5. SCOPE CONTROL
OUTPUTS
Outputs
.1. Project scope statement
(update)
.2. WBS (updates)
.3. WBS dictionary
(updates)
.4. Scope baseline (updates)
.5. Requested changes
.6. Recommended corrective
action
.7. organizational process
assets (updates)
.8. Project management
plan (updates)
PMBOK p. 122
49
Pito Sumarno
50