Capability Guide: Governance and Scope¶

Purpose¶

Define delivery context, ownership boundaries, and scope structures that downstream modules depend on.

When To Use This Guide¶

• creating a new project/program structure
• introducing or refactoring phases and delivery organisations
• assigning scope and design package ownership
• diagnosing downstream confusion caused by weak governance context

Modules In Scope¶

• portfolio_mgmt
• scope_mgmt

Inputs and Preconditions¶

• project/program naming and ownership model agreed
• delivery phases and timeline assumptions defined
• team/organisation ownership data available

End-to-End Workflow¶

flowchart LR
    Setup["Program and Project Setup"] --> Phase["Phase Definition"]
    Phase --> Org["Delivery Organisation Mapping"]
    Org --> Scope["Scope Allocation"]
    Scope --> Package["Design Package Structuring"]
    Package --> Assign["Assignments and Ownership"]

Step-by-Step¶

1. Create/validate program and project records.
2. Define phases and delivery milestones.
3. Map delivery organisations and ownership domains.
4. Allocate scope units to responsible teams.
5. Create design packages and assignment records.
6. Validate that downstream modules can consume the resulting context.

Key Artifacts Produced¶

• project/program/phase records
• delivery organisation records
• scope allocation records
• design package and assignment mappings

Downstream Consumers¶

• sysdef_mgmt: receives scope context for definition boundaries
• project_interface_mgmt: relies on project ownership context
• ops_mgmt: uses governance context for readiness planning

Validation Checklist¶

docker compose run --rm app sh -c "pytest portfolio_mgmt/tests scope_mgmt/tests -v"
./scripts/run_smoke_tests.sh

• phase and project context visible in UI flows
• scope assignments resolve to valid ownership entities
• no orphaned scope artifacts without project/phase context

Common Failure Modes¶