Charter vs. Card: Choosing Scope Depth

You don't want the same ceremony for a one-sprint enhancement as you do for a multi-team platform refactor.

When to Use a Scope Card

The Card is your minimal, tactical contract.

• The work fits inside a single sprint or tightly bounded request.
• Dependencies are limited and known.
• Risk profile is low to medium.
• It is a slice of a bigger initiative, not the initiative itself.

When to Use a Scope Charter

The Charter is the single source of truth for messy, cross-functional work.

• Multiple teams or vendors are involved.
• Architecture, compliance, or critical data models are touched.
• Boundary decisions must be made (who owns what domain).
• Leadership expects a contract.