Sprint 17 goals - old

[bhushan-ebi]

The VF sprint should focus on strengthening the consistency, usability, optimisation, and delivery readiness of selected VF components. The aim is to ensure that design decisions, documentation needs, accessibility considerations, optimisation opportunities, and implementation requirements are clearly defined before work begins.

High-level goals

1. Align the Figma library with the latest VF release

• Review vf-footer and vf-pagination against the latest VF release.
• Update the Figma components where needed so the design library remains accurate and reliable.
• Capture any remaining gaps, dependencies, or follow-up decisions.

2. Clarify the scope for selected VF component enhancements

• Review the Hero, Card, Video, and Embed components against VF principles: design consistency, accessibility, responsiveness, optimisation, and documentation.
• Define what each ticket is intended to improve and what information is needed before sprint work begins.
• Make sure each component has a clear goal, expected outcome, and agreed scope.

3. Improve guidance for complex or overlapping component use cases

• Clarify how large images should be handled in the Hero component.
• Define best practice for links within Card body content.
• Clarify the purpose and use cases for vf-embed, vf-video, and vf-video-teaser.
• Add or update documentation where guidance is currently missing or unclear.

4. Enable clear, achievable, and aligned sprint delivery

• Ensure each ticket includes the component or use case in scope, the issue or opportunity being addressed, and the expected design or documentation output.
• Identify open questions, dependencies, or decisions needed from the team before implementation.
• Keep the sprint focused on work that is clear, actionable, and aligned across design and development.

5. Bug fixes

• Bug fix for broken Slack link
• Bug fixes for search on angular and react sites
• Header alignment fix

7. Deployment

• ebi-header-footer changes deployment