Project management skills are essential for Lean Six Sigma to deliver results. Scope definition, cost estimation, resource planning, timelines, and risk management — these disciplines ensure that improvement projects translate into sustained business outcomes.
The Fundamentals
Projects are typically progressed through five sequential stages. This staged approach reduces surprises, improves resource allocation, and maintains stakeholder alignment throughout the project lifecycle.
Define the project purpose, scope, and high-level objectives. Identify key stakeholders and obtain authorization to proceed.
Develop the detailed project plan — scope, schedule, budget, resources, risks, and communication plan.
Carry out the work defined in the project plan. Direct and manage the team, procure resources, and deliver outputs.
Track progress against plan, manage changes, identify and resolve issues, and report status to stakeholders.
Formally complete the project. Obtain sign-off, document lessons learned, release resources, and celebrate success.
Lean Six Sigma Project Charter
The project charter is a foundational document in a Lean Six Sigma project. It defines the problem, scope, objectives, team, and timeline — and serves as the formal agreement between the project team and the sponsor. Every Lean Six Sigma project should start with a completed, approved charter.
Describe the financial or strategic impact of the problem. Link the project to organizational goals. Quantify the cost of the current situation where possible.
State the problem clearly — what is wrong, where it occurs, when it was first observed, and the magnitude of the impact. Avoid solutions or causes at this stage.
Define the target in measurable terms. Use SMART criteria — Specific, Measurable, Achievable, Relevant, Time-bound. Example: "Reduce invoice processing errors by X% by [date]."
Define the process boundaries (start and end points). Explicitly list what is out of scope to prevent scope creep and manage stakeholder expectations.
Name the Project Sponsor, Green Belt / Black Belt lead, team members, and process owner. Define roles and expected time commitment from each person.
Set target completion dates for each DMAIC phase — Define, Measure, Analyze, Improve, Control. A typical Green Belt project runs 3–6 months end to end.
PMBOK Framework
Earlier PMBOK Guide editions organized project management into ten knowledge areas. PMI’s current PMBOK Guide uses principles and performance domains, but these knowledge areas remain a practical way to connect project management disciplines with DMAIC.
Coordinates all project management processes and activities. Includes the project charter, project plan, and change control.
Defines and controls what is and is not included in the project. Prevents scope creep — one of the most common causes of project failure.
Plans, develops, manages, and controls the project timeline. Includes activity sequencing, duration estimating, and critical path analysis.
Plans, estimates, budgets, and controls project costs to complete the project within the approved budget.
Ensures the project and its deliverables meet the defined quality standards. Closely aligned with Lean Six Sigma tools and methods.
Identifies, acquires, and manages the team and physical resources needed to complete the project successfully.
Plans and manages timely, accurate communication between all stakeholders throughout the project lifecycle.
Identifies, analyzes, and responds to project risks. Closely linked to FMEA in Lean Six Sigma projects — both are proactive risk management tools.
Identifies all project stakeholders and manages their engagement, expectations, and influence throughout the project.
Agile Project Management
Agile project management allows stages to overlap and evolve, with teams working closely with customers and stakeholders to clarify requirements as the project progresses. This is particularly suited to software, digital, and fast-track projects where requirements are not fully known at the outset.
Sequential phases, fixed scope, detailed upfront planning
Iterative sprints, evolving scope, continuous customer collaboration
Scrum Framework
Scrum organizes work into fixed-length iterations called Sprints (typically 1–4 weeks). Three key roles, five events, and three artifacts define the framework.
Owns the product backlog, prioritizes work based on business value, and represents the customer's needs to the development team.
Facilitates the Scrum process, removes impediments, coaches the team, and protects the team from external interference.
A self-organizing, cross-functional team that delivers a potentially shippable product increment at the end of each Sprint.
An ordered list of everything needed in the product — user stories, features, bugs. The single source of work for the team.
A time-boxed iteration (1–4 weeks) during which the team completes a set of backlog items and delivers a working increment.
A visual tool showing work items in columns: To Do → In Progress → Done. Used in both Scrum and standalone Lean projects.
Reference Materials
PMI’s official page for the current PMBOK Guide, including edition details and access options.
A free visual Kanban board tool for managing improvement projects and team workflows.
A comprehensive guide to modern project management approaches — excellent overview for practitioners.
Articles, research, and learning resources covering project management practices and current topics.