Templates (Profile Versions)¶
This page provides Software Delivery Profile versions of the three CDS artifacts. These templates are intentionally lightweight. They are designed to be:
- fast to fill
- easy to review
- stable enough to support handoffs (especially into 3SF)
Use them as:
- working documents during workshops
- handoff artifacts between roles/teams
- alignment checkpoints during delivery
Meaning Handshake (Software Delivery)¶
Situation¶
- Why now? What triggered this work?
Conditions (include delivery reality)¶
- Business/organizational conditions:
- Delivery conditions:
- Access/RBAC reality:
- Environment reality:
- Security/compliance gates:
- Data realities (sources, privacy, residency):
- Operational realities (support, monitoring, incident posture):
Needs (must be true)¶
- Need 1:
- Need 2:
- Needs in tension (if any):
Frictions / Problems (what blocks needs)¶
- Friction 1:
- Friction 2:
Stakeholders & Stakes¶
- Primary beneficiaries:
- Primary payers (money/risk/reputation):
- Blockers / gate owners:
- Operators/support owners:
Dependency landscape¶
For each dependency:
- Dependency:
- Owner/team:
- Lead time (typical):
- Definition of ready:
- Escalation path:
Domain language (semantics)¶
- Key terms and meanings:
- Known ambiguous/contested terms:
- Examples/boundary cases:
Evidence & Signals¶
- Qualitative signals:
- Quantitative/operational signals:
Assumptions & Unknowns¶
- Assumption:
- Unknown:
- Disagreement (if any):
Intent Package (Software Delivery)¶
Outcome statement (change in the world)¶
- For whom:
- What changes:
- What stays protected:
Success signals & evidence¶
- Leading signals:
- Lagging signals:
- Evidence review cadence:
- Acceptance owner (for evidence):
Scope boundaries¶
- In scope:
- Out of scope:
- Unknown / to be discovered:
- Key dependencies that can reshape scope:
Constraints (non-negotiables)¶
- Security/privacy:
- Compliance/regulatory:
- Data constraints:
- Budget/time constraints:
- Other constraints:
- Constraint validation owner(s):
Tradeoffs accepted¶
- Optimizing for:
- Sacrificing:
- Tradeoff owner(s):
Quality attributes (NFRs) — must be true¶
- Reliability/availability:
- Performance:
- Observability:
- Operability/support:
- Maintainability:
- Other:
Reversibility classification¶
- Easy to reverse:
- Costly to reverse:
- Effectively irreversible (requires explicit ownership):
Assumptions & Unknowns (with disconfirmation paths where possible)¶
- Assumption:
- How it could be disproven:
- Unknown:
- How we reduce it:
Feasibility probes / learning plan (timeboxed)¶
Probe template:
- Probe:
- Timebox:
- Pass/fail signal:
- Decision it enables:
Decision rights¶
- Who decides scope changes:
- Who decides constraint exceptions (if any):
- Who approves tradeoffs/debt:
- Who approves acceptance evidence:
Revisit triggers¶
- Trigger:
- What happens when triggered:
Commitment Envelope (Software Delivery / 3SF-ready)¶
Parties, roles, decision rights (triangle owners)¶
- Client sponsor:
- Client acceptance owner:
- Client gate owners (security/compliance/access):
- Vendor accountable delivery owner:
- Product/domain authority:
- Operational authority (who runs/supports it):
Commitment statement¶
- Outcome:
- Boundary (in/out):
- Horizon (timebox/checkpoints):
- Quality bar (must be true):
Deliverables¶
- Deliverable 1:
- Deliverable 2:
Evidence & acceptance (value contract)¶
- Evidence required:
- Evidence cadence:
- Acceptance method:
- What happens if evidence is inconclusive:
Constraints & non-negotiables¶
- Constraint:
- Validation owner:
- Evidence needed (if relevant):
Tradeoffs accepted¶
- Tradeoff:
- Tradeoff owner:
Dependency obligations (explicit commitments)¶
Obligation template:
- Obligation:
- Owner:
- Lead time:
- Definition of ready:
- Escalation path:
- What happens if not met:
Governance cadence (engagement contract)¶
- Forum/cadence:
- Required attendees:
- Agenda minimum (signals, risks, decisions, dependencies):
- Decision recording method:
Change protocol¶
- What counts as change:
- How change is proposed:
- Who approves:
- Urgent change path:
- Change recording method:
Risk posture & escalation (delivery contract)¶
- Top risks:
- Early signals:
- Mitigation/rollback stance (conceptual):
- Escalation path:
Operational posture (product runs in reality)¶
- Support model / on-call:
- Monitoring/alerting expectations:
- Runbook expectations:
- Release/cutover posture (if relevant):
Revisit triggers & expiry¶
- Revisit triggers:
- Expiry / renewal point:
- What must be re-confirmed on renewal:
Notes on usage¶
- Start with v0 versions (fill only the bold essentials) when stakes are low and reversibility is high.
- Use full templates when:
- multiple teams/orgs are involved
- access/approvals are significant
- production risk or compliance risk exists
- acceptance and value evidence matter
These templates are intended to be copied into your working tools (docs, tickets, proposals) and adapted to your org context without changing the underlying CDS structure.