You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
Value Prop: Provide a better Veteran-facing experience by ensuring contact lists display correctly, thus rendering correctly when screen readers are used.
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
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.
Value Prop: Ensure a better Veteran experience by removing flippers that are no longer needed and are also flaky, occasionally causing unintended issues that are Veteran-facing.
Value Prop: Provide better experiences to Veterans across the portfolio by adopting the new global OFCIO's Federal header/footer design, and also by improved performance.
Migrate Sketch files to Figma #(this is the epic; Jordan will be chipping away at the associated stories)
Value Prop: Update the styles and comments in the mockups and prototypes moved into Figma to ensure our UX folks are able to continue providing valuable designs for Veteran-facing projects.
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.
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.
Sprint Priorities
🥅 Goals 🥅
Candidates for Sprint 102 (Jan 31, 2024 to Feb 13, 2024 )
Drupal
Aging Content Notifications
Defect (a11y): Invalid HTML for < ul > when adding Benefits Hub contacts (👉🏼Stretch/Next Sprint)
Front-end
V3 Components Opt-Out
Federal Standardized Header/Footer
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.
``
The text was updated successfully, but these errors were encountered: