Welcome to Project Management for SBL!
In your Strategic Business Leader (SBL) exam, you aren't just an accountant; you are a leader. One of the most important things a leader does is turn a big, "pie-in-the-sky" strategy into reality. How do they do that? Through projects! This chapter is all about how to lead and manage those projects effectively. Don't worry if this seems a bit technical at first—at its heart, project management is just about staying organized and keeping people focused on a goal.
1. What Exactly is a Project?
In business, we have "Business as Usual" (BAU) and "Projects." If you work in a bakery, baking 100 loaves of bread every morning is BAU. However, if you decide to design and launch a brand-new gluten-free product line, that is a project.
Key Characteristics of a Project:
• Temporary: It has a clear start and a clear end date.
• Unique: It isn't a routine operation; it creates something new.
• Cross-functional: It often involves people from different departments (e.g., Marketing, Finance, and IT).
• Uncertainty: Because it’s new, it carries more risk than daily tasks.
Analogy: Think of a wedding. It has a specific date (temporary), it’s a one-off event (unique), and you need a caterer, a DJ, and a florist to work together (cross-functional). That is project management!
2. The Project Life Cycle
Every project goes through four main stages. Think of this as the "circle of life" for a project.
Stage 1: Initiation
This is where we ask: "Should we do this?" We define the business case. If the project doesn't align with the company's strategy, we stop right here.
Stage 2: Planning
This is the "How?" stage. We decide on the budget, the timeline, and who is doing what. This results in the Project Initiation Document (PID).
Stage 3: Execution (and Control)
This is where the work happens. The Project Manager (PM) monitors progress to make sure things don't go off track. If there are delays, the PM must take action.
Stage 4: Completion
The project is finished and handed over to the users. We also do a Post-Implementation Review (PIR) to see what we learned.
Quick Review: Initiation -> Planning -> Execution -> Completion.
3. Key Players: Who’s Who in a Project?
In the SBL exam, you might be asked to explain the roles of different people. Here are the "Big Three":
1. The Project Sponsor (The Champion)
This is usually a senior executive. They don't do the day-to-day work, but they "own" the project. They provide the funding and make sure the project stays aligned with the business strategy. If the Project Manager has a huge problem they can't solve, they go to the Sponsor.
2. The Project Manager (The Conductor)
This person is responsible for the day-to-day running of the project. They manage the team, the budget, and the schedule. Their job is to deliver the project "on time, on budget, and to specification."
3. The Project Team (The Workers)
The people actually doing the tasks (the coders, the builders, the designers). They report to the Project Manager.
Common Mistake: Don't confuse the Sponsor with the Manager! The Sponsor provides the "Why" and the "Money," while the Manager provides the "How" and the "Action."
4. The Project Initiation Document (PID)
The PID is the "Bible" of the project. It is a formal document that everyone agrees on before the real work starts. It prevents "Scope Creep" (where a project keeps getting bigger and more expensive because people keep adding new ideas).
What’s inside a PID?
• Objectives: What are we trying to achieve? (Use SMART goals!)
• Scope: What is included, and—just as importantly—what is NOT included?
• Constraints: Time and budget limits.
• Risks: What could go wrong?
• Roles: Who is in charge of what?
5. Managing the "Project Triangle"
This is a concept you must remember for the exam. Every project is a balancing act between three things:
1. Time: How long it takes.
2. Cost: The budget available.
3. Quality (Scope): What the project delivers.
If you change one, at least one of the others must change too. If your boss says, "I want this project finished two weeks early" (Time), you will likely need more money (Cost) or you will have to cut features (Scope).
Did you know? This is often called the "Iron Triangle" because you cannot break the laws of physics—you can't have it faster, cheaper, and better all at the same time!
6. Project Planning Tools
How do we actually track a project? There are two main tools the SBL exam loves:
A. Gantt Charts
This is a horizontal bar chart that shows the project schedule. It shows when each task starts, how long it lasts, and which tasks overlap. It’s a great visual tool for communicating the plan to stakeholders.
B. Critical Path Analysis (CPA)
The Critical Path is the sequence of tasks that takes the longest time to complete. If any task on the critical path is delayed by even one day, the entire project will be late. Tasks NOT on the critical path have "float" (extra time/wiggle room).
Key Takeaway: As a leader, you must focus your energy on the Critical Path because that's where the most risk lies.
7. Why Do Projects Fail?
SBL often asks you to critique a failing project. Common reasons include:
• Poor leadership: The Sponsor isn't interested.
• Bad Planning: The PID was weak or unrealistic.
• Inadequate Resources: Not enough money or the wrong people.
• Resistance to Change: Staff don't want the new system (this links to Change Management!).
• Lack of Communication: Stakeholders don't know what’s happening.
8. Post-Implementation Review (PIR)
Once the project is "live," the work isn't quite over. A PIR is done a few months after completion. We ask:
• Did we achieve the benefits we promised in the business case?
• Is the system working as expected?
• What can we do better next time?
Memory Aid: Think of the PIR as the "Project Report Card." It’s how the organization learns and improves for the next project.
Summary: Your SBL Checklist for Projects
• Is there a clear Business Case and Sponsor?
• Is there a PID to prevent scope creep?
• Are we monitoring the Project Triangle (Time, Cost, Quality)?
• Are we watching the Critical Path?
• Are we doing a PIR to learn from our mistakes?
Don't worry if this feels like a lot to remember. Just keep asking yourself: "If I were the leader here, how would I make sure this project stays on track?" You've got this!