Research Spike Handbook - department-of-veterans-affairs/caseflow GitHub Wiki
Resource Links
Tier 4 Snow tickets
SOPs
- List of Tier 3 SOPs in Confluence
- List of SOPs in Github
- Bat Team SOPs note: these are older SOPs that are outdated, but still have some useful information
- Irsr Tier 4 SOPs
Caseflow Wiki
Tips & Tricks
- Utilize Searches
- The slack search bar is paramount for finding past threads on certain subjects and error codes
- Use the github search bar within the caseflow repo (todo: add images)
Goals and Thought Processes
The goal of a research spike is to find an ACTION ITEM on the issue or improvement presented.
Our job as developers is to find the potential solution(s) and prepare them as a pitch for your Tech Lead/BAs and Team. The pitch can often take the form of an SOP, Automated Task, Code Change, Hotfix, Business Alteration or something entirely different. These can sometimes seem nebulous and part of purpose of the spike can sometimes be It's important to weigh out the pros and cons of each potential route along with determining the breadth of the area of affect.
Factors to take into account or questions to ask
- Are there questions for the business side?
- What parts of the code are affecting the issue?
- Is the issue a repeated issue?
- Check the Tier 4 Backlog in Jira to find other tickets with the same issue
- Jira Tier 4 Snow Ticket Backlog
- Are there already SOPs that deal with similar issues?
- Is the problem due to a failing SOP?
- Was the issue created by code that is no longer in use?
- Can you reproduce the problem locally or in UAT?
FAQ
TODO