1 PROJECT MANAGEMENT COURSE 1 : OVERVIEW & INTRODUCTION G.N. Sandhy Widyasthana [email protected] 022‐70702020 081 225 702020
1
PROJECT MANAGEMENTCOURSE 1 : OVERVIEW & INTRODUCTION
G.N. Sandhy [email protected]
022‐70702020081 225 702020
2
Brief Introduction
• Education– Electro STT Telkom (S1) 1991‐1995– MBA ITB (S2) 2004‐2006
• Certification :– PMP from Project Management Institute USA– Lead Auditor from Bay water Australia– CCNA from Cisco
• Working Experience :– Reliability & Security Lab, TelkomRDC– Integrity & Security Lab, TelkomRDC– Business Competitiveness Lab, TelkomRDC– Subdit Tariff, Dit NWS
3
Feedback From Student
• Student background (semester, major etc)
• Expected output from Project Management Course
• Choose Ketua Kelas
• Forming group (3‐4 person for each group)
4
Rules
• No Copycat– Discuss and writing by yourself– Don’t forget to write reference
• Schedule : – Friday : 13.20 – 15.00 proposed change to Saturday 11.30 – 13.00– Saturday : 13.20 – 15.00
• Present minimum 75 % from all courses– Absent check– Late not more than 15 minutes
• Point– Class & Group Activity : 10 %– UTS : 25 %– Group Assignment : 30 %– Tugas Besar / UAS : 35 %
55
Satuan Acara Pengajaran
• Problem Based Learning
• 18 Lecturer + 1 Guest Speaker
• 6 case (presentation format) + 1 final case (paper format)/UAS
66
Satuan Acara Pengajaran
• Course 1 : Definisi Proyek dan Manajemen Proyek• Course 2 : Lingkungan Proyek• Course 3 : Organisasi Proyek• Course 4 : Tim Kerja dan Peranan Unit Organisasi• Course 5 : Tender dan Kontrak Proyek• Course 6 : Tahap Perencanaan dan WBS• Course 7 : Jaringan Kerja, PERT dan GANTT Chart• Course 8 : CPM dan Aplikasi Sumber Daya• Course 9 : Crash Program
77
Satuan Acara Pengajaran
• Course 10 : Perkiraaan Biaya dan Owner Estimate • Course 11 : Pengendalian Proyek dan S Curve• Course 12 : BCWS, ACWP dan BCWP• Course 13 : Analisis Variansi• Course 14 : Kinerja Proyek (CPI dan SPI)• Course 15 : Pelaporan Proyek• Course 16 : Audit Proyek• Course 17 : Terminasi Proyek• Course 18 : Evaluasi Proyek
8
What is a Project?• A project is a temporary endeavor undertaken to produce a unique product or service
– Temporary – Definitive beginning and end
– Unique – New undertaking, unfamiliar ground
Temporary UniqueCharacteristics of Projects
9
10
Project Success
Customer Requirements satisfied/exceeded
Completed within allocated time frame
Completed within allocated budget
Accepted by the customer
11
Project Failure
Scope Creep Poor Requirements Gathering
Unrealistic planning and scheduling
Lack of resources
12
What is Project Management•Project Management is the application of skills, knowledge, tools and techniques to meet the needs and expectations of stakeholders for a project.
– The purpose of project management is prediction and prevention, NOT recognitionand reaction
13
Triple Constraint
Quality
ScopeScope
TimeTime
CostCost
14
Triple Contraint• Increased Scope = increased time + increased cost
• Tight Time = increased costs + reduced scope
• Tight Budget = increased time + reduced scope.
15
Key Areas of Project Management
• Scope Management
• Issue Management
• Cost Management
• Quality Management
• Communications Management
• Risk Management
• Change Control Management
16
Scope Management• Primarily it is the definition and control of what ISand IS NOT included in the project.
17
Issue Management• Issues are restraints to accomplishing the deliverables of the project.
• Typically identified throughout the project and logged and tracked through resolution.
Rope not thick
Issue… already impacting the cost, time or quality
18
Cost Management• This process is required to ensure the project is completed within the approved budget and includes:
Resourcespeopleequipmentmaterials
Quantities
Budget
19
Quality Management• Quality Management is the process that insure the project will meet the needs
“conformance to requirements” - Crosby
“fitness for use” - Juran
“the totality of characteristics of an entity that bear on its ability to satisfy stated and implied need’ - ISO 8402:1994
20
Communications Management• This process is necessary to ensure timely and appropriate generation, collection, dissemination, and storage of project information
21
Risk Management• Risk identification and mitigation strategy
• Risk update and tracking
Tree – location, accessibility, ownership
Weather
Risk… POTENTIAL negative impact to project
22
Change Control Management
• Define how changes to the project scope will be executed
Scope Change
Schedule changes
Technical Specification Changes
All changes require collaboration and buy in via the project sponsor’s signatureprior to implementation of the changes
23
Project Life Cycle
24
Initiation Phase• Define the need
• Return on Investment Analysis
• Make or Buy Decision
• Budget Development
25
Definition Phase• Determine goals, scope and project constraints
• Identify members and their roles
• Define communication channels, methods, frequency and content
• Risk management planning
26
Planning Phase• Resource Planning
• Work Breakdown Structure
• Project Schedule Development
• Quality Assurance Plan
27
Work Breakdown Structure• For defining and organizing the total scope of a project
• First two levels ‐ define a set of planned outcomes that collectively and exclusively represent 100% of the project scope.
• Subsequent levels ‐represent 100% of the scope of their parent node
28
Implementation Phase• Execute project plan and accomplish project goals
• Training Plan
• System Build
• Quality Assurance
29
Deployment Phase• User Training
• Production Review
• Start Using
30
Closing Phase• Contractual Closeout
• Post Production Transition
• Lessons Learned
31
Project Management Tools• PERT Chart‐ designed to analyze and represent the tasks involved in completing a given project
Gantt Chart ‐ popular type of bar chart that illustrates a project schedule
32
Role of a Project Manager
Process Responsibilities
People Responsibilities
• Project issues • Disseminating project information• Mitigating project risk • Quality • Managing scope • Metrics • Managing the overall work plan
• Implementing standard processes• Establishing leadership skills• Setting expectations• Team building• Communicator skills
33
Reference
• Avneet Mathur, Slide Introduction To Project Management
• PM BOK (Project Management Body Of Knowledge