dunkirk.sh
a mirror of the irs's new direct file system just in case it gets taken down
1# Bug Prioritization
2
3The following is a draft of guidelines for prioritizing bugs and incident responses that arise during tax season. For the below, we expect releases to happen weekly.\
4\
5**Rank 0 (R0): Emergency Hotfix, needs to ship as soon as possible**
6
7* You can't submit a tax return (as an individual or to a state) for \>1% of submissions
8* Refund or amount due calculation is incorrect and we know taxpayers are being affected by the issue
9* Security incident or PII is exposed
10* Direct File is down or significantly degraded
11* High traffic feature where functionality is broken or not available, and no workaround
12
13\
14**R1: Now, Showstopper fix for the next immediate release**
15
16* High traffic functionality is broken - difficult or time consuming workaround
17* Medium traffic functionality is broken for a smaller percentage of taxpayers (10 - 50%) with no workaround
18* Submissions to states or MeF are blocked for \<1% of taxpayers
19* Direct file performance is degraded (metric)
20* Refund or amount due calculation would be incorrect but circumstances to trigger the issue are rare enough that production users are unlikely to be affected before scheduled release.
21
22\
23**R2: Next, fix for the scheduled release following the next immediate release**
24
25* High value taxpayer experience improvements: Medium, high, to very high traffic feature has confusing functionality with a workaround
26* Low traffic functionality is broken for a smaller percentage of taxpayers (10 - 50%)
27
28\
29**R3: Later this tax season**
30
31* Usability feedback (via customer support or other sources): improves a medium traffic feature but there is a current workaround
32* Low traffic functionality is broken for a smaller percentage of taxpayers (\<10%)
33
34\
35**R4: Consider for this tax season**
36
37* Nice to have usability improvements, functionality not needed to perform daily work and is not time sensitive
38
39\
40**R5: backlog for future tax seasons**
41
42* Unlikely to get to these: low impact improvements
43
44## References
45
46* Last year's guidelines
47 * P0: emergency, merits a hotfix\
48 P1: a **must**/show stopper for the next scheduled release\
49 P2: a **should** for the next scheduled release\
50 P3: a **must** for this tax season\
51 P4: a **should** for this tax season\
52 P5: backlog for future tax seasons
53* Feedback from states
54 * ability to submit a return is impacted (critical)
55 * ability to accurately _calculate_ state taxes is impacted (high priority)
56 * smooth user experience for TP when doing their state taxes (lower priority)
57* Tax Logic Priority Scale
58 * P0: Yesterday (needs to ship as soon as possible, probably an incident)
59 * P1: Now (needs to be in the next regular release)
60 * P2: Next (should be release after next)
61 * P3: Later
62 * P4: Before the end of filing season
63 * P5: After filing season
64* CfA user pain score calculator: https://files.codeforamerica.org/2022/11/29092445/Client-Pain-Score-User-Pain-Score.pdf
65* Note: we chose Rank (R0) vs. Priority (P0) because there is a separate IRWorks priority that uses a different "P" scale