Project Management Body of Knowledge
Open in the Padhaiko app2.1 Project environment
Projects are planned and executed within internal and external conditions that shape decision-making, constrain available options, and influence project outcomes. In the Project Management Body of Knowledge (PMBOK), the project environment comprises Enterprise Environmental Factors (EEFs), Organizational Process Assets (OPAs), and broader external contextual forces.
Project Environment: EEFs and OPAs
- Enterprise Environmental Factors (EEFs): Conditions not under the immediate control of the project team that influence, constrain, or direct the project:
- Internal EEFs: Organizational culture and structure, geographic distribution of facilities/teams, existing IT infrastructure and software tools, resource availability and staff skill levels.
- External EEFs: Marketplace conditions, government regulations and data-protection laws, industry standards (ISO/IEEE), vendor ecosystems, and economic/political climate.
- Organizational Process Assets (OPAs): Internal plans, processes, policies, procedures, and knowledge bases specific to the performing organization:
- Processes & Procedures: Standard templates (charters, WBS, risk registers), change-control procedures, financial/procurement controls, and quality audit checklists.
- Corporate Knowledge Base: Historical project files, lessons-learned repositories, defect databases, and estimating benchmarks from past ICT projects.
| Dimension | Focus Areas | ICT Project Examples |
|---|---|---|
| Cultural & Social | Communication norms, work ethics, user attitudes toward technology | Resistance to new ERP workflows among legacy staff |
| International & Political | Cross-border time zones, labor laws, data-sovereignty rules | GDPR/local data residency laws for cloud-hosted apps |
| Physical & Technical | Hardware, network bandwidth, office/remote infrastructure | Unreliable ISP links at rural branch deployment sites |
| Economic & Market | Exchange rates, inflation, competitor launches, vendor pricing | USD-denominated cloud billing fluctuations |
| Organizational | Governance, leadership style, risk appetite, reporting hierarchy | Strict change-control boards in banking IT |
2.2 Managerial skills: Conceptual, technical, human-relation
Effective project managers balance three complementary managerial skill sets (originally classified by Robert L. Katz). Their relative importance shifts depending on organizational level and project complexity.
Three Essential Managerial Skills
- Conceptual Skills: The mental ability to see the project and organization as an integrated whole, understand how subsystems interact, align deliverables with strategic business goals, and anticipate long-term risks and trade-offs.
- Human-Relation (Interpersonal) Skills: The ability to communicate clearly, motivate, negotiate, resolve conflicts, build trust, and lead cross-functional teams and diverse stakeholders.
- Technical Skills: Proficiency in specific methods, processes, tools, and domain technologies—both project management techniques (WBS, CPM/PERT, EVM, risk matrices) and ICT domain fluency (SDLC, cloud architecture, cybersecurity, testing).
| Aspect | Project Manager Skill Focus | Functional Specialist Skill Focus |
|---|---|---|
| Conceptual | High (especially for large/strategic programs) | Connects architecture choices to ROI, scope boundaries, and enterprise strategy |
| Human-Relation | Very High across all project levels | Facilitates daily standups, negotiates with sponsors, manages vendor/team conflicts |
| Technical | Moderate to High (broad fluency rather than deep coding) | Understands estimation realism, reviews schedules/budgets, assesses technical risks |
2.3 Role and responsibilities of key project members
Clear accountability prevents duplicated effort and gaps in governance. Key roles in an ICT project include:
| Role | Primary Responsibilities | Authority & Accountability |
|---|---|---|
| Project Sponsor (Champion) | Provides funding and strategic direction; approves the project charter and major scope/budget changes; resolves high-level organizational roadblocks; signs off final acceptance. | Ultimate business owner of the project's ROI and business case. |
| Project Manager (PM) | Leads day-to-day planning, scheduling, budgeting, risk management, communication, and team coordination; integrates all knowledge areas to meet Triple Constraint targets. | Accountable for delivering project objectives on time, within budget, and to quality standards. |
| Project Team (Developers, Engineers, QA, Designers) | Executes technical WBS tasks (architecture, coding, network setup, testing, documentation), estimates task durations accurately, and reports actual progress and impediments. | Accountable for deliverable quality and technical execution. |
| Functional / Resource Managers | Own departmental staff, technical standards, and specialized tools; assign qualified personnel to projects and manage career/performance evaluations. | Control departmental resources and technical excellence. |
| Customer / End Users / Product Owner | Define functional requirements and acceptance criteria; prioritize backlog features; participate in reviews and User Acceptance Testing (UAT). | Validate whether the delivered system solves the business need. |
| Steering Committee / Change Control Board (CCB) | Senior leadership panel providing governance oversight, reviewing phase-gate milestones, and approving or rejecting formal change requests. | Governs cross-departmental priorities and baseline changes. |
2.4 Problem solving using problem trees
Before launching an ICT intervention or diagnosing a failing project, teams must distinguish root causes from visible symptoms. A Problem Tree (core part of the Logical Framework Approach) maps cause-and-effect relationships visually.
Problem Tree Analysis
A Problem Tree is a hierarchical diagram structured like a tree that models a complex problem by separating:
- Trunk (Focal / Core Problem): The central undesirable condition being analyzed (stated negatively as an existing situation, never as "lack of a solution").
- Roots (Causes): Underlying primary and secondary causes driving the core problem (placed below the trunk, linked upward by causal arrows).
- Branches & Leaves (Effects / Consequences): Observable symptoms and downstream impacts caused by the core problem (placed above the trunk).
Constructing and Converting a Problem Tree
- Identify Existing Problems: Brainstorm all negative conditions with stakeholders (avoiding "missing software" phrasings—write "patient records are frequently lost or delayed" instead of "no EHR system").
- Select the Focal Problem (Trunk): Choose the central problem around which most other issues cluster.
- Trace Causes Downward (Roots): Ask "Why does this happen?" repeatedly to break direct causes into deeper root causes.
- Trace Effects Upward (Branches): Ask "What does this lead to?" to map operational, financial, and reputational consequences.
- Convert to an Objective Tree (Solution Tree): Rewrite every negative statement into a positive, achievable future state:
- Causes Means (project deliverables/outputs).
- Core Problem Project Purpose (central objective).
- Effects Ends (strategic impact/goals).
[Client dissatisfaction & contract penalties] <-- Secondary Effect
^
[Missed market deadlines] [High post-release bug rate] <-- Primary Effects
^ ^
======================================================================
CORE PROBLEM (TRUNK): Software releases are consistently late & unstable
======================================================================
^ ^
[Uncontrolled scope creep] [Inadequate automated testing] <-- Primary Causes
^ ^
[No formal change-control process] [Tight deadlines skip QA phase] <-- Root Causes2.5 Project and organizational structure
The structure of the parent organization directly dictates who holds authority over project budgets, staff assignments, and technical priorities.
2.5.1 System view of project management
System View of Project Management
The system view treats a project not as an isolated set of tasks, but as an open, interconnected system operating inside a broader organization. It integrates three spheres:
- Systems Philosophy: Holistic thinking—understanding how changing one component (e.g., database architecture or sprint cadence) affects cost, schedule, security, and business operations.
- Systems Analysis: Breaking down a complex problem into components, inputs, processes, outputs, feedback loops, and interfaces to evaluate alternatives.
- Systems Management: Addressing business, technological, and organizational issues together before and during execution so technical solutions actually succeed in the organization.
2.5.2 Functional organization
In a functional organization, staff are grouped strictly by specialty (e.g., Software Development, Networking, QA, Finance, HR), each led by a Functional Manager.
- How projects run: Projects take place within a single department, or each department completes its portion independently and hands work over the wall via functional managers.
- Advantages: Clear career paths, deep technical specialization, no duplication of specialist roles, clear line of command.
- Disadvantages: No single full-time Project Manager with cross-departmental authority; slow inter-departmental coordination; functional work often takes priority over project deadlines.
2.5.3 Projectized organization
In a projectized organization, the entire company is structured around projects (common in IT consulting firms, system integrators, and defense contractors).
- How projects run: Dedicated cross-functional teams report directly to a Project Manager who holds near-total authority over budget, schedule, and team assignments.
- Advantages: Fast decision-making, strong unity of command, high team loyalty to project goals, rapid communication.
- Disadvantages: Duplication of equipment and specialists across projects; team members experience "home-less" anxiety when a project ends; weaker cross-project technical standardization.
2.5.4 Matrix organization
A matrix organization blends functional and projectized structures: team members keep a permanent functional "home" while being assigned to cross-functional projects, creating a two-boss reporting structure (Functional Manager + Project Manager).
Matrix structures come in three forms based on the balance of power:
- Weak Matrix: Retains most characteristics of a functional organization; the PM acts merely as a project coordinator or expediter with little formal authority.
- Balanced Matrix: Recognizes the need for a PM, but shares authority and budget control roughly equally between the Functional Manager and the Project Manager.
- Strong Matrix: Has many characteristics of a projectized organization—full-time PMs with considerable authority and dedicated full-time project administrative staff.
- Advantages: Efficient sharing of scarce specialists (e.g., a senior DBA or security architect across multiple projects); retains functional career homes after project closure.
- Disadvantages: Violates unity of command (dual reporting creates conflict over priorities and performance reviews); higher communication and management overhead.
2.5.5 Organizational structure influences on projects
The table below summarizes how organizational structure governs authority, budget control, and PM staffing according to PMI:
| Project Characteristic | Functional | Weak Matrix | Balanced Matrix | Strong Matrix | Projectized |
|---|---|---|---|---|---|
| PM Authority | Little or none | Low | Low to moderate | Moderate to high | High to almost total |
| Resource Availability | Little or none | Low | Low to moderate | Moderate to high | High to almost total |
| Who Controls Project Budget | Functional Manager | Functional Manager | Mixed (shared) | Project Manager | Project Manager |
| PM Role | Part-time | Part-time | Full-time | Full-time | Full-time |
| PM Administrative Staff | Part-time | Part-time | Part-time | Full-time | Full-time |
Worked Out Examples
2.1
Problem Tree and Objective Tree Analysis (ICT Scenario): A mid-sized university notices that students frequently abandon its online course-registration portal during peak enrollment week, forcing manual paper registrations. Interviews reveal: (a) server crashes occur under concurrent load, (b) database queries lack indexing, (c) UI error messages are cryptic, (d) developers rushed deployment without load testing, and (e) there was no formal UAT sign-off with students.
- Construct a Problem Tree identifying the Core Problem, Causes (Roots), and Effects (Branches).
- Convert the Problem Tree into an Objective Tree showing the project purpose, means, and ends.
Mapping Causes, Core Problem, and Effects (Problem Tree):
- Effects (Branches — consequences): Forced fallback to manual paper registration administrative overload, long student queues, and enrollment delays.
- Core Problem (Trunk): High student abandonment of the online course-registration portal during peak enrollment.
- Primary Causes (Upper Roots):
- Frequent portal crashes and slow response under concurrent load.
- Confusing user experience (cryptic UI error messages).
- Secondary / Root Causes (Deep Roots): 1a. Unindexed database queries causing bottlenecks. 1b. Rushed deployment without load/stress testing. 2a. Absence of formal student UAT sign-off before go-live.
[Administrative overload & delayed semester start]
^
[Forced fallback to manual paper registration]
^
================================================================
CORE PROBLEM: High student abandonment of portal at peak load
================================================================
^ ^
[Server crashes & timeouts] [Cryptic UI error messages]
^ ^ ^
[Unindexed DB] [No load testing] [No student UAT]Converting to an Objective Tree (Positive Future State): Flip each negative node into an actionable positive outcome:
- Ends (Strategic Impact): Smooth, timely semester enrollment with minimal administrative paper overhead.
- Project Purpose (Central Objective): High student completion rate and reliable portal performance during peak enrollment.
- Means (Project Outputs / Deliverables):
- Portal remains stable and fast under peak concurrent load (1a) Optimize & index DB queries; (1b) Execute automated load testing before release.
- Clear, intuitive UI guidance (2a) Conduct formal student UAT and revise error messages.
The Core Problem (high student abandonment during peak load) is driven by root causes (unindexed DB queries, skipped load testing, lack of student UAT) and produces effects (manual paper fallback and enrollment delays). Converting each node into a positive state yields an Objective Tree whose means are DB indexing, load testing, and formal student UAT.
2.2
Selecting an Organizational Structure Using a Weighted Scoring Matrix: An enterprise ICT department must choose an organizational structure (Functional, Balanced Matrix, or Projectized) for a high-priority -month cybersecurity zero-trust migration spanning networking, identity, and cloud teams. Management assigns criteria weights and scores ( to ) as shown below:
| Criterion | Weight | Functional | Balanced Matrix | Projectized |
|---|---|---|---|---|
| Cross-department speed & PM authority | ||||
| Dedicated focus on migration deadline | ||||
| Efficient sharing of rare security experts | ||||
| Post-project staff retention / career home |
Compute the weighted score for each structure and recommend the best choice, noting its key management risk.
Computing the weighted score for each organizational structure: For each structure, :
Interpreting the scores and identifying key risk:
- Projectized achieves the highest weighted score (), closely followed by Balanced Matrix (), while Functional () performs poorly because cross-departmental coordination and PM authority are weak.
- Recommendation: Adopt a Projectized structure (or Strong Matrix if rare security architects must still support other projects part-time).
- Key Risk to Mitigate: Under a pure Projectized setup, team members face post-project reassignment anxiety ("no functional home") and specialist duplication—mitigated by planning transition pathways back into functional security operations upon closure.
Weighted scores: Functional = , Balanced Matrix = , Projectized = . Projectized (score ) is selected for maximum speed and PM authority, provided post-project staff transition is planned early.
Exercises
Practice Exercises — Project Management Body of Knowledge
Differentiate between Enterprise Environmental Factors (EEFs) and Organizational Process Assets (OPAs) in the project environment. Give two ICT-specific examples of each.
Distinction between EEFs and OPAs:
- EEFs are internal or external conditions beyond the project team's immediate control that constrain or direct the project (e.g., company culture, local data-privacy regulations, existing cloud infrastructure, market labor rates).
- OPAs are internal plans, policies, templates, procedures, and historical knowledge bases owned by the performing organization that guide and accelerate project execution (e.g., standard WBS/risk-register templates, past software effort-estimation databases, formal change-control SOPs).
EEFs are constraining conditions outside the team's direct control (e.g., data-protection laws, legacy IT infrastructure), whereas OPAs are internal reusable processes, templates, and historical knowledge bases (e.g., standardized SDLC templates, lessons-learned repositories).
Explain Katz's three managerial skills (conceptual, human-relation, and technical) in the context of an ICT project manager. Why are human-relation skills critical even for highly technical software projects?
Three managerial skills:
- Conceptual Skills: Ability to view the project holistically, align technical architecture with business strategy, and evaluate trade-offs across scope, cost, and risk.
- Technical Skills: Fluency in project management tools (CPM, WBS, EVM) and ICT domain concepts (SDLC, architecture, testing) to validate estimates and technical risks.
- Human-Relation Skills: Ability to communicate, motivate, negotiate, and resolve conflict across developers, clients, vendors, and executives.
Why human-relation skills are critical in ICT projects: ICT projects fail more often from misunderstood requirements, stakeholder misalignment, and team conflict than from pure coding errors. Because software work is knowledge-intensive and cross-functional, human-relation skills enable accurate requirement elicitation, high team morale, and smooth conflict resolution.
An ICT project manager needs conceptual skills (big-picture strategic alignment), technical skills (PM and ICT domain fluency), and human-relation skills (leadership, communication, conflict resolution). Human-relation skills are critical because ICT projects depend on cross-functional collaboration and clear stakeholder alignment to prevent scope misunderstandings and team burnout.
Define a Problem Tree and describe the step-by-step process of building one and converting it into an Objective Tree.
Definition and structure: A Problem Tree is a cause-and-effect hierarchy consisting of a Trunk (the central focal problem), Roots (underlying primary and secondary causes), and Branches (observable effects and downstream consequences).
Construction and conversion to an Objective Tree:
- Brainstorm existing negative conditions (avoiding "lack of solution" phrasing).
- Establish the central focal problem (trunk).
- Trace direct and root causes downward ("Why?") and effects upward ("What does this lead to?").
- Convert into an Objective Tree by rephrasing every negative condition into a positive future state: causes become means, the core problem becomes the project purpose, and effects become strategic ends.
A Problem Tree maps a focal core problem (trunk) to its underlying causes (roots) and resulting effects (branches). Converting each negative node into a positive future statement transforms the diagram into an Objective Tree linking project means to the project purpose and strategic ends.
Compare Functional, Balanced Matrix, Strong Matrix, and Projectized organizational structures in terms of PM authority, budget control, resource availability, and team loyalty/career path.
Comparison across key dimensions:
- Functional: PM has little/no authority (part-time role); Functional Manager controls budget and resources; strong technical career path but weak cross-departmental coordination.
- Balanced Matrix: PM has low-to-moderate authority (full-time role); budget and resources are shared between PM and Functional Manager; dual reporting ("two bosses") creates potential priority conflicts.
- Strong Matrix: PM has moderate-to-high authority (full-time PM + full-time admin staff); PM controls budget; retains functional career homes while enabling faster project execution.
- Projectized: PM has high-to-almost-total authority over budget and dedicated resources; strong project loyalty and fast decisions, but risk of resource duplication and post-project staff insecurity.
Moving from Functional Balanced Matrix Strong Matrix Projectized, PM authority, budget control, and resource availability increase steadily from minimal/functional-controlled to near-total/PM-controlled, while functional career stability is strongest in Functional/Matrix structures and weakest in Projectized organizations.
A fintech startup is comparing a Projectized setup against a Strong Matrix setup for developing three parallel banking microservices with shared cybersecurity and database architects. Criteria weights and scores (–) are:
- Speed of single-project decisions (weight ): Projectized , Strong Matrix
- Efficient sharing of scarce specialists (weight ): Projectized , Strong Matrix
- Retention of technical standards across projects (weight ): Projectized , Strong Matrix
- Post-project career security for staff (weight ): Projectized , Strong Matrix
Calculate the weighted score for each structure and state which structure should be adopted.
Calculating weighted scores:
Decision: Because , Strong Matrix outperforms Projectized here: it gives full-time PMs substantial authority while allowing scarce security and DB architects to be shared efficiently across all three parallel projects with consistent technical standards.
Projectized = , Strong Matrix = . The fintech startup should adopt a Strong Matrix structure.