pm-communication-plan-6a68d585dc-done-criteria.yaml

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

# yaml-language-server: $schema=../../../../../../specdojo/schemas/v1/grade-done-criteria.schema.yaml
id: prj-0001:pm-communication-plan-grade-criteria
document: prj-0001:pm-communication-plan
path: docs/ja/projects/prj-0001/030-project-management/pm-communication-plan.md
graded_at: "2026-10-15T16:22:32.254Z"
graded_by: agy-expert-executor
content_hash: 9079267db2d4ded76eaf486b2ae824cc1c2706cfb132d257fe65c54f63217edb
summary:
  satisfied: 1
  unsatisfied: 2
  total: 3
criteria:
  - id: DC-001
    text: 報告・連絡・会議体の計画を承認できる粒度で記述されていること
    roles:
      - PO
    viewpoint: vp-po-decision-readiness
    status: satisfied
  - id: DC-002
    text: 進捗・課題・リスクの報告経路が定義されていること
    roles:
      - PM
    viewpoint: vp-pm-control-reporting
    status: unsatisfied
    reason: >-
      Reporting routes for regular issues and risks connecting reporter, recipient, means, and record target are
      missing, and progress recipients are unspecified.
  - id: DC-003
    text: 関係者ごとの情報要求・関与方針が業務観点で確認できること
    roles:
      - BA
    viewpoint: vp-ba-stakeholder-clarity
    status: unsatisfied
    reason: >-
      Stakeholders with distinct information requirements and engagement policies are merged, preventing tracking from a
      business perspective.