Owner: Architect:

_<Architect is responsible for completing this section to define the
details of the story>_

Story (Required)

This task is to define and document the incident handling process

Background (Required)

<Describes the context or background related to this story>

Glossary

<List of new terms and definition used in this story>

Out of scope

<Defines what is not included in this story>

In Scope

<Defines what is included in this story>

Approach(Required)

_<Description of the general technical path on how to achieve the goal of
the story. Include details like json schema, class definitions>_

Demo requirements(Required)

_<Description of demo which would show the value of this story. Any demo
should also be included as part of the acceptance criteria.>_

Dependencies

_<Describes what this story depends on. Dependent Stories and EPICs should
be linked to the story.>_

Edge Case

_<Describe edge cases to consider when implementing the story and defining
tests>_

Acceptance Criteria

_<Provides a required and minimum list of acceptance tests for this story.
More is expected as the engineer implements this story>_

Development:

QE:
Documentation: Yes/No (needs-docs|upstream-docs / no-doc)

Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
fix/Breaking change/Deprecated Functionality/Technology Preview>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

v

Legend

Unknown

Verified

Unsatisfied