<!--
تعليمات النموذج الذكي: املأ مواضع [ أضف التفاصيل... ] استنادًا إلى سياق المشروع، وراجع `parameters.md` للمتغيرات العامة.

توجيهات استيفاء الأقسام:
الحقول المطلوبة: **تاريخ الإعداد**, **مدير المشروع**, **أعدّها**, **هدف دورة تطوير**, **مدة دورة تطوير**, **أساس الطاقة الاستيعابية**, **المنقول من دورة تطوير السابقة**, **القصص الملتزم بها**, **النطاق المضاف بعد التخطيط**, **معرّف القصة**, **عنوان القصة**, **نقاط القصة**, **الأولوية**, **الحالة**, **معايير القبول**, **يتحقق منها**, **سبب الإضافة**, **طلبها**, **الأثر في دورة تطوير**, **المُسنَد والطاقة المتاحة**, **عضو الفريق**, **الدور**, **القصص المسندة**, **الطاقة المتاحة**, **فجوات المهارات والطاقة**, **اعتماديات خارج الفريق**, **المخاطر المرصودة عند التخطيط**, **المخاطرة**, **المحفّز**, **الاحتمال**, **الأثر**, **الاستجابة**, **خطة الطوارئ**
-->

<h3 align="left">{{اسم_الشركة}}</h3>
<h2 align="left">{{اسم_المشروع}} - {{معرف_المشروع}}</h2>
<h1 align="center">سجل تخطيط دورة تطوير</h1>

| **تاريخ الإعداد:** {{التاريخ_الحالي}} | **مدير المشروع:** {{اسم_مدير_المشروع}} | **أعدّها:** {{معد_الوثيقة}} |
| ---: | --- | --- |
---

## 1. إطار دورة تطوير

<!-- الحقول في هذا القسم: هدف دورة تطوير، مدة دورة تطوير، أساس الطاقة الاستيعابية، المنقول من دورة تطوير السابقة -->

**هدف دورة تطوير:** [ أضف التفاصيل... ]

**مدة دورة تطوير:** [ أضف التفاصيل... ]

**أساس الطاقة الاستيعابية:** [ أضف التفاصيل... ]

**المنقول من دورة تطوير السابقة:** [ أضف التفاصيل... ]

---

## 2. النطاق الملتزم به

<!-- الحقول في هذا القسم: معرّف القصة، عنوان القصة، نقاط القصة، الأولوية، الحالة، معايير القبول، يتحقق منها، سبب الإضافة، طلبها، الأثر في دورة تطوير -->

**القصص الملتزم بها:**

| معرّف القصة | عنوان القصة | نقاط القصة | الأولوية | الحالة |
| ---: | --- | --- | --- | --- |
| [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] |

**معايير القبول:**

| معرّف القصة | معايير القبول | يتحقق منها |
| ---: | --- | --- |
| [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] |

**النطاق المضاف بعد التخطيط:**

| معرّف القصة | سبب الإضافة | طلبها | الأثر في دورة تطوير |
| ---: | --- | --- | --- |
| [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] |

---

## 3. إسناد الفريق

<!-- الحقول في هذا القسم: عضو الفريق، الدور، القصص المسندة، الطاقة المتاحة، فجوات المهارات والطاقة، اعتماديات خارج الفريق -->

**المُسنَد والطاقة المتاحة:**

| عضو الفريق | الدور | القصص المسندة | الطاقة المتاحة |
| ---: | --- | --- | --- |
| [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] |

**فجوات المهارات والطاقة:** [ أضف التفاصيل... ]

**اعتماديات خارج الفريق:** [ أضف التفاصيل... ]

---

## 4. مخاطر دورة تطوير

<!-- الحقول في هذا القسم: المخاطرة، المحفّز، الاحتمال، الأثر، الاستجابة، خطة الطوارئ -->

**المخاطر المرصودة عند التخطيط:**

| المخاطرة | المحفّز | الاحتمال | الأثر | الاستجابة |
| ---: | --- | --- | --- | --- |
| [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] | [ أضف التفاصيل... ] |

**خطة الطوارئ:** [ أضف التفاصيل... ]

---

## 5. الاعتماد والتوقيعات

| الدور | الاسم | التوقيع | التاريخ |
| ---: | ---: | ---: | ---: |
| **قائد الموقع / التنفيذ** | {{اسم_قائد_الموقع}} | _______________________ | [.... -.... -.... ] |
| **مخطط المشروع / الجدولة** | {{اسم_مسؤول_الجدولة}} | _______________________ | [.... -.... -.... ] |
| **مدير المشروع** | {{اسم_مدير_المشروع}} | _______________________ | [.... -.... -.... ] |
---

<div align="left" style="margin-top: 20px; font-size: 12px; color: #7f8c8d;">
  <span>سجل التدقيق الإلكتروني: Hash SHA256: {{رمز_تجزئة_التدقيق_SHA256}}</span> <br>
 <strong>النموذج:</strong> سجل تخطيط دورة تطوير <strong>المرجع:</strong> PMO-04.03.10 <br>
 <i>تاريخ الإنشاء: {{وقت_الإنشاء}}، بواسطة <a href="https://github.com/fakhruldeen/Tasleemat/" style="color: #7f8c8d;">تسليمات</a></i>
</div>

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://tasleemat.pmo/schemas/completed/PMO-04.03.10.schema.json",
  "title": "Completed SPRINT PLANNING LOG Data Contract",
  "description": "Additive structural schema validating completed SPRINT PLANNING LOG artifact data payloads (PMO-04.03.10).",
  "type": "object",
  "properties": {
    "artifact_id": {
      "type": "string",
      "const": "PMO-04.03.10"
    },
    "metadata": {
      "type": "object",
      "properties": {
        "project_name": {
          "type": "string",
          "minLength": 1
        },
        "project_code": {
          "type": "string"
        },
        "date_prepared": {
          "type": "string",
          "format": "date"
        },
        "project_manager": {
          "type": "string",
          "minLength": 1
        },
        "prepared_by": {
          "type": "string",
          "minLength": 1
        },
        "version": {
          "type": "string"
        },
        "status": {
          "type": "string",
          "enum": [
            "draft",
            "baselined",
            "in_review",
            "approved"
          ]
        }
      },
      "required": [
        "project_name",
        "date_prepared",
        "project_manager",
        "prepared_by"
      ]
    },
    "sprint_frame": {
      "type": "object",
      "properties": {
        "sprint_goal": {
          "type": "string",
          "minLength": 1,
          "description": "The one outcome the sprint is for, stated as a capability the team can demonstrate rather than as a list of stories. A goal written as a list of stories cannot be used to reject anything, and a sprint that cannot reject anything has no goal."
        },
        "sprint_window": {
          "type": "string",
          "minLength": 1,
          "description": "The start and end dates, and the length of the sprint. The window is a constraint rather than a preference, because a sprint length that drifts produces a velocity figure that means nothing."
        },
        "capacity_basis": {
          "type": "string",
          "minLength": 1,
          "description": "How much the team believes it can take on, and what that belief is based on. Capacity stated without its basis is a wish, and the first sprint is where a capacity figure is usually found to be wrong."
        },
        "carry_over_from_the_previous_sprint": {
          "type": "string",
          "minLength": 1,
          "description": "What was not finished, and whether it has been re-estimated or carried as-is. Work carried without a new estimate is work whose estimate has never been tested."
        }
      },
      "required": [
        "sprint_goal",
        "sprint_window",
        "capacity_basis",
        "carry_over_from_the_previous_sprint"
      ]
    },
    "committed_scope": {
      "type": "object",
      "properties": {
        "story_id": {
          "type": "string",
          "minLength": 1,
          "description": "The identifier from the board, so the story can be traced when the sprint ends and the question is asked afterwards. A story with no identifier cannot be found again once it leaves the room."
        },
        "story_title": {
          "type": "string",
          "minLength": 1,
          "description": "A short name for the story, in the language the team uses for it. A title that restates the acceptance criteria instead of naming the story makes the log harder to scan than the board it came from."
        },
        "story_points": {
          "type": "string",
          "minLength": 1,
          "description": "The estimate for each story, and the scale used. Points are a relative comparison rather than a duration, so a scale changed between sprints makes two velocities incomparable."
        },
        "priority": {
          "type": "string",
          "minLength": 1,
          "description": "Order relative to the other stories in this sprint, and why this story sits where it does. Priority stated as high or medium without a reason is a label rather than an ordering."
        },
        "status": {
          "type": "string",
          "minLength": 1,
          "description": "Where the story stands at the end of the sprint, against what was committed. A status recorded only at review is too late to be useful to anyone planning the next sprint."
        },
        "acceptance_criteria": {
          "type": "string",
          "minLength": 1,
          "description": "What will be true when the story is done, written so that a person who was not in the planning meeting can tell. Criteria agreed after the work is built describe whatever was built."
        },
        "verified_by": {
          "type": "string",
          "minLength": 1,
          "description": "Who checks the criteria and when. A criterion with no named verifier is a statement of intent, and the review becomes the first time anyone looks at it."
        },
        "reason_added": {
          "type": "string",
          "minLength": 1,
          "description": "Why the story entered a sprint that had already been planned. The reason is the part worth recording, because it distinguishes a genuine discovery from a preference."
        },
        "requested_by": {
          "type": "string",
          "minLength": 1,
          "description": "Who asked for the addition, so the trade-off can be discussed with the person who wanted it. Scope added mid-sprint is how a sprint stops being a commitment."
        },
        "effect_on_sprint": {
          "type": "string",
          "minLength": 1,
          "description": "What the addition displaces, or which committed story now carries the risk of not finishing. An addition recorded without an effect reads as free, and it is not."
        }
      },
      "required": [
        "story_id",
        "story_title",
        "story_points",
        "priority",
        "status",
        "acceptance_criteria",
        "verified_by",
        "reason_added",
        "requested_by",
        "effect_on_sprint"
      ]
    },
    "team_assignment": {
      "type": "object",
      "properties": {
        "team_member": {
          "type": "string",
          "minLength": 1,
          "description": "The person, named rather than as a role, so the assignment can be checked against the person's actual availability."
        },
        "role": {
          "type": "string",
          "minLength": 1,
          "description": "The role this person holds on the sprint, which is not the same as their title outside it. The role decides who settles an argument about scope during the sprint."
        },
        "assigned_stories": {
          "type": "string",
          "minLength": 1,
          "description": "The stories this person is carrying in this sprint. The list is the thing to read for over-allocation: a person on every story in the log is a plan that has not been made yet."
        },
        "available_capacity": {
          "type": "string",
          "minLength": 1,
          "description": "How much of this person's time the sprint actually has, after other commitments. Capacity at full for every story in the log is a statement of hope rather than of plan."
        },
        "skill_and_capacity_gaps": {
          "type": "string",
          "minLength": 1,
          "description": "What the committed scope needs that the team does not have. A gap named at planning is a risk to be managed; the same gap found at the end of the sprint is a surprise."
        },
        "dependencies_outside_the_team": {
          "type": "string",
          "minLength": 1,
          "description": "What must arrive from another team, and by when. A dependency with no date is an assumption, and it is usually discovered on the last day of the sprint."
        }
      },
      "required": [
        "team_member",
        "role",
        "assigned_stories",
        "available_capacity",
        "skill_and_capacity_gaps",
        "dependencies_outside_the_team"
      ]
    },
    "risks_to_the_sprint": {
      "type": "object",
      "properties": {
        "risk": {
          "type": "string",
          "minLength": 1,
          "description": "What could stop the sprint, described as the event rather than as a feeling. A risk written as a concern cannot be managed, because there is nothing to watch for."
        },
        "trigger": {
          "type": "string",
          "minLength": 1,
          "description": "The observable signal that the risk is happening. This is what makes a risk trackable: without a trigger the item is reviewed at the end of the sprint and found to have happened."
        },
        "likelihood": {
          "type": "string",
          "minLength": 1,
          "description": "How likely the risk is, and what that judgement rests on. A bare high or low records no basis, so the next person cannot tell whether the estimate improved or the mood changed."
        },
        "impact": {
          "type": "string",
          "minLength": 1,
          "description": "What the sprint loses if the risk occurs, measured in the same units as the commitment. Impact stated as severe is not comparable to a story estimate."
        },
        "response": {
          "type": "string",
          "minLength": 1,
          "description": "What will be done about the risk while the sprint is running. A risk with no response is recorded in order to be mentioned later."
        },
        "contingency": {
          "type": "string",
          "minLength": 1,
          "description": "What will be dropped or deferred if the risk occurs. A sprint with no contingency is a sprint where the decision gets made under pressure by whoever is most available at the time."
        }
      },
      "required": [
        "risk",
        "trigger",
        "likelihood",
        "impact",
        "response",
        "contingency"
      ]
    }
  },
  "required": [
    "artifact_id",
    "metadata",
    "sprint_frame",
    "committed_scope",
    "team_assignment",
    "risks_to_the_sprint"
  ]
}

{
  "form_name": "SPRINT PLANNING LOG",
  "document_reference": "PMO-04.03.10",
  "_llm_instructions": "Populate the fields of 'SPRINT PLANNING LOG' and write the value of each field under 'Generated Value', based on the project context. Context: the project carrying reference PMO-04.03.10.",
  "fields": {
    "f01_Sprint_Goal": {
      "section": "Sprint Frame",
      "label": "Sprint Goal",
      "guidance": "The one outcome the sprint is for, stated as a capability the team can demonstrate rather than as a list of stories. A goal written as a list of stories cannot be used to reject anything, and a sprint that cannot reject anything has no goal.",
      "value": ""
    },
    "f02_Sprint_Window": {
      "section": "Sprint Frame",
      "label": "Sprint Window",
      "guidance": "The start and end dates, and the length of the sprint. The window is a constraint rather than a preference, because a sprint length that drifts produces a velocity figure that means nothing.",
      "value": ""
    },
    "f03_Capacity_Basis": {
      "section": "Sprint Frame",
      "label": "Capacity Basis",
      "guidance": "How much the team believes it can take on, and what that belief is based on. Capacity stated without its basis is a wish, and the first sprint is where a capacity figure is usually found to be wrong.",
      "value": ""
    },
    "f04_Carry_over_From_the_Previous_Sprint": {
      "section": "Sprint Frame",
      "label": "Carry-over From the Previous Sprint",
      "guidance": "What was not finished, and whether it has been re-estimated or carried as-is. Work carried without a new estimate is work whose estimate has never been tested.",
      "value": ""
    },
    "f05_Story_ID": {
      "section": "Committed Scope",
      "label": "Story ID",
      "guidance": "The identifier from the board, so the story can be traced when the sprint ends and the question is asked afterwards. A story with no identifier cannot be found again once it leaves the room.",
      "value": ""
    },
    "f06_Story_Title": {
      "section": "Committed Scope",
      "label": "Story Title",
      "guidance": "A short name for the story, in the language the team uses for it. A title that restates the acceptance criteria instead of naming the story makes the log harder to scan than the board it came from.",
      "value": ""
    },
    "f07_Story_Points": {
      "section": "Committed Scope",
      "label": "Story Points",
      "guidance": "The estimate for each story, and the scale used. Points are a relative comparison rather than a duration, so a scale changed between sprints makes two velocities incomparable.",
      "value": ""
    },
    "f08_Priority": {
      "section": "Committed Scope",
      "label": "Priority",
      "guidance": "Order relative to the other stories in this sprint, and why this story sits where it does. Priority stated as high or medium without a reason is a label rather than an ordering.",
      "value": ""
    },
    "f09_Status": {
      "section": "Committed Scope",
      "label": "Status",
      "guidance": "Where the story stands at the end of the sprint, against what was committed. A status recorded only at review is too late to be useful to anyone planning the next sprint.",
      "value": ""
    },
    "f10_Acceptance_Criteria": {
      "section": "Committed Scope",
      "label": "Acceptance Criteria",
      "guidance": "What will be true when the story is done, written so that a person who was not in the planning meeting can tell. Criteria agreed after the work is built describe whatever was built.",
      "value": ""
    },
    "f11_Verified_By": {
      "section": "Committed Scope",
      "label": "Verified By",
      "guidance": "Who checks the criteria and when. A criterion with no named verifier is a statement of intent, and the review becomes the first time anyone looks at it.",
      "value": ""
    },
    "f12_Reason_Added": {
      "section": "Committed Scope",
      "label": "Reason Added",
      "guidance": "Why the story entered a sprint that had already been planned. The reason is the part worth recording, because it distinguishes a genuine discovery from a preference.",
      "value": ""
    },
    "f13_Requested_By": {
      "section": "Committed Scope",
      "label": "Requested By",
      "guidance": "Who asked for the addition, so the trade-off can be discussed with the person who wanted it. Scope added mid-sprint is how a sprint stops being a commitment.",
      "value": ""
    },
    "f14_Effect_on_Sprint": {
      "section": "Committed Scope",
      "label": "Effect on Sprint",
      "guidance": "What the addition displaces, or which committed story now carries the risk of not finishing. An addition recorded without an effect reads as free, and it is not.",
      "value": ""
    },
    "f15_Team_Member": {
      "section": "Team Assignment",
      "label": "Team Member",
      "guidance": "The person, named rather than as a role, so the assignment can be checked against the person's actual availability.",
      "value": ""
    },
    "f16_Role": {
      "section": "Team Assignment",
      "label": "Role",
      "guidance": "The role this person holds on the sprint, which is not the same as their title outside it. The role decides who settles an argument about scope during the sprint.",
      "value": ""
    },
    "f17_Assigned_Stories": {
      "section": "Team Assignment",
      "label": "Assigned Stories",
      "guidance": "The stories this person is carrying in this sprint. The list is the thing to read for over-allocation: a person on every story in the log is a plan that has not been made yet.",
      "value": ""
    },
    "f18_Available_Capacity": {
      "section": "Team Assignment",
      "label": "Available Capacity",
      "guidance": "How much of this person's time the sprint actually has, after other commitments. Capacity at full for every story in the log is a statement of hope rather than of plan.",
      "value": ""
    },
    "f19_Skill_and_Capacity_Gaps": {
      "section": "Team Assignment",
      "label": "Skill and Capacity Gaps",
      "guidance": "What the committed scope needs that the team does not have. A gap named at planning is a risk to be managed; the same gap found at the end of the sprint is a surprise.",
      "value": ""
    },
    "f20_Dependencies_Outside_the_Team": {
      "section": "Team Assignment",
      "label": "Dependencies Outside the Team",
      "guidance": "What must arrive from another team, and by when. A dependency with no date is an assumption, and it is usually discovered on the last day of the sprint.",
      "value": ""
    },
    "f21_Risk": {
      "section": "Risks to the Sprint",
      "label": "Risk",
      "guidance": "What could stop the sprint, described as the event rather than as a feeling. A risk written as a concern cannot be managed, because there is nothing to watch for.",
      "value": ""
    },
    "f22_Trigger": {
      "section": "Risks to the Sprint",
      "label": "Trigger",
      "guidance": "The observable signal that the risk is happening. This is what makes a risk trackable: without a trigger the item is reviewed at the end of the sprint and found to have happened.",
      "value": ""
    },
    "f23_Likelihood": {
      "section": "Risks to the Sprint",
      "label": "Likelihood",
      "guidance": "How likely the risk is, and what that judgement rests on. A bare high or low records no basis, so the next person cannot tell whether the estimate improved or the mood changed.",
      "value": ""
    },
    "f24_Impact": {
      "section": "Risks to the Sprint",
      "label": "Impact",
      "guidance": "What the sprint loses if the risk occurs, measured in the same units as the commitment. Impact stated as severe is not comparable to a story estimate.",
      "value": ""
    },
    "f25_Response": {
      "section": "Risks to the Sprint",
      "label": "Response",
      "guidance": "What will be done about the risk while the sprint is running. A risk with no response is recorded in order to be mentioned later.",
      "value": ""
    },
    "f26_Contingency": {
      "section": "Risks to the Sprint",
      "label": "Contingency",
      "guidance": "What will be dropped or deferred if the risk occurs. A sprint with no contingency is a sprint where the decision gets made under pressure by whoever is most available at the time.",
      "value": ""
    }
  }
}