Closed oddball-lindsay closed 3 weeks ago
Regarding understanding the MVP expectations for ARP -- @jvcAdHoc no good time with ARF's UX folks until next Weds, and we might actually be able to just use the existing Accredited Reps Crew meeting to talk about this.
On our call to explore the UX needs for accepting/declining POA requests, ARF shared some resources. Storing here for reference:
Also, Renata's notes and links to the recording (plus other resources).
This is on hold for now. Will discuss it more at next crew meeting.
@jvcAdHoc do you mind expanding on why this is on hold?
If it's related to the discussion around Accredited Rep Portal designs, my understanding was that was a "nice to have" but not required to pass this tech spec along to Sam. But perhaps I misinterpreted!
Got it, I misinterpreted your comment in Tuesday's slack up thread
It'd be nice if we can wrap this up this sprint and get something over to Sam. And if needed we can do a smaller ticket next sprint to update tech specs based on anything new we discover from the ARF/ARP discussion.
I merged the tech spec and shared it with Sam. Going to close out this ticket.
Background
Last sprint we outlined an initial tech spec, to explore if the Request POA service can exist in vets-api (#87565).
There were no major concerns, so we're on to the next step which is to create a more detailed tech spec that includes things like pseudo code and a database schema. This will help leadership fully understand how this service could function in vets-api, and serve as evidence for them to make an informed decision.
Tasks
Acceptance Criteria