Since initial discovery work (Engineering: Carlos; UX: Sara), the Account Creation API architecture shifted. Joe Niquette led those conversations and updated the identity team's implementation plan, but we don't completely know what that will look like. Once identity has something ready for our team to look at in staging, we need to:
compare the implementation to what we had modeled previously during discovery efforts,
understand the differences,
determine whether or not the error states we previously identified as needs for the FE are still technically feasible.
If not, we may need to edit our UX strategy
User story
As a Cartography team member, I want to check our team's understanding of the Account Creation API from discovery against the actual implementation in Staging. Does it work as expected?
[ ] Evaluate if the Mural (above) is still accurate
[ ] Update it if not
[ ] What errors are still possible with amended API architecture? If not all of them can be captured anymore, can enough detail be communicated to users that they will understand next steps & what the problem is?
Eng:
[ ] Getting hands on an implementation model (from identity team or other)
[ ] Are we getting clear enough error data to display alerts indicated in the Mural (above, under Notes section)
[ ] If we need to display errors in another team's space or on a benefit hub page, what is our plan for doing that? Who will do the work and what people need to be involved?
[ ] Any issues identified have been communicated back to identity team (Joe Niquette) and/or MHV API team as needed
Acceptance criteria
[ ] Have an accurate diagram of the real-life implementation the Account Creation API
[ ] We've mapped exactly what data/errors will trigger alerts in the FE user experience
[ ] UX understands how to use these errors to create meaningful alerts for the FE UX
[ ] We know what teams to work with / get validation on our plan for related alerts in the FE experience
fmccaf1
commented
1 day ago
Description
Since initial discovery work (Engineering: Carlos; UX: Sara), the Account Creation API architecture shifted. Joe Niquette led those conversations and updated the identity team's implementation plan, but we don't completely know what that will look like. Once identity has something ready for our team to look at in staging, we need to:
User story
As a Cartography team member, I want to check our team's understanding of the Account Creation API from discovery against the actual implementation in Staging. Does it work as expected?
Notes
Possible tasks:
UX:
Eng:
Acceptance criteria