-
Story
-
Resolution: Done
-
Major
-
None
-
None
Owner: Architect:
_<Architect is responsible for completing this section to define the
details of the story>_
Story (Required)
As a developer of Primaza, I would like to see a website focusing on documentation.
Background (Required)
A website with documentation will help developers to learn about Primaza.
Glossary
NA
Out of scope
NA
In Scope
<Defines what is included in this story>
Approach(Required)
A website with docs.
Demo requirements(Required)
NA
Dependencies
NA
Edge Case
NA
Acceptance Criteria
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