Closed carodew closed 4 years ago
I believe this should be closed. Design work for foxtrot will be via more current stakeholder communications.
Closing. This isn't work currently prioritized . Will depend on more recent stakeholder feedback to craft UX priorities.
@carolaponce commented on Fri Oct 19 2018
Working On****
Initiative: Supporting intake and disposition tracking for non-compensation business lines
Process documentation #1028
Initiative: Alerting users about invalid AMA issues
Next Priorities****
Initiative: User Research Plan for December Pilot
Can we schedule this in Oakland? @shanear? What to plan for (WIP)
Initiative: Allow withdrawing issues for HLRs and SCs
Initiative: Tracking power(s) of attorney at the issue level
Initiative: searching/viewing status of SCs/HLRs/Appeals
Finished Work
Initiative: Establishing AMA reviews
Initiative: Editing reviews post-intake
Initiative: supporting opt-ins from the legacy system to AMA
Parking lot
@carolaponce commented on Wed Oct 24 2018
From @shanear
department-of-veterans-affairs/caseflow#7383 department-of-veterans-affairs/caseflow#5695 department-of-veterans-affairs/caseflow#7515
1023
@jimruggiero commented on Sat Sep 07 2019
@leikkisa Putting this list on your radar for Foxtrot roadmap prep I'm going to start when I return from PTO. Prep work will be to organize all that's currently in the backlog, for Foxtrot and then meet with you to review and get your input on tech debt/prioritization and finesse my prep docs. I'd like your thoughts on the unchecked items above: is the list still accurate? any of this roll into tech debt/improvements? Not an immediate priority, but wanted you to have a few weeks to think on this. I expect to have my stuff ready for us to discuss between 9/25-10/1.
@jimruggiero commented on Sat Sep 07 2019
@carodew mind if I put this in your backlog until we determine next steps for this outstanding work?
@carodew commented on Mon Sep 09 2019
@jimruggiero sure, it can hangout with us designers. This seems like something you and I should talk through to figure out what the intent is, current needs, and break it down into smaller chunks?
@jimruggiero commented on Mon Sep 09 2019
@carodew Agreed. I'm thinking we can chat late next week or the week after. There's no rush on this.
@carodew commented on Tue Mar 31 2020
@jimruggiero should we bounce this back to @msj0nes and @rutvigupta-design to determine relevancy/next steps? This seems like a pre-epic or pre-product brief set of notes, but if it's not something to prioritize in the short term I think labeling and closing is probably the best approach.
@rutvigupta-design commented on Tue Mar 31 2020
@carodew @jimruggiero I would love to work with @msj0nes to break this into smaller incremental improvement tickets.