The document discusses hybrid project management, particularly in the context of telecom and ICT projects. It outlines the differences between projects and operations, describes the role of project managers, and explains the hybrid methodology combining waterfall and agile approaches. Additionally, it highlights the importance of project management in maintaining clear communication, controlling changes, and tracking progress, ultimately emphasizing the need for a tailored approach in project management.

1. Hybrid project
management
Hardware project or Non-
software projects Management
Project
Hybrid

2. - Worked as Telecom Project Engineer @ Aker solutions
- Worked as ICT user support consultant @Amesto Firstpoint
- Interested in telecom, IT and Project management.
Aziz Alriddan PMP PRINCE2

3. Outline
• What is a project?
• What is project management?
• Project Timeline
• How project management is important? Why?
• Types of Projects?

4. What is a Project?
I want to
build a car
Everyday is
different
Has a duration Ends with a product
Starts with idea
Building a car project
Start date: Aug -2020
End date: Jun - 2021
The product is
a car
Not business as usual

5. Project vs Operations
• All work in Life is either, a project or Operation!
• Building a house
• Writing a book
• Going for a picnic
Project
• Help desk in DNB
• Network maintenance in Telenor
• Barista in Espresso Torgallmenningen
Operation

6. Business
Case
Feasibility
study
Project
Customer
request
Legal
requirement
Market
demand Organizational
need
Continuous
improvement
Go
or
No-go?
Business
need or
idea
Project timeline

7. - Project manager role in Hybrid and waterfall
projects can be analogised as a pilot

8. Project managers spend 90% of time on
communications
Communicating with:
- Project team
- Sponsor
- Management
- Client/customer/Users

9. Buidling an Oil
platform using
Hybrid Method
Waterfall + Agile

10. - Hybrid is a combination of Waterfall + Agile
Waterfall/Predictive
Building an Oil Platform
• Requirements are defined
• No significant changes
• Client/provider relationship
• COST of change is High.
Agile/Adaptive
building Facebook App
• Requirements are NOT defined
• Changes are common
• Partners relationship
• Cost of change is low.

11. Example of a Hybrid project
Platform A work breakdown structure WBS
Platform A
Project
Separator
installation Drilling
workshop
Oil meter
Compressor 1
Main deck
Drilling
Workshop
North Crane Wi-Fi
Network
Reporting system
AppTop deck
Control
room
Hull
buidling
Generator
Gauges Agile
Agile

12. Design
• Collect requirements from customer in iterations
• Build in increments
• Refine 3D prototype
Build
• Using Kanban board
Control
• Phase gates
• Quality checks
Using PDMS CAD software to pr

13. Types of Hybrid
• Agile On individual work package level
• Agile on phase level of a Predictive approach
• Both on Horizontal and vertical levels

14. Conclusion
It is about combining the best of the two
There is no Better off!
Use each when needed
Agile is working for us, not we working for Agile

15. Why project management is important?
• It is based on best practices
• It avoids ambiguity (No I thaught you meant this not that)
• It unites terminologies (All are on same page speak same language)
• It controls changes (Change has to be authorized)
• It tracks progress (avoids disappointment)
• It defines roles and responsibilty (Battery limit)