---
# System prepended metadata

title: 'Education PreDocket :dog::canned_food: session 5/19 :yellow_heart:'

---

# Education PreDocket :dog::canned_food: session 5/19 :yellow_heart:
## Location: team3.caseflowdemo.com
## Goal
The purpose of the [dogfooding](https://deviq.com/practices/dogfooding) session is to run through as many relevant user story scenarios that we're able to come up with.  Ideally, the individual scenarios work perfectly as intended.  </br>
However, the reason it's important that we go through this process is so that if we do indeed encounter any gaps or deficiences we can **properly document them for remediation**
## Capturing deficiencies
It's best that we document any issues that we discover in as much of a uniform standard as possible so that upon later review, we're able to parse the individual instances as easily as possible for potential translation to tech debt/tech improvement Jira tickets. </br>
Here's the template that we've decided to use for this session.  So the goal is to fill it our for each individual discovery as throroughly as possible to capture the maximum amount of information on the particular issue:
1. Description of issue
2. Expected result (what **should've** occurred)
3. Actual result (what **did** occur)
4. Steps to reproduce
5. Severity (using best judgement or by conferring with the team)
    * **Low**: (negligable, non-blocking)
    * **Medium**: (impactful, potentially blocking) 
    * **High**: (serious issue, definitely blocking)  
6. Relevant screenshot(s)
    * screenshots are easy to add to hackMD, simply capture the shot you want on your machine, then drag and drop it into the doc like so:![](https://i.imgur.com/BMGvEp7.png)

### Issue template
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
___
## Discovered Issues
### Issue 1
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
### Issue 2
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
### Issue 3
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
### Issue 4
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
### Issue 5
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
### Issue 6
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
### Issue 7
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
### Issue 8
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
### Issue 9
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
### Issue 10
1. Description of issue:
2. Expected result:
3. Actual result:
4. Steps to reproduce:
5. Severity:   
6. Relevant screenshot(s):
---
