1. Definition
Project Management is the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements. A project is a temporary endeavor undertaken to create a unique product, service, or result (e.g., building a bridge, developing software, launching a marketing campaign).
2. The Triple Constraint (Iron Triangle)
Every project operates within the tension of three fundamental constraints. Changing one typically affects the others:
- Scope: What work must be done to deliver the product?
- Time: The schedule for completion (deadlines, milestones).
- Cost: The budget (resources, labor, materials).
- Quality is often considered the central outcome of balancing these three.
3. The Project Life Cycle (Phases)
Projects typically progress through five process groups (per PMI – Project Management Institute):
| Phase | Description |
|---|---|
| 1. Initiation | Define the project idea, business case, feasibility, and authorize the project (Project Charter). |
| 2. Planning | Define scope, create schedule, estimate costs, plan risk management, assemble team. |
| 3. Execution | Perform the work as defined in the plan; manage team communication and quality. |
| 4. Monitoring & Controlling | Track progress against the plan, manage changes, identify variances, implement corrective actions. |
| 5. Closure | Finalize deliverables, release resources, obtain customer acceptance, document lessons learned. |
4. Key Project Management Concepts
- Work Breakdown Structure (WBS): A hierarchical decomposition of the total scope of work into smaller, manageable components (work packages).
- Critical Path: The longest sequence of dependent tasks in a project schedule. Any delay on the critical path directly delays the project finish date.
- Stakeholder: Any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by a project (e.g., sponsor, customer, team members, regulators).
- Deliverable: Any measurable, tangible, verifiable outcome or result produced during the project.
- Milestone: A significant event or achievement in the project (e.g., “Design Approved”). Milestones have zero duration.
- Risk Management: The process of identifying, analyzing (probability/impact), planning responses for, and monitoring uncertain events that could help or hinder the project.
- Change Control: A formal process for reviewing, approving, or rejecting changes to the project baseline (scope, schedule, budget).
- Baseline: The original approved plan (scope, schedule, cost) against which project performance is measured.
5. Popular Methodologies (How you manage)
| Methodology | Core Concept | Best For |
|---|---|---|
| Waterfall | Linear, sequential phases (one completes before next starts). | Construction, manufacturing, projects with fixed requirements. |
| Agile | Iterative, incremental delivery; adaptive planning; customer collaboration. | Software development, creative projects with evolving requirements. |
| Scrum (Agile subset) | Time-boxed “sprints,” roles (Scrum Master, Product Owner), daily stand-ups. | Small cross-functional teams needing rapid feedback. |
| Kanban | Visual workflow management (board with columns: To Do, Doing, Done). | Continuous delivery, support teams, maintenance work. |
| PRINCE2 | Process-based, focuses on business justification, defined roles, management by stages. | Large government or corporate projects requiring heavy governance. |
| Lean | Maximize value by eliminating waste (inefficiency, defects, excess inventory). | Manufacturing, process improvement. |
6. Essential Documents & Artifacts
- Project Charter: Authorizes the project and gives the PM authority.
- Project Management Plan: The master document integrating all subsidiary plans (scope, schedule, cost, risk, etc.).
- RACI Matrix: A chart defining roles (Responsible, Accountable, Consulted, Informed) for each task.
- Issue Log: Tracks problems that need resolution.
- Lessons Learned: A record of what went well and what didn’t for future projects.
7. Common Roles
- Project Sponsor: The champion with authority and budget; high-level decision maker.
- Project Manager: The person accountable for achieving project objectives.
- Project Team: Those performing the work.
- PMO (Project Management Office): An internal group that standardizes processes and provides governance.
8. Success Criteria (How you measure)
A project is typically considered successful if it:
- Delivers within the approved time, cost, and scope.
- Meets quality standards and customer expectations.
- Satisfies key stakeholders.
- Achieves the intended business benefit (e.g., increased revenue, reduced risk).