Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(PW) Sprint 103 Priorities & Candidates #17059

Closed
3 tasks
FranECross opened this issue Jan 25, 2024 · 1 comment
Closed
3 tasks

(PW) Sprint 103 Priorities & Candidates #17059

FranECross opened this issue Jan 25, 2024 · 1 comment
Assignees
Labels
Public Websites Scrum team in the Sitewide crew sitewide

Comments

@FranECross
Copy link

FranECross commented Jan 25, 2024

Sprint Priorities

🥅 Goals 🥅

Preview Give feedback

Candidates for Sprint 102 (Jan 31, 2024 to Feb 13, 2024 )

Drupal

Aging Content Notifications

  • Value Prop: How might we ensure a better site-user experience by ensuring alignment to our VA.gov style guide by implementing notifications of timeframes specific to a particular content type e.g. full-width banner is 7-days, Home page news spotlight block is 30 days, and Home page benefit promo block is 30 days. Configurable to allow other content types to have different timeframes assigned.

Defect (a11y): Invalid HTML for < ul > when adding Benefits Hub contacts (👉🏼Stretch/Next Sprint)

Front-end

V3 Components Opt-Out

  • Value Prop: To ensure Veteran-facing products & wizards aren't adversely affected when the Design Team updates all V1 to V3 on February 26th, we are opting out, and then will strategically updated V1 components (which have a V3 counterpart) in our products to V3

Federal Standardized Header/Footer

  • Value Prop: Continue build-out of the header, as well as forking injected header code, so we can quickly make any adjustments in order to meet March 25th in anticipation of possible contract shift, or if no contract changes, then to meet the April deadline/announcement.

Tech Debt: Remove obsolete/flaky flippers (👉🏼Stretch/Next Sprint)

Redirect Request

UX / Research

Federal Standardized Header/Footer (Cindy)

Migrate Sketch files to Figma #(this is the epic; Jordan will be chipping away at the associated stories)

Accessibility

Accessibility audit of Injected Header

  • Value Prop: Ensure a better Veteran experience by ensuring the accessibility issues discovered aren't coming from the injected header itself, and if they are, tickets will be created to fix the issues.

    
    

``

@FranECross FranECross added the Public Websites Scrum team in the Sitewide crew label Jan 25, 2024
@jilladams jilladams transferred this issue from department-of-veterans-affairs/va.gov-team Jan 26, 2024
@jilladams
Copy link
Contributor

@FranECross from today, some updates that'll inform sprint plan:

  • Per Daniel 1:1: He'll have Notifications plan in some kind of shape by end of sprint 102. Any tickets out of that are likely Drupal priority?
  • Laura got the opt out V3 ticket ready, [V3 Components] Opt-out of V3 components #16976 so I penciled that as FE goal for the sprint.
  • Per Randi in FE: Build flat HTML for TeamSites header/footer #16815 comments, the header build did not fit in the 13 points alotted there and we likely need to break that ticket up. Have scheduled 30mins we could use with Randi on Mon if she needs it. Whatever shakes out there is likely a good sprint goal for 103.
  • We have Chris back theoretically before end of sprint, but that's not fully confirmed yet. I'd suggest we plan without him, and he can pick up stretch tickets if he does make it back within sprint.

@FranECross FranECross self-assigned this Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Public Websites Scrum team in the Sitewide crew sitewide
Projects
None yet
Development

No branches or pull requests

2 participants