governor

To prevent over-engineering, enforce project tier constraints using a 3-tier system (Prototype, MVP, Production) that audits scope and flags violations. This approach ensures development effort is appropriately allocated and complexity is managed throughout the lifecycle.

Project tiering assigns constraints based on project maturity, categorizing work into Prototype, MVP, or Production phases. It guides developers on appropriate complexity levels for each stage, ensuring minimal features for prototypes and robust builds for production.

Audit project scope by enforcing tier limitations that flag proposed work exceeding current maturity constraints. This scope auditing process provides anti-rationalization guidance to avoid common pitfalls and prevent development effort misallocation.

Use the prototype tier for new projects requiring quick validation with minimal features, and transition to the MVP tier when a more robust build is needed. Tier enforcement defines appropriate development effort allocation based on project maturity.

Yes, the governance approach applies to production projects by enforcing tier-appropriate complexity constraints and auditing scope. It provides anti-pattern guidance for each phase, ensuring development effort remains appropriately allocated even at production maturity.