Project Management Made Simple: A Practical Guide to Managing Projects Like a Pro
Project management often sounds like a complex, specialised discipline reserved for certified professionals and large corporations. But the truth is, project management is something everyone does — every day. Whether you’re organising a marketing campaign, launching a product, or even planning a family event, you’re managing a project.
In a recent mini-course, management consultant Deniz Sasal broke down project management into simple, relatable concepts. What’s usually a 10-hour course was condensed into an hour-long video that explained everything from project life cycles to process groups, scheduling, and budgeting — all in plain language.
This article summarises the essence of that lesson — how project management really works, why it’s simpler than most people think, and how you can start applying it in your own career today.
What Is a Project, Really?
At its core, a project is a temporary effort to create a unique result. It has a start, an end, and a specific goal — unlike operations, which are ongoing and repetitive.
For example:
- Building a boat = Project (has a beginning and an end).
- Running a boat factory = Operations (ongoing).
Projects can exist at different levels. A programme is a collection of related projects, and a portfolio is a collection of programmes. Understanding this hierarchy helps you see how organisations manage everything from a single task to company-wide initiatives.
Project Life Cycle vs Project Management Process
One of the most common sources of confusion in project management is mixing up these two terms.
- The Project Life Cycle is unique to your project — it’s the step-by-step sequence specific to your industry or goal. For example, an IT project might go through:
- High-level design
- Detailed design
- Coding
- Testing
- Installation
- Handover
- High-level design
It’s fully customisable.
- The Project Management Process, however, follows a universal structure. According to the Project Management Institute (PMI), there are five process groups:
- Initiating
- Planning
- Executing
- Monitoring and Controlling
- Closing
- Initiating
These are fixed — you can’t change their order. But how you apply them depends on your project’s scale and needs.
Initiation: Setting the Foundation
Every project begins with a question: Why are we doing this?
In the Initiation phase, you answer that through two key documents:
- Project Charter – a simple summary that includes objectives, scope, estimated cost, timeline, key stakeholders, and major milestones. It doesn’t need to be overly detailed; it simply seeks approval to proceed.
- Stakeholder Register – a list of everyone affected by the project. This could include your sponsor, team members, clients, or even your neighbours if you’re hammering and drilling all day (as Deniz jokes).
The goal here is to get a “go” or “no-go” decision from leadership. If the project doesn’t make sense, it’s better to stop now than waste resources later.
Planning: Turning Vision into Structure
Once the project is approved, it’s time to plan — the most detailed and strategic phase.
By the end of planning, you should have a comprehensive project plan that answers three key questions:
- What are we going to do?
- How are we going to do it?
- How will we know when we’re done?
A project plan includes:
- Requirements (what stakeholders want)
- Scope statement (what’s included and what’s not)
- Work Breakdown Structure (WBS)
- Schedule (timeline or Gantt chart)
- Cost and budget estimates
- Quality and risk considerations
The Work Breakdown Structure (WBS): Your Project’s Blueprint
The WBS is the heart of planning. It breaks your project into smaller, manageable parts — called work packages.
For instance, if your project is to build a boat, your WBS might include:
- Design: Acquire plans, adjust scale, finalise drawings
- Manufacturing: Procure materials, frame, laminate, assemble, paint
- Electronics: Source and install components
- Rigging: Procure and install mast and sails
- Testing: Pool trials and sea trials
Each of these can be broken down further until you can confidently estimate the time and cost required.
Once the WBS is ready, you combine it with your scope statement and a WBS dictionary (a description of each work package). Together, these form your Scope Baseline — your official guide for what the project includes.
Scheduling and Time Management
Using your WBS, you now estimate how long each task will take and when it will happen.
For smaller projects, a simple Gantt chart in Excel or PowerPoint works perfectly. For larger ones, tools like Microsoft Project help map dependencies and calculate the critical path — the sequence of tasks that determine your project’s overall duration.
Key scheduling strategies include:
- Fast Tracking: Doing activities in parallel to save time.
Crashing: Adding extra resources to speed up work (but at a higher cost).
Cost Management
Now you assign costs to each work package. Add up direct, indirect, fixed, and variable costs to create a budget.
In professional project management (like PMP), this includes contingency reserves (for risks) and management reserves (for unexpected changes). But in practice, many managers simply add a 20% buffer to stay safe.
Execution: Bringing the Plan to Life
This is where work actually happens. If your planning was solid, execution becomes straightforward.
As the project manager, your job is to:
- Guide your team
- Manage communication and expectations
- Prevent scope creep (unauthorised additions to the project)
- Ensure work aligns with the approved plan
Remember: execution takes the most time, but if you’ve planned well, it’s the easiest stage.
Monitoring and Controlling: Staying on Track
This stage runs in parallel with execution. You continuously measure progress against the plan.
You track:
- Scope: Are we still within defined limits?
- Schedule: Are we ahead or behind?
- Cost: Are we within budget?
- Quality and risks: Are we maintaining standards?
You also handle change requests carefully — evaluating their impact before approving or rejecting them.
Some industries use Earned Value Management (EVM) to measure performance, but as Deniz points out, real-world projects often grow non-linearly (like compound interest), making strict formulas less practical.
Closing: Wrapping Up the Project
Finishing the work doesn’t mean the project is over. The closing phase involves final administrative tasks such as:
- Handing over deliverables to the client and obtaining sign-off.
- Completing procurements and settling final payments.
- Documenting lessons learned — what worked and what didn’t.
- Releasing resources back to their departments.
- Celebrating success!
Deniz shares a personal example — his boat project wasn’t perfect, the bow leaned slightly to one side — but it still served as a valuable lesson for next time. That’s the essence of continuous improvement in project management.
Final Thoughts: Project Management Is for Everyone
Project management isn’t just for certified professionals. It’s a mindset — a structured, logical way of turning ideas into outcomes.
As Deniz says:
“Project Management is not a profession on its own. It’s a complementary discipline that helps you run your projects easily.”
Whether you’re a teacher, designer, or chemist, mastering project management helps you plan, execute, and deliver results more efficiently. It’s about clarity, structure, and adaptability — not paperwork or certificates.
So, the next time you plan a project — big or small — remember: start simple, focus on fundamentals, and enjoy the process.
Because, as Deniz concludes, “Project Management is awesome.”
