1.12: Project Management Basics

Project Management Basics

A Gentle Entry into the Discipline of Project Thinking

Before you build a Work Breakdown Structure…
Before you calculate task durations, build Gantt charts, or talk about critical paths…
It helps to step back and ask a simple but powerful question:

What exactly is a project?
And what makes someone a project manager?

In this section, we’ll explore the essential building blocks of project management—the core language, structures, and concepts that form the foundation of everything else in this practicum. Whether you’re brand new to the field or just brushing up, this chapter is designed to be your on-ramp into the world of project work.

What Is a Project?

According to the Project Management Institute (PMI), a project is:

“A temporary endeavor undertaken to create a unique product, service, or result.”

Let’s break that down:

• Temporary means it has a clear beginning and end. It’s not ongoing operations.
• Unique means the outcome hasn’t been created exactly like this before—it’s not routine.
• Product, service, or result means something meaningful gets delivered in the end.

Examples of real-world projects:

• Building a mobile app
• Planning a fundraiser
• Launching a new sales process
• Designing and rolling out an employee training program
• Writing and publishing this very book

What matters is that a project has:

• A goal
• A team (even a team of one)
• A deadline
• A budget or constraints
• Stakeholders (people who care about the outcome)

Who Is the Project Manager?

In formal roles, a Project Manager (PM) is the person responsible for leading the team, managing the plan, and delivering the result on time and within scope.

But you don’t need a title to be a project manager.
Any time you are coordinating tasks, timelines, expectations, or communication across people and parts—you are managing a project.

In this practicum, that person is you.

You will play the role of a project planner and strategist, helping teams make informed decisions, track progress, and avoid costly surprises. Even if you’re not leading the whole team, your planning will shape how the work unfolds.

Core Concepts You Need to Know

Here are the pillars of project management that you’ll encounter throughout this book:📌 Scope

The scope defines what’s in the project—and what’s not.

It includes:

• Deliverables (what will be produced)
• Boundaries (what’s included or excluded)
• Objectives (what success looks like)

Unclear scope is one of the top causes of project failure. If no one knows exactly what the project is supposed to achieve, it becomes impossible to schedule or budget properly.

In this practicum, you’ll learn how to define, document, and protect scope using real tools like Scope Statements and WBS charts.

Stakeholders

Stakeholders are anyone affected by or invested in your project—positively or negatively.

Types of stakeholders:

• Customers or users
• Project sponsors or funders
• Team members
• Legal or compliance officers
• Executives
• Vendors or partners

Each stakeholder has different priorities, expectations, and constraints. Part of your job is learning how to balance these voices and create plans that respect competing needs.

Throughout the book, you’ll practice building communication plans, stakeholder maps, and executive summaries.

Project Phases (The Lifecycle)

While every project is unique, most follow a similar phased lifecycle. In PMI’s PMBOK® Guide (Project Management Body of Knowledge), these are broken down into five process groups:

1. Initiation – Defining the need, scope, and stakeholders.
2. Planning – Mapping out the work, resources, budget, and risks.
3. Execution – Doing the work and managing the team.
4. Monitoring & Controlling – Tracking progress and adjusting plans.
5. Closing – Wrapping up, capturing lessons, and delivering results.

This book focuses heavily on the Planning and Monitoring/Controlling phases—because that’s where project structure is born and refined.

Each milestone corresponds to one of these phases, helping you practice each piece in order.

The Project Charter

One of the most important early documents in any project is the Project Charter.

Think of the charter as the project’s birth certificate—a brief but official document that authorizes the project to begin.

A charter typically includes:

• Project name and sponsor
• Problem statement or need
• Scope overview
• High-level timeline and budget
• Major milestones
• Key stakeholders
• Assumptions and constraints
• Success criteria

It answers the question: What are we doing, why, and who says so?

In this practicum, you’ll often begin your planning with a memo that acts as a simplified version of a Project Charter—defining your challenge and role.

The Iron Triangle: Scope, Time, and Cost

Every project is constrained by three interlocking variables:

• Scope – What you’re delivering
• Time – How long it will take
• Cost – How much it will require

Change one, and the others shift.

Example:

• Increase the scope → you’ll likely need more time or money
• Cut the budget → you might need to reduce scope or extend the timeline

Balancing these trade-offs is one of the hardest and most important jobs of any project planner.

You’ll experience these tensions first-hand as you work through milestones involving estimation, risk, and change control.

Foundational Readings (Optional but Valuable)

If you’re curious about going deeper into the world of professional project management, here are a few trusted resources:

• PMBOK® Guide – A Guide to the Project Management Body of Knowledge
  (Project Management Institute)
  The gold standard for certified professionals. Dense but comprehensive.

• Making Things Happen by Scott Berkun
  A smart, human, and accessible read on the messy reality of running projects.

• Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland
  Great introduction to agile planning frameworks in fast-moving teams.

• The Lean Startup by Eric Ries
  Especially useful if you’re interested in planning for innovation or uncertainty.

You don’t need to read any of these before starting this book—but they can help you connect your learning to broader frameworks and industry practices.

A Final Word

Project management is not about control. It’s about clarity.
It’s not about perfection. It’s about communication and course correction.
It’s not about knowing everything. It’s about making decisions with what you know now—and improving from there.

This practicum gives you the space to practice that mindset, using real tools, grounded in real-world logic, all within the safety of structured support.

You’re not just learning to manage projects.
You’re learning to think like a planner.
And that changes everything.