Manajemen Proyek

Pertemuan 2 – PNJ
Project Management Process

16 Maret 2019

Kar Ferri Novezar, ST, MT, PMP

47 Processes PMBOK 5th Edition
Project Phase, Project & Product Cycle

• Project phase: “A collection of logically related project

activities usually culminating in the completion of a
major deliverable.”
• Project phases vary by project or industry, but some
general phases include
▫ concept
▫ development
▫ implementation
▫ support
• Project life cycle: “Collectively the project phases are
known as the project life cycle.”
• Product life cycle: The natural grouping of ideas,
decisions, and actions into product phases, from product
conception to operations to product phase-out.
Project Life Cycle vs Project Management
Life Cycle
Construction Project Life Cycle
Defining the Product Life Cycle
Project and Product Life Cycle
Sample Project to Explain Project Process & Cycle
Sample Project to Explain Project Process &
Cycle
Project Organization
• Seperti apa bentuk organisasi proyek atau
struktur proyek di perusahaan anda
Functional Organization
Weak Matrix Organization
Balanced Matrix Organization
Strong Matrix Organization
Projectized Organization
Matrix vs Function and Projectize
PMO Role

• Supportive
▫ Consultative role, supply templates, best practice,
training, lesson learn. Degree to control project is low
• Controlling
▫ Provide support and require compliance (project
framework/methodologies, template, form, tools,
governance)
▫ Degree to control project is moderate
• Directive
▫ Control the project by directly managing the project
▫ The Project Manager is assigned by and report to the
PMO
▫ Degree to control project is high
Latihan
1. Seorang staff A dari Divisi Planning PT ABC
ditunjuk untuk ikut dalam proyek implementasi
jaringan IT pada kantor cabang PT ABC
2. Seorang staff B dari Divisi Project 3 PT XYZ
sedang menyiapkan laporan proyek kepada
Project Managernya
• Apa bentuk organisasi pada soal no 1
• Apa bentuk organisasi pada soal no 2
• Jelaskan keuntungan dan kerugian pada kedua
bentuk organisasi proyek tersebut
Project Management Processes
• Regardless of the type of project lifecycle, project
management encompasses the following process groups,
shown with some representative tasks:
1. Initiating/Define – Scope the project; Charter the project; identify
stakeholders
2. Planning – Develop the project plan. Collect requirements; identify
schedule; plan scope, cost, quality, human resource, risk, and
procurement management
3. Executing – Launch the plan. Direct and manage project work;
perform quality assurance; manage and develop project team; conduct
procurements
4. Monitoring and Controlling – Monitor project progress. Monitor
and control project work; manage scope change; monitor and control
schedule; control quality; control risks; control procurements
5. Closing – Close out the project: Close project; close procurements
Project Management Process
Initiating Processes Overview
• Initiating processes define a new project or new phase of an existing project
• Initial project scope, project stakeholders, and project manager are identified
• Key purposes are to:
▫ Align the stakeholders' expectations with project purpose
▫ Give stakeholders visibility into project scope and objectives
▫ Demonstrate that stakeholder participation helps ensure project success
• All of these set the vision of the project: what needs to be accomplished
Initiating Process
Initiating Processes

• Develop Project Charter

▫ Justifies and formally authorizes a project or a project phase
▫ Documents the stakeholders’ initial requirements and
expectations
▫ Forms the basis for the partnership between the requesting
(customer) and performing (supplier) organizations
• Identify Stakeholders
▫ Identifies all people or organizations impacted by the project
▫ Documents their interests and involvement with the project,
as well as their potential impact on project success
▫ Forms the basis for developing a strategy to approach and
involve each stakeholder to maximize positive influences and
minimize negative influences
Stakeholder of the Project,
PMBOK 5th Edition, page 31
Key Project Stakeholder Roles

• Customer. Person or organization that acquires product

• User. Person or organization that uses product
• Performing organization. Organization performing work of project
• Project manager. Responsible for managing project
• Project management team. Individuals directly involved in project
management activities
• Project team members. Individuals performing work of project
• Sponsor. Entity providing financial resources for project
• PMO. Project management office. Responsible for centralized and
coordinated management of all projects under its supervision
Project Charter Content

• Project Charter, includes:

▫ Project purpose or justification,
▫ Measurable project objectives and related success criteria,
▫ High-level requirements,
▫ High-level project description,
▫ High-level risks,
▫ Summary milestone schedule,
▫ Summary budget,
▫ Project approval requirements
▫ Assigned project manager, responsibility, and authority
level
▫ Name and authority of the sponsor or other person(s)
authorizing the project charter.
Project Charter Content

• Project purpose or justification

▫ Define the reason why the project is being done, by referring to
any of the Initiating process inputs
• Measurable project objectives and related success
criteria
▫ Scope. Scope needed to achieve project goals and measurable
criteria for scope success
▫ Time. Goals for timely completion and specific dates for success
▫ Cost. Goals for project expenditures and range of costs for success
▫ Quality. Quality criteria and specific measures for criteria for
success
▫ Other. Any other objectives along with measurable criteria of
success
Project Charter Content

• High-level requirements
▫ Describe the high-level product capabilities that
satisfy stakeholder needs and expectations. Do not
include detailed requirements
 Example: Customer request redundant circuit from
Jakarta to Surabaya with BW 1 G
Project Charter Content

• Assumptions and constraints

▫ An assumption is “a thing that is accepted as true
or as certain to happen, without proof”
 Example: The capacity is ready, no issue on site
acquisition.
▫ A constraint is a limitation or restriction
 Example: Permit to deploy the network
Project Charter Content

• High-level project description and boundaries [scope]

▫ Provide an executive-summary-level description of the
project, identify what will and will not be included in the
project
 Example: The network provided is until customer port … It will
not provide customer network configuration
• High-level risks
▫ Risks represent any major areas of uncertainty for the
project
▫ Risks may be internal or external
 Example: Interoperability with customer equipment
 Example: Over budget due to long deployment and uncertainty
Project Charter Content

• Summary milestone schedule

▫ Identify any significant points or events in the project, such
as key deliverables, beginning or ending of phases, or
product acceptance
▫ Include estimated completion dates for the milestones
 Examples: On site survey complete on: 1/31/2016; Installation
complete on: 4/30/2016
• Summary budget
▫ Provide a rough order of magnitude (ROM) estimate of
expenditures schedule for project
 ROM estimates may be as broad as ±100% but usually range
±35%
▫ Budget should break down total expenditures by major
categories (software, hardware, human resources, etc.)
Project Charter Content

• Stakeholder list
▫ A stakeholder is “a[n] individual, group, or
organization who may affect, be affected by, or
perceive itself to be affected by a decision, activity, or
outcome of a project”*
▫ Identify a preliminary list of the most critical project
stakeholders–this list will be refined later
• Project approval requirements
▫ Identify any criteria that must be met in order for the
project to be accepted by the project customer
▫ Example: The delivered project shall be referred to
agreed design with customer
Project Charter Content

• Project manager, responsibility, and authority levels

▫ Staffing. Specific authority project manager is granted to
hire/fire, discipline, or accept/reject project staff
▫ Budget management and variance. Specific authority project
manager is granted to commit, manage, and control project
funds; also, what variance requires higher approval
▫ Technical decisions. Specific authority project manager is granted
regarding deliverable technical decisions or project approach
▫ Conflict resolution. Specific authority the project manager is
granted to resolve team and organizational conflict, as well as
conflict with external stakeholders
▫ Escalation path for authority limitations. Define the path for
escalation of issues exceeding the project manager’s authority
• Name and authority of the sponsor or other person(s)
authorizing the project charter
Contoh Templat Project Charter
Project Charter then Kick off Meeting

• Charters are normally short and include key

project information and stakeholder signatures
• It’s good practice to hold a kick-off meeting at
the beginning of a project so that stakeholders
can meet each other, review the goals of the
project, and discuss future plans
Project Kick-off Pre-Requisites

• The project charter is finalized and signed off.

• A sufficient budget has been allocated to the project (for
the next phase or for the entire project).
• The project is approved to proceed by the sponsor.
• A project manager / project lead is assigned.
• The tasks/activities are defined at a high level and
resource requirements have been estimated.
• Required resources have been formally assigned to the
project and have confirmed attendance at the kick-off
meeting.
Purpose of Kick off Meeting

• The project kick-off meeting is the first opportunity a Project

Manager has to energize the project team and establish a common
purpose toward completing the work.
• An effective kick-off meeting will ensure that all project team
members have an understanding of
▫ the project objectives
▫ scope and constraints
▫ each team members' role and responsibility in the project
▫ the high level work plan (deliverables and milestones)
▫ how to track their time on the project
▫ where project documentation will be located
• The goal is to get everyone up to speed but not to discuss every item
in detail.
Tugas – Membuat Project Charter

• Project Pembangunan Jaringan Internet antar

Fakultas di PNJ
▫ Requirement:
 Kapasitas internet di masing2 Fakultas sebesar 100
Mbps
 Jaringan utama antar Fakultas menggunakan
jaringan FO
 Penyebaran internet di dalam Fakultas
menggunakan Access Point
 Target penyelesaian selama 6 bulan