Epic
Title
One line describing the Epic
Story (The Conversation)
As a [role]
I want [feature]
So that [benefit]
Success Criteria (The business value objectives/goals)
( ) SC2 ...
( ) SCX ...
( ) F2 ...
Description/Notes
[Assumptions, Dependencies, new issues or concerns, identified risks, links to information that can assist in completing the story. This section can also include a statement about exclusions. For example: The ODE will not process Hex strings]
Links to ODE's: Definition of Ready & Definition of Done
Feature
Title
One line describing the Feature...
Description (The Conversation)
A short description of the Feature, describing the Product Use-Case or Product Functionality that the Feature is intending to implement.
Usage Metrics (The Design/Business/System Metrics)
() UM2 ...
() UMx ...
Additional Notes
[Assumptions, Dependencies, new issues or concerns, identified risks, links to information that can assist in completing the spike. This section can also include a statement about exclusions. For example: The ODE will not process Hex strings]
Links to ODE's: Definition of Ready & Definition of Done
User-Story
WYSIWYG
Raw Jira Format
Title
One line describing the Story
Story (The Conversation)
As a [role]
I want [feature]
So that [benefit]
Acceptance Criteria
() AC 2 ...
() AC X ...
Description/Notes
[Assumptions, Dependencies, new issues or concerns, identified risks, links to information that can assist in completing the story. This section can also include a statement about exclusions. For example: The ODE will not process Hex strings]
Business Value Justification
[ Describe the business value for this work-item ]
Links to ODE's: Definition of Ready & Definition of Done
User-Story Story-Point Estimation: ____ (see How we Size/Estimate)
As a [role]
I want [feature]
So that [benefit]
h3. Acceptance Criteria
() AC 1 ...
() AC 2 ...
() AC X ...
h3. Description/Notes
See issue [#264|https://github.com/usdot-jpo-ode/jpo-ode/issues/264]
h3. Business Value Justification
[ Describe the business value for this work-item ]
Links to ODE's: [Definition of Ready|https://usdotjpoode.atlassian.net/wiki/spaces/ODTD/pages/205324340/ODE+Definition+of+Ready] & [Definition of Done|https://usdotjpoode.atlassian.net/wiki/spaces/ODTD/pages/205389868/ODE+Definition+of+Done]
Task
Title
One line describing the Task
Task Description (The Conversation)
Describe the purpose and objective of the Task
Evaluation Criteria
() EC2 ...
() ECx ...
Additional Notes
[Assumptions, Dependencies, new issues or concerns, identified risks, links to information that can assist in completing the Task]
Business Value Justification
[ Describe the business value for this work-item ]
Links to ODE's: Definition of Ready & Definition of Done
Task's Story-Point Estimation: ____ (see How we Size/Estimate)
Defect
Title
One line describing the Bug
Defect Description/Summary
Describe the behavior that was observed and why it is considered a Bug.
Location, Environment, Images
- Location or URL of the defect where the behavior was observed
- Environment of the one who discovered the defect: Browser, OS, Screen Size, etc...
- Images: attach any visual image of the problem if possible
Steps to Reproduce
- Describe with as much detail as possible the steps taken to help others reproduce the bug
Evaluation Criteria
- Is this Defect linked to a User-Story? if so then link to it. Add any additional, valuable information for developers.
Links to ODE's: Definition of Ready & Definition of Done
Defect Story-Point Estimation: ____ (see How we Size/Estimate)
Spike
Title
One line describing the Spike
Time-Bound Estimation: ____ (estimate in hours or days)
Description/Intent of the Spike (The Conversation)
Describe the purpose/intent of the Spike and what we hope the outcome of spike leads to.
Evaluation Criteria
() EC2 ...
() ECx ...
Additional Notes
[Assumptions, Dependencies, new issues or concerns, identified risks, links to information that can assist in completing the spike. This section can also include a statement about exclusions. For example: The ODE will not process Hex strings]
Links to ODE's: Definition of Ready & Definition of Done
Enabler
Title
One line describing the Enabler
Time-Bound Estimation: ____ (estimate in hours or days)
Description/Intent of the Enabler (The Conversation)
Describe the purpose/intent of the Enabler and what we hope/expect the outcome of Enabler leads to.
Evaluation Criteria
() EC2 ...
() ECx ...
Additional Notes
[Assumptions, Dependencies, new issues or concerns, identified risks, links to information that can assist in completing the spike. This section can also include a statement about exclusions. For example: The ODE will not process Hex strings]
Links to ODE's: Definition of Ready & Definition of Done
Documentation Checklist
( ) Update JIRA (https://usdotjpoode.atlassian.net/browse/ODE)
( ) Update ODE user guide (https://github.com/usdot-jpo-ode/jpo-ode docs/JPO_ODE_UserGuide.docx)
( ) Create run/test documentation on GitHub wiki (https://github.com/usdot-jpo-ode/jpo-ode/wiki)
( ) Update Release Notes on GitHub (https://github.com/usdot-jpo-ode/jpo-ode ReleaseNotes.md)
( ) Update Swagger file, if applicable (https://usdot-jpo-ode.github.io/) (https://github.com/usdot-jpo-ode/jpo-ode docs/ODESwagger.yaml)
( ) Update ODE architecture document, if applicable (https://github.com/usdot-jpo-ode/jpo-ode docs/JPO ODE Architecture.docx)