Skip to content

Issue Template

michschl edited this page Nov 19, 2024 · 1 revision

Task Description

[Provide a detailed description of the task, including objectives and context, referencing specific standards, profiles, or documentation where necessary.]


Acceptance Criteria

The task is considered complete when:

  • [Measurable criteria that need to be met for this task to be considered done.]
  • [Measurable criteria that need to be met for this task to be considered done.]

Dependencies

  • [List any dependencies, such as other tasks, approvals, or required input from stakeholders.]

Assignees and Roles

  • Assignee: [Person responsible for completing this task]
  • Contributer(s): [List the person(s) who support to complete this task]
  • Reviewer(s): [List the person(s) responsible for reviewing this task]

Related Documentation

  • [Link to relevant profiles, standards, guidelines, or other reference materials]

Notes

  • [Any additional notes, context, or relevant details]

Meeting Checkpoints

  • Initial Review Date: [Scheduled date for first review or check-in]
  • Next Meeting Goal: Ensure the task is on track to be presented in the next stream meeting.

Definition of Ready

  • Scope is Defined: The task aligns with stream objectives and has a clear scope.
  • Acceptance Criteria: Acceptance criteria are clear, specific, and measurable.
  • Dependencies and Stakeholders: Necessary dependencies and stakeholders are identified.
  • Technical Requirements: Relevant technical details and resources are available.