Skip to content

User & Stakeholder Feeback Integration Process

This document tracks improvements made across Sprint 2 and Sprint 3 based on user and stakeholder feedback.
It provides before-and-after comparisons and iteration notes to demonstrate clear integration of feedback.


  • Feedback Received:
    • Users wanted to see team crests instead of just Team Names.
    • Users wanted to be able to select and view favorite teams.
  • Team Crests:

    • Before: Teams displayed as plain text with their names Before - Team Crests
    • After: Official team logos/crests displayed from API data.
      After - Team Crests
  • Favorite Teams:

    • Before: No functionality to select or save favorite teams.
    • After: Users can select favorite teams, and see them as a priority above any other team After - Favorites

  • Feedback Received:
    • Users wanted to see league tables clearly.
    • Requested improved creativity and design for better usability.
  • Requested Improvements:
    • Enhance CSS styling for visual appeal.
    • Add timestamps to track goals/events.
    • Animate key actions (e.g., substitutions).
    • Allow live input time modifications.
    • Integrate another group’s API alongside our own.
    • Fix live input bugs (e.g., goals/subs not saving correctly).
    • Ensure player cards are visible and functional.

  • League Tables:

    • Before: No standings table available.

    • After: Dynamic league tables with ranks, points, and team crests.
      After - League Tables

  • CSS / Visual Design:

    • Before: Basic styling, limited color usage.
      Before - CSS
    • After: Improved typography, layout, and responsive design.
      After - CSS
  • Player Cards:

    • Before: Player details hidden/misaligned.
      Before - Player Cards
    • After: Player cards visible with consistent layout.
      After - Player Cards
  • Event Timestamps:

    • Before: Events displayed without timestamps.
      Before - Events
    • After: Goals, substitutions, and key actions include timestamps.
      After - Events

  • Sprint 2 focused on basic user improvements (crests, favorites).
  • Sprint 3 built on this with major stakeholder-driven changes (tables, events, animations, CSS, API integration).
  • Each feature has before/after proof, commit evidence, and iteration notes, directly satisfying rubric criteria:
    • Before-and-after comparisons.
    • Documented changes based on feedback.
    • Evidence of iterative improvement.
    • Commit history demonstrating integration.

For the original user feedback and response screenshots, see User Feedback.