Skip to content

prj-assumptions-constraints-dependencies-04a3c0d40b-done-criteria.yaml ​

このページは docs/ja/projects/prj-0001/execution/grade/criteria/prj-assumptions-constraints-dependencies-04a3c0d40b-done-criteria.yaml から生成された表示用ページです。正本は YAML ファイルであり、このページは再生成できます。

yaml
# yaml-language-server: $schema=../../../../../../specdojo/schemas/v1/grade-done-criteria.schema.yaml
id: prj-0001:prj-assumptions-constraints-dependencies-grade-criteria
document: prj-0001:prj-assumptions-constraints-dependencies
path: docs/ja/projects/prj-0001/020-project-definition/prj-assumptions-constraints-dependencies.md
graded_at: "2026-10-12T16:24:15.945Z"
graded_by: agy-expert-executor
content_hash: 0955f4b530ac5676defacfcfed9eec94f04a2e13b294154bb940de1b371a87eb
summary:
  satisfied: 1
  unsatisfied: 3
  total: 4
criteria:
  - id: DC-001
    text: 業務上の前提・制約が業務観点で識別できること
    roles:
      - BA
    viewpoint: vp-ba-requirements-completeness
    status: unsatisfied
    reason: >-
      Operational constraints and deviations regarding exclusion of personal, confidential, and non-public information
      cannot be identified from a business perspective.
  - id: DC-002
    text: 重要な前提・制約を受け入れられる情報が含まれていること
    roles:
      - PO
    viewpoint: vp-po-decision-readiness
    status: unsatisfied
    reason: >-
      Critical constraints regarding exclusion of confidential information lack monitoring and deviation procedures, and
      publication scope decisions remain unconfirmed in decision records.
  - id: DC-003
    text: 技術的制約・外部依存が識別できること
    roles:
      - ARC
    viewpoint: vp-arc-technical-constraints
    status: satisfied
  - id: DC-004
    text: 依存関係・リスクが計画・統制の観点で識別できること
    roles:
      - PM
    viewpoint: vp-pm-dependency-risk
    status: unsatisfied
    reason: >-
      Unresolved publication scope is treated as resolved in ACD-D02/ACD-D03, obscuring dependency risks to schedule and
      release gates.