Project Management Philosophies

A project management philosophy is a collection of guiding values and principles. It is more abstract and less prescriptive, focusing on overarching mindsets and ideals rather than detailed instructions.

A project management framework provides a structured approach for organizing work, roles, and processes. Frameworks are more prescriptive than philosophies - they outline what to do but still allow room for customization.

A project management methodology is a comprehensive set of methods, rules, and processes designed to manage a project from start to finish. Methodologies tend to be more rigid and provide an end-to-end, detailed roadmap.

Traditional Philosophy

Traditional project management emphasizes upfront planning, linear processes, and predictability. It is often used in industries where change is costly, like construction and manufacturing.

Waterfall Methodology

Waterfall is a traditional, linear, and sequential methodology where each phase of a project (planning, design, implementation, testing, deployment) must be completed before the next phase can begin. This structured method typically follows distinct stages like requirements, design, implementation, testing, and maintenance. Waterfall works best for projects with fixed, clear requirements and is characterized by thorough upfront planning and documentation. 

requirements -> design -> implementation -> testing -> maintenance

Agile Philosophy

Agile project management is an iterative, flexible approach to managing projects that emphasizes continuous improvement, collaboration, collaboration, and adaptability to change. It breaks projects into small, manageable cycles called "sprints" or "iterations," which allows teams to deliver value incrementally and respond to feedback quickly. This contrasts with traditional linear methods by allowing for adjustments throughout the project lifecycle, making it well-suited for projects with uncertain requirements, like software development.

Scrum Framework

Scrum is an Agile framework that focuses on using short time-boxed iterations called "sprints" to create a project cycle and deliver working software or products. These cycles usually last one to two weeks at a time and are organized with teams of 10 or less. Each team member has a clearly defined role, and larger team communication is done by daily standups where team members can address any blockers they might be experiencing. 

[small slice of requirements]
        ↓
      design → implementation → testing → delivery
        ↺ (repeat every 1-4 weeks in Sprints)

Kanban Framework

Kanban, or "signboard" in Japanese, is an Agile framework and visual workflow management system that focuses on continuous delivery and limiting work-in-progress (WIP) to improve efficiency. Every work item is a separate card on a board, and allows users to track progress by moving their card through specific workflows. 

[work item]
  ↓
→ To Do → In Progress → Review → Done
    (limit WIP)
  ↺ (pull new work when capacity allows)

Lean Philosophy

Lean project management is a philosophy and set of principles that emphasizes continuous improvement, maximizing value, and minimizing waste (Muda, Muri, Mura), focusing on delivering value incrementally.

  • Muda refers to activities that consume resources without providing additional value.
  • Muri refers to overuse of equipment or employees.
  • Mura refers to operational "unevenness", which decreases efficiency and productivity in the long term. 
[Customer Value Identified]
  ↓
→ Build → Measure → Learn
     ↺ (eliminate waste, optimize flow, empower teams)