Staging Review [Claims & Appeals - Notice of Disagreement]

vhenry07 commented 3 years ago

Steps to complete Staging Review:

[x] VFS Product Manager: Create this issue and fill in your team and feature name in the title.
[x] VFS: Link to this issue once created in #vfs-platform-support in Slack; tag @vsp-product-support-members.
[x] VSP: Schedule meeting with VSP reviewers and requesting team attendees (as listed below)
[x] VFS: At least 4 days before scheduled meeting, you must complete list of artifacts below
[x] VFS: Verify that access information has been provided for the tool or feature in staging. Do not put staging credentials in your va.gov-team ticket; store or reference them in a .md file in the va.gov-team-sensitive repository.
[x] VSP: Create feedback tickets and link to the Staging Review ticket (if no feedback, please comment stating that).
[x] VFS: Respond to VSP feedback tickets.
[ ] VFS: Update this ticket with the product’s launch date after it has gone live.
[x] VSP: Update Platform Collaboration Point Tracker.
[ ] VFS: Close this ticket when the review is complete.

Artifacts

Link to product outline
Link to the tool or feature in staging. Do not put staging credentials in your va.gov-team ticket; store or reference them in a .md file in the va.gov-team-sensitive repository. - Staging
Staging test-user information (https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-claims.md)
Link to content brief (if applicable)
Link to or specify the artifact that represents this initiative's content source of truth - Staging. (for example, mockup, prototype, Github, Word outline, or staging or preview link)
Link to release plan with the "Planning" sections completed (in each section: Phase I, Phase II, Go Live)
Link to your product test [cases](https://dsvavsp.testrail.io/index.php?/suites/view/6&group_by=cases:section_id&group_order=asc&display_deleted_cases=0&group_id=1070)/test [plan](https://dsvavsp.testrail.io/index.php?/plans/view/1870) in TestRail with test execution logs (learn more) for QA practice area review
Link to your Coverage for References and Summary(Defects) reports in TestRail for QA practice area review
Link to verification that accessibility checks are complete:
- (preferred) Link to your TestRail VSP accessibility test plan template. OR
- Link to a doc in your product folder that indicates all required checks from the accessibility staging review prep doc are complete.
List of known issues (with links to tickets when applicable)

Meeting attendees from requesting team

Product Manager (required): Ronnie Henry
DEPO Product lead (recommended): Matt Self
DEPO Design lead (required): Ryan Thurlwell
Anyone else from your team who significantly contributed to the artifacts provided (required): Anna Carey, Robin Garrison, Christian Valla, Kevin Stachura, Asha Gross
Content, IA, accessibility, and QA specialists (if applicable): Tze Lei, Josh Kim, Angela Fowler

Scheduling

What is your preferred time slot per the VSP Collaboration Meetings Calendar? 05/10/3:30

Please note:

All times are shown in ET.
Available time slots are indicated with [CALENDAR BLOCK].
When you reserve a time slot, the reserved meeting will show up alongside the [CALENDAR BLOCK].
Please select a time slot at least 4 business days from request date.

Additional information

Please refer to the VSP Collaboration Cycle README on Github for more information about the Collaboration Cycle.

shiragoodman commented 3 years ago

hey @vhenry07 - can you please complete the attendees section? This is who we will include in the review and provide feedback to. thanks!

vhenry07 commented 3 years ago

hey @vhenry07 - can you please complete the attendees section? This is who we will include in the review and provide feedback to. thanks!

done.

shiragoodman commented 3 years ago

hey @vhenry07 - review has been scheduled for 5/10 at 3:30pm ET, however I have a couple questions...

We just completed a Midpoint Review on Friday 4/30. It seems very unlikely that your team will have made changes to the product by tomorrow - tomorrow being 4 days prior to the review. This is when we ask that all artifacts be completed and be in their ready state. Will your product be ready for review by tomorrow? If not, we might want to reschedule?
If you are planning to make changes and cannot reschedule, would you be able to let us know what feedback of ours you will be addressing so that we can review those specifically opposed to us reviewing the entire product in full again?

vhenry07 commented 3 years ago

Yes, let's reschedule. Thursday 5/20 at 1:30

shiragoodman commented 3 years ago

rescheduled for 5/20 at 1:30 pm ET. Thanks!

AngelaFowler82 commented 3 years ago

Can I get an invite?

joshkimux commented 3 years ago

@vhenry07 Hi Veronica, checking in quickly to see if foundational accessibility checks were completed and if this is ready for review in staging. The link in the ticket leads to a broken page 🙇

For some context, it usually takes the accessibility team a week to complete accessibility feedback.

Also, would it be possible to convert the staging test user information into a more accessible format using this template? This format is more intuitive for Angela to use with her screen reader.

vhenry07 commented 3 years ago

GM @shiragoodman Requesting reschedule to Tuesday, 5/25 at 11am.

allison0034 commented 3 years ago

Hi @vhenry07 I am getting an error when I try to view the staging link.

Sorry — we can’t find that page Try the search box or one of the common questions below.

allison0034 commented 3 years ago

@vhenry07 would 5/25 at 11:30 work? The 11 is already taken.

vhenry07 commented 3 years ago

Yes. Veronica Henry | PMP Sr. Product Manager | mobile 702-509-6192 | e. @.***

On Mon, May 17, 2021 at 12:06 PM Allison Christman @.***> wrote:

@vhenry07 https://github.com/vhenry07 would 5/25 at 11:30 work? The 11 is already taken.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-team/issues/24069#issuecomment-842447704, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASNVA6PFY5QF4KAEXF72TBDTOE5IPANCNFSM435H4X2Q .

Mottie commented 3 years ago

@allison0034 The updated staging link is: https://staging.va.gov/decision-reviews/board-appeal/request-board-appeal-form-10182

joshkimux commented 3 years ago

@vhenry07 would it be possible to convert the staging test user information into a more accessible format using this template? This format is more intuitive for Angela to use with her screen reader, it will also let us know what to look for specifically when testing for each user.

vhenry07 commented 3 years ago

Document updated: https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-claims2.md

tlei123 commented 3 years ago

@pjhill @ddzz , all QA test-runs are now completed, and QA-artifact links updated above in main description.

cc @vhenry07 @shiragoodman

peggygannon commented 3 years ago

Hi, @vhenry07 @kevinstachura Hello, do have a content brief from the sitewide content team for this work? If so, can you please upload it here to the ticket?

kevinstachura commented 3 years ago

@peggygannon we do! It's located here:

https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/content/content-briefs/content-brief-NOD.md

shiragoodman commented 3 years ago

hey @vhenry07 - just a reminder to please post the link to the ticket for the Sitewide Content work for the static page entry point - thank you :)

vhenry07 commented 3 years ago

Here's the ticket: https://github.com/department-of-veterans-affairs/va.gov-team/issues/24996

department-of-veterans-affairs / va.gov-team