search

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

Public resources for building on and in support of VA.gov. Visit complete Knowledge Hub:
https://depo-platform-documentation.scrollhelp.site/index.html
283 stars 204 forks source link

Public Websites: Sprint 47 Priorities #24084

Closed brianalloyd closed 3 years ago

brianalloyd commented 3 years ago

Sprint 47 Priorities (CLP Launch Trust / R&S Enhancements / Tech-debt & In-take Requests / Research and Discovery)

  1. CLP Launch / Finalize Analytics Tracking / Push user product survey for feedback / Iterative updates (audiences / Conditional rendering)
  2. R&S Search Enhancements, Implement -How do you rate / Action Bug Fixes / 508 issues
  3. Focus on Priority NIGHTWATCH issues / 'Tech-Debt' items from backlog - Mission to clear out tech-debt and mitigate risk
  4. Intake Requests for May along with some applicable Tech Debt (508/a11y issues)
  5. Post Research activities from VA.gov Wayfinding Research

Capacity Planning: PTO/Holiday's

John: 0 Brian: 1 Nick: 🐯 Team Spt. Kelson: 1 Cassandra: 0 Cindy: 0

Campaign Landing Page MVP 1.0

Resources and Support

Priority R&S Breakdown: WIP [MVP 1.1 EPIC department-of-veterans-affairs/va.gov-team#15588] [Iterate Search EPIC department-of-veterans-affairs/va.gov-team#15584] [Iterate New Feature department-of-veterans-affairs/va.gov-team#20332]

Discovery (Research & Design)

Intake Request - Techical Debt

Discussion Topics/Grooming

Benefit Hubs

Collab Cycle Tracking Template ### # Collab Cycle Tasks After copying this template into your new Sprint Priority issue, keep the Collab Cycle tasks needed for this sprint and delete the rest. - [VSP Collaboration Cycle Image](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle-visual.pdf) - [VSP Collaboration Cycle Requirements/Info](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md) - [Change Release Checklist](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/decision-tools/DRAFT_Change_Checklist.md) ## Define - [ ] **[Define] Kickoff-Intent** - #(ticket) - [ ] **[Define] Design intent** - #(ticket) ## Discover - [ ] **[Discover] Usability Testing Prep** - #(ticket) - [ ] **[Discover] Research Plan Review** - #(ticket) - [ ] **[Discover] IA Request** - #(ticket) ### [Submit Analytics request](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#analytics-request) - [ ] [Analytics request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=joanneesteban%2C+bsmartin-ep%2C+jonwehausen%2C+bmcgrady-ep&labels=analytics-insights%2C+analytics-request%2C+collaboration-cycle%2C+collab-cycle-review&template=analytics-implementation-and-qa-request-template.md&title=Analytics+Implementation+or+QA+Support+for+%5BTeam+Name+-+Feature+Name%5D) has been submitted and finalized ## Build ### [Privacy and security review]( https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#privacy-and-security-review) - [ ] Submit ticket for review: Use Privacy and Security Review template in va.gov-team-sensitive repository - [ ] Provide artifacts at least 48 hours prior to the review - [ ] Schedule/hold Privacy and Security Review - [ ] Complete any tickets that came out of Privacy/Security review (if any) ### [Submit Analytics **QA** request](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#analytics-request) - [ ] [Analytics request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=joanneesteban%2C+bsmartin-ep%2C+jonwehausen%2C+bmcgrady-ep&labels=analytics-insights%2C+analytics-request%2C+collaboration-cycle%2C+collab-cycle-review&template=analytics-implementation-and-qa-request-template.md&title=Analytics+Implementation+or+QA+Support+for+%5BTeam+Name+-+Feature+Name%5D) has been submitted and finalized ## Pre-Release ### Release Plan - [ ] Create UAT plan - [UAT Template](www.google.com)* - [UAT Plan Example](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Research/UAT/profile-research-plan-UAT.md) - [ ] Complete Release Plan - [Release Plan Example](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Profile%202.0%20Release%20Plan.md) ### Staging Review PREP (2 weeks prior to Staging Review) #### QA - QA Staging review scheduling: Have artifacts in and tag Tze 2 weeks in advance from the Staging Review. This makes it possible for Tze to get to it w/o being rushed. When you schedule the Staging review, also tag Tze in Slack. - [ ] Create list of staging users - [ ] Create list of use cases [see [Use Cases template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/design/product-use-cases-template.md)] and submit to Tze so he can create test cases/regression tests - [ ] Create “Coverage for references report” OR a add a link to the Epic for the product you are releasing #### Accessibility - [ ] Complete the [required accessibility checklist](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#staging-review) - [ ] Complete QA/Accessibility tickets that came out of Staging review prep (if any) ### Conduct Internal QA Session It is beneficial to conduct an internal QA session prior to actual QA. This consists of the team allocating 1 hour to meet look for bugs and or issues with the product. This is beneficial because the engineers and designers have in-depth knowledge of potential problem areas that QA might not have the time/resources to look into. - [ ] Internal QA has been conducted #### List of issues coming out of internal QA session: - [ ] Issue name #00000 - [ ] All issues that came from internal QA have been completed ### [Request Staging Review](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#staging-review) - [ ] Provide all required artifacts in the request - [ ] Schedule/hold staging review - [ ] Complete all IA feedback tickets - [ ] Complete all Accessibility feedback tickets - [ ] Complete all QA feedback tickets - [ ] Complete all Content feedback tickets - [ ] Complete all Design feedback tickets ### [Contact Center review]( https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#contact-center-review) - [ ] Create Product guide - [Product Guide example]() - [ ] Create Product video - [ ] Submit request for Contact Center Review - [ ] Complete Contact Center Review ### Analytics follow up on Staging - [ ] Analytics are complete - [ ] Frontend has implemented analytics data layer changes - [ ] Dashboards have been created and link directly to your OKR/KPI's - [ ] Review dashboard(s) with Analytics team to ensure understanding of all metrics/calculations - [ ] Dashboards are finalized/work correctly ### Preparing/Updating all necessary supporting documentation for your product - [ ] API calls and dependent systems [Example](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account#api-calls-and-dependent-systems) - [ ] Update product outline with updated release information and links to analytics dashboards [Product Outline Example](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account) ### Coordinate with relevant parties regarding any changes that affect other teams/stakeholders #### Ex:(re-directs, changes to content, changes that affect other teams) - [ ] Create issues in Github for changes that will take place, add dates, and tag relevant people/teams (re-directs, content changes, UI changes, etc) - [ ] Update dates/parties accordingly as launch approaches and dates are finalized ## Release ### UAT - [ ] Conduct UAT Go/No-Go meeting - [Example](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/uat-go-nogo.md) - [ ] UAT has been conducted - [ ] Issues have been logged/added to the Release Plan. [Example](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Profile%202.0%20Release%20Plan.md) - [ ] Launch-Critical UAT issues have been resolved ### Phased Launch (depends on phases in your launch)* - [ ] Conduct Launch Go/No-Go meeting - [Template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/go-no-go-meeting-template.md) - Invite your entire team, analytics, platform team members, etc - [ ] Resolve any issues (if applicable) - [ ] Continue with phased launch, resolving issues if they arise, monitoring analytics daily #### Go-live to 100% of traffic - [ ] Conduct Go-live go/no go meeting - [Example](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Profile%202.0%20Launch%20go%20no-go.md) - [ ] Resolve issues (if applicable) - [ ] Launch to 100% of users ## Monitoring - [ ] Monitor analytics daily to ensure there are no abnormalities/errors - [ ] Resolve any issues (if applicable) ## Post Launch - [ ] Fill in post-launch metrics in the Release Plan - [ ] Remove old code (if applicable) ### [Full Accessibility and 508 Office Review](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#full-accessibility-and-508-office-audit) - [ ] Request [Full 508/Accessibility Review](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=1Copenut%2C+shiragoodman&labels=508%2FAccessibility%2C+vsp-product-support%2C+collaboration-cycle%2C+collab-cycle-review&template=full-accessibility-and-508-office-audit.md&title=Full+Accessibility+%26+508+Office+Audit+%5BTeam+Name+-+Feature+Name%5D) - [ ] Complete required scans/tests - [ ] Make required changes (if any) ### [Post Launch Check-in](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#post-launch-check-in) - [ ] Update Release Plan with "post-launch questions" completed - [ ] Schedule/Hold check-in - [ ] Measure results against OKRs - [ ] Prepare next steps and potential iterations if applicable # Feedback from other teams **Platform feedback:** - The biggest blocker to a successful launch would be not implementing platform feedback earlier in the process. - It would be ideal to implement the feedback prior to the staging review. - More frequent communication of changes/issues via the slack channel would be beneficial. **Accessibility feedback:** - Include accessibility in design syncs, design-intent review, and anytime large changes are made. - More frequent communication with Accessibility (ex: Biweekly accessibility meetings) - For individual meeting/mini reviews use this [GH template](Enter link to template) - Have an "Engineering intent review" and include accessibility (in addition to design intent review). **PM Feedback:** - Update Collaboration Tracker - Add time estimates maybe - how to roll this out - put in epic format?
Kanban Board Template ### # Kanban Board _Please select a ticket and include [WIP - [NAME]] next to the ticket that is being worked._ Pick up tickets by priority on the `To Do ` section to begin and move ticket through kanban workflow until `Done`. Please include resolution steps on tickets along with instructions if for some reason you are unable to complete the ticket during this sprint. Please tag on tickets when moved to **Done** section for validation and closeout. Please connect if you have any questions or concerns in the interim. Welcome to **VFS team** (for this sprint) we're excited to have the help.
TO DO
ON-GOING - [ ] [FE] #174XX (WIP - Name)
DONE - [x] [FE] #174XX (Validate - Name)
brianalloyd commented 3 years ago

closing, S47 is a wrap!