Video summary
04 | Key Project Management Terms for the Initiation Phase | Construction Management
Main summary
Key takeaways
Summary
Hany Ismail introduces foundational project-management terms relevant to the initiation phase, focusing on how projects are organized, how stakeholders are managed, and how responsibilities and organizational roles are clarified.
Projects, programs, and portfolios
- Project: A temporary effort with a specific goal, such as delivering a product, service, or result.
- Program: A coordinated group of related projects managed together to achieve benefits or control that would be harder to achieve if the projects were managed separately.
- Example: Developing a city train facility could involve separate projects for stations, railways, train maintenance, advertising, and reservation software. The program is complete when its relevant projects are complete.
- Portfolio: A collection of projects, programs, and operations managed together to support strategic objectives.
- Example: A city-wide construction portfolio might include infrastructure programs—such as roads, metro, and airport projects—as well as residential and sports-facility projects.
- Portfolio management can help prioritize and share resources across programs and projects, and manage risks in line with strategic goals.
- A portfolio may contain programs, individual projects, or both. Projects within a portfolio do not necessarily need to be related to one another, unlike projects within a program.
Stakeholder management
A stakeholder is an individual who can affect or be affected by a project, internally or externally. Stakeholders may influence a project’s direction or outcome. For example, local residents may raise concerns that cause problems or delay work.
The session outlines this approach to stakeholder management:
- Identify stakeholders, for example by creating a stakeholder register.
- Assess each stakeholder’s interest and power using a low-to-high interest/power matrix:
- Low interest, low power: Monitor with minimal effort.
- High interest, low power: Keep informed. For example, people who regularly use a bridge under construction may care about its progress but have little decision-making power.
- Low interest, high power: Keep satisfied and address relevant comments or requirements, such as municipal regulations.
- High interest, high power: Engage closely and continue monitoring, since these stakeholders may significantly influence or change the project.
- Plan communication to keep stakeholders appropriately informed and engaged.
- Engage stakeholders in suitable ways, such as through emails or meetings, according to their interests and influence.
Project charter
A project charter is a foundational document that sets out the project’s scope, deliverables, constraints, and stakeholders. It serves as an agreement between the project sponsor and team, providing direction and authority to proceed while establishing expectations. A charter may be only one or two pages.
Organizational Breakdown Structure and organization chart
These structures serve different purposes:
- Organizational Breakdown Structure (OBS): Shows the organization by function, department, or role and helps identify project roles and responsibilities. Examples include project manager, HSE manager, and construction manager.
- Organization chart: Shows the people in the organization and who reports to whom. If individuals have not yet been assigned, titles can be used initially and names added later.
RACI matrix
A RACI matrix clarifies responsibility for project tasks and helps prevent confusion:
- Responsible: Performs the task.
- Accountable: Owns the task’s success or failure and is answerable if something goes wrong.
- Consulted: Provides input or expertise.
- Informed: Is kept updated.
The speaker stresses that responsibility and accountability depend on the perspective and task being considered. Examples include:
- Supervising concrete work: The construction engineer is responsible; the project manager is accountable.
- Creating the project schedule: The planning engineer is responsible; the project manager is accountable; the construction engineer may be consulted.
- Attending a meeting with the CEO and top management: The project manager is responsible and may inform the construction and planning engineers.
- Preparing weekly and monthly reports: The planning engineer is responsible; the project manager is accountable; the construction engineer may be informed.
- Controlling timesheets: The HR officer is responsible; the construction engineer may be accountable for issues such as staff attendance; the project manager may be informed.
- Making a cake: The mother making the cake is responsible, while the father may be accountable for ensuring it is produced on time.
The matrix should be established at the beginning of the project so everyone understands their role and can follow up on assigned work.
Speaker
- Hany Ismail — Presenter from Planning Engineer Website
Rate this summary
Your feedback will help improve summaries.
Improve this summary
Reprocess with a stronger model when the summary feels incomplete or inaccurate.
Translate summary in another language
Ask questions to this video
Chat for follow-up questions, clarifications, and source-backed answers.