Agile & Hybrid9 min read

Lean Project Management Principles for PMP: Eliminate Waste, Deliver Value

Master Lean project management principles for the PMP exam. Learn the 7 wastes, value stream mapping, and how Lean thinking applies to PM.

Leanwaste eliminationvalue stream mappingPMP examLean principles

Lean Thinking in Project Management

Lean originated in Toyota's manufacturing system and has been adapted for software development, project management, and knowledge work broadly. For the PMP exam, Lean provides a lens for evaluating project efficiency — particularly around eliminating waste and maximizing value delivery. PMI's Agile Practice Guide references Lean concepts repeatedly, making them fair game for the exam.

The Five Lean Principles

  1. Define Value — Value is defined from the customer's perspective. Any activity that doesn't contribute to what the customer is willing to pay for is waste. On the PMP exam, this principle connects to stakeholder analysis and benefits realization.
  2. Map the Value Stream — Identify every step in the process from concept to delivery. Categorize each step as value-adding, necessary but non-value-adding, or pure waste. Value stream mapping makes invisible inefficiencies visible.
  3. Create Flow — Once waste is removed, ensure the remaining steps flow smoothly without interruptions, delays, or bottlenecks. In project management, this means reducing handoffs, wait times, and approval queues.
  4. Establish Pull — Instead of pushing work based on forecasts, let downstream demand pull work through the system. In agile terms, teams pull work from the backlog when they have capacity rather than having work pushed to them by a manager. Kanban's pull-based system is a direct implementation of this principle.
  5. Pursue Perfection — Continuously improve the process. There is no end state — each improvement reveals the next opportunity. This connects to the agile principle of regular reflection and adjustment.

The Seven Wastes in Project Management

Adapted from manufacturing, the seven wastes (muda) in knowledge work are:

  • Partially done work — Work in progress that isn't delivering value yet. Incomplete features, unmerged code branches, pending approvals sitting in queues.
  • Extra features — Building more than what's needed. Gold-plating, adding features "just in case," or over-engineering solutions. The Agile Manifesto's simplicity principle addresses this directly.
  • Relearning — Failing to capture knowledge, leading to the same problems being solved repeatedly. Poor documentation of decisions and lessons learned.
  • Handoffs — Each handoff between people or teams introduces delay and information loss. Cross-functional teams minimize handoffs.
  • Delays — Waiting for approvals, waiting for dependencies, waiting for decisions. Queue time is often the largest component of lead time.
  • Task switching — Context switching between multiple projects or tasks reduces efficiency by 20-40% depending on complexity. WIP limits combat this waste.
  • Defects — Bugs, errors, and rework. The earlier a defect is caught, the cheaper it is to fix. Practices like TDD and continuous integration address this.

Value Stream Mapping for Project Managers

Value stream mapping (VSM) is a diagnostic tool that visualizes the flow of work from request to delivery. For each step, you capture:

  • Processing time (how long the work actually takes)
  • Wait time (how long the work sits idle between steps)
  • Percent complete and accurate (quality at each step)

The ratio of processing time to total time (processing + waiting) reveals the process efficiency. Many organizations discover that work spends 80-90% of its time waiting — a powerful insight for improvement.

Lean on the PMP Exam

PMI doesn't test Lean certification material, but Lean concepts inform many correct answers:

  • A question about why a team is constantly busy but nothing gets finished? Think WIP limits and flow (Lean waste: partially done work).
  • A question about reducing cycle time? Think about eliminating delays and handoffs.
  • A question about scope creep or unnecessary features? Think about defining value from the customer's perspective.

Lean and Agile: The Relationship

Lean predates agile by decades, but agile practices are deeply influenced by Lean thinking. Kanban is a direct Lean adaptation. Scrum's emphasis on eliminating waste (through focused sprints and retrospectives) reflects Lean principles. Understanding Lean gives you a deeper appreciation for why agile practices work, which helps you answer "why" questions on the exam.

Explore how Lean connects to other agile and PM concepts in our topics library.

Practice what you just learned

Test your knowledge with flashcards, mini exams, and full-length practice tests on PMPprep.

Start Studying Free