Project scope, boundaries, and constraints

Learning objectives

• Define in/out scope for a garment project.
• Distinguish constraints from assumptions.
• Control scope change through sponsor review.

Wide enough, narrow enough

Scope must be wide enough to solve the customer problem but narrow enough for one Black Belt team in one DMAIC cycle. Every scope change should be recorded and re-authorized.

Garment-factory example

Include fabric receipt through cutting issue for one knit product family; exclude supplier-development redesign and finished-goods logistics.

Method

1. Draw the boundary on the process map.
2. List in/out explicitly.
3. Identify interfaces and constraints.
4. Test the boundary against the goal.

Common mistakes

• Scoping an entire enterprise.
• Excluding the step most likely to drive the issue for political convenience.