End of Project Sprint Review

Development Incidents

Time Allocation for Grouping

  • Code refactor delayed progress for grouping
    • Critical path
  • Story point estimation for grouping

Spotify API Completeness

  • Spotify’s API doesn’t include genre data in each Track
  • Only available in the Artist
  • Not good!
  • Used Last.fm instead

User Feedback

Received feedback from a beta tester, and other members of the tutorial group who suggested making changes to the functionality of the application, such that it would be more useful and straightforward to an actual project user.

What went poorly

  • Grouping
  • Spotify API documentation - genre data (Last.fm)
  • Pivotal feature availability
  • Pivotal software bugs
    • Arbitrary iteration planning
    • Had to apply a manual velocity override which would reset each time pivotal was reloaded

What Went Well

  • Our epics were mostly satisfied.
  • Pivotal gave us a guide on how much work should be done per week
  • Pull Request templates and deploy previews
  • Got user feedback

Advertised Features

(Epic Stories)
  • Splitting of large playlists by track information ✓
  • Spotify account integration ✓
  • Track visualisation ✓
  • Reorganise sub-playlists ✓
  • Tracks can be grouped for easier bulk edits

Additional Features

(User Feedback)
  • Select multiple playlists
  • Track list count and genre count
  • Playlist for Liked Songs

Timeline

ProjectedActual