Practice Ownership¶
Why This Exists¶
This document defines what Practices own and what they do not own.
Owner¶
The owner is the Chief Product Officer and Enterprise Architect.
Business Value¶
Ownership clarity prevents Practices from duplicating domain facts or becoming vague labels. It keeps the Digital Procurement Company aligned to One Concept, One Owner.
Ownership Rules¶
| Rule | Meaning |
|---|---|
| Practices own capabilities | A Practice is accountable for the stable business abilities it operates. |
| Domains own facts | Domain Models own source facts, lifecycle, aggregates, rules, events, APIs, and database responsibilities. |
| Digital Professionals execute | Digital Professionals execute or support capability workflows within Practice guardrails. |
| SOPs govern work | SOPs define repeatable methods, handoffs, approvals, and evidence expectations. |
| KPIs measure performance | Practice outcomes are measured through defined KPIs. |
Practice Ownership Matrix¶
| Practice | Owns capabilities related to | Does not own |
|---|---|---|
| Executive Office | Coordination, approvals, schedules, reminders, executive workflow, leadership cadence. | Source facts owned by domains. |
| Business Analysis | Customer understanding, business requirements, capability gaps, context analysis. | Organization-owned profile facts. |
| Compliance | Readiness workflows, document preparation support, compliance risk operations. | Compliance Domain source facts are owned by the Compliance Domain. |
| Procurement Intelligence | Opportunity discovery workflows, tender analysis, qualification support. | Opportunity Domain facts. |
| Bid Management | Bid planning, collaboration, proposal preparation, approvals, submission coordination. | Opportunity facts or Contract delivery facts. |
| Contract Delivery | Contract delivery operations, milestone discipline, closeout coordination. | Bid submission facts. |
| Supplier Marketplace | Supplier and marketplace operating capabilities. | Organization facts and Contract state. |
| Funding | Funding readiness and application support capabilities. | Final financial advice or Contract facts. |
| Procurement Academy | Learning and procurement education capabilities. | Operational facts from Bid, Compliance, or Contract. |
| Business Intelligence | KPI, dashboard, reporting, and insight capabilities. | Source facts behind reports. |
| Platform Administration | Configuration, support, audit review, feature flags, governance workflows. | Identity enforcement, Billing facts, Organization facts. |
Domain Ownership Boundary¶
Practices and domains are related but not the same thing.
flowchart TD
Practice[Practice]
Capability[Business Capability]
Domain[Domain]
Facts[Business Facts]
SOP[SOP]
Professional[Digital Professional]
Practice -->|owns| Capability
Domain -->|owns| Facts
Capability -->|uses| Facts
SOP -->|governs execution of| Capability
Professional -->|executes| Capability
Practical Example¶
Bid Management owns the capability to coordinate a bid workspace. The Bid Domain owns bid workspace state, proposal artefacts, approval records, and submission records. Atlas executes Bid Management workflows. SOPs define how the bid is planned, reviewed, approved, and submitted.