Welcome to the World of Project Structure!
Hello there! We are diving into a crucial part of the CIMA E2 syllabus: Project Structure. Think of a project like building a house. You wouldn't just start laying bricks, right? You need an architect, a foreman, and a group of specialists. In business, a project needs the right "people structure" to succeed. If roles aren't clear, projects fail. By the end of these notes, you’ll understand exactly who does what and how different companies organize their project teams.
Don’t worry if this seems a bit "corporate" at first. We’ll use simple analogies to make it stick!
1. Key Roles in a Project
Every project needs a clear hierarchy. Without it, nobody knows who to ask for help or who is responsible for the budget. Let's look at the four main players:
A. The Project Sponsor (The "Owner")
The Project Sponsor is usually a senior executive who "owns" the project from a business perspective. They aren't doing the daily work, but they are the ones who want the results.
Their main jobs:
- Providing the funding and resources.
- Defining the project's overall objectives.
- Making the ultimate "Go/No-go" decisions.
- Acting as a champion for the project at the board level.
B. The Project Steering Committee / Project Board
Think of this as the "High Council." It consists of the Sponsor, senior users (those who will use the final product), and senior suppliers. Their job is to provide strategic guidance and oversight.
C. The Project Manager (The "Conductor")
The Project Manager (PM) is the person on the ground. If the Sponsor is the owner of the house, the PM is the site foreman. They make sure the project stays on track, on time, and on budget.
Quick Review: The Sponsor provides the money; the Project Manager provides the management.
D. The Project Team (The "Doers")
These are the subject matter experts (engineers, accountants, IT staff) who actually perform the project tasks. They report to the Project Manager during the life of the project.
Common Mistake to Avoid: Don't confuse the Project Sponsor with the Project Manager! The Sponsor is the "client" or "investor," while the Manager is the "employee" responsible for delivery.
Summary: Clear roles ensure accountability. The Sponsor funds it, the Board guides it, the Manager runs it, and the Team builds it.
2. Types of Project Organization Structures
How a project fits into a company depends on how that company is organized. There are three main ways to set this up:
A. Functional Structure (The "Silo" Approach)
In this setup, the project is managed within the existing departments (like Finance, HR, or Marketing). There is no dedicated project team.
Analogy: Imagine trying to organize a Christmas party, but you have to do it during your lunch break at your normal desk while still doing your regular job.
Pros: No extra cost for new staff; experts stay in their departments.
Cons: Project work often gets ignored because "business as usual" (BAU) takes priority.
B. Pure Project / Projectized Structure
Here, the project is a standalone entity. People are pulled out of their departments and work 100% on the project.
Pros: Total focus; the Project Manager has full authority.
Cons: It’s expensive; when the project ends, the team might have no jobs to go back to (this is called "project isolation").
C. Matrix Structure (The Hybrid)
This is the most common structure in the CIMA syllabus. Staff report to two bosses: their Functional Manager (regular boss) and the Project Manager (temporary project boss).
Memory Aid: The "Two-Boss" Trouble. If you see "two bosses" in an exam question, think Matrix!
Pros: Flexible; experts can share knowledge across projects.
Cons: It causes conflict. Who does the employee listen to if both bosses give different deadlines?
Did you know? Matrix structures are popular because they allow companies to be efficient with their experts, even if they are harder to manage!
Key Takeaway: Use Functional for small departmental changes, Projectized for massive one-off builds, and Matrix for complex projects requiring different experts.
3. The Project Initiation Document (PID)
The PID is the "contract" for the project. It defines the structure we just talked about. Before a project starts, the PID must be signed off.
What’s inside a PID?
1. The Business Case: Why are we doing this? (e.g., to save \( \$500,000 \) a year).
2. Scope: What is included and, more importantly, what is not included?
3. Project Organization: Who are the Sponsor, PM, and Team members?
4. Risk Log: What could go wrong?
Think of the PID as the "North Star" of the project. Whenever there is a dispute about what the project should be doing, everyone looks back at the PID.
Quick Review Box:
- Sponsor: Provides resources and high-level support.
- PM: Handles day-to-day planning and control.
- Functional Structure: High stability, low project focus.
- Matrix Structure: Shared resources, but potential boss-conflict.
- PID: The foundational document that defines everything.
Summary and Final Tips
When you are studying Project Structure for E2, always ask yourself: "Who has the power?"
In a Functional structure, the Department Manager has the power. In a Projectized structure, the Project Manager has the power. In a Matrix, the power is shared (which is why it's messy!).
Exam Tip: If a question mentions "conflicting priorities" or "staff feeling pulled in two directions," the answer is almost certainly related to the Matrix Structure.
Keep going! You're doing great. Managing projects is all about people and organization, and once you master these structures, the rest of the section will fall into place.