github twitter linkedin email rss
Transfer of Spotify Users
May 25, 2011
2 minutes read

picture alt

So here we go, after a partnership of a few years to provide Spotify with a purchase service they decided to go with their own service.

This was an interesting project as it was completely separate from the usual team workflow and with no determined set of owners/champions.

It was suppose to be fast but it felt more lost and without direction than the other projects. It did remind me a lot of the time before the teams adopted product managers, leads and kaban (and other things). There was a lot of pulling around from different people interested in the project from Support to Marketing to Development and random timelines and feature ideas were decided.

Being almost a one person development team was a difficult task, I had to single handily do the development, set targets and review them with the other areas.

In retrospective there are things that showed up that were quite useful:

  • Writing down the actual features and trying to keep that set fixed - as well as acceptance criteria for different cases.
  • Having Systest/UAT environments.
  • Specialised help from two of the product managers (content and web)
  • Having help from a tester

### What could have been done better:

  • Not taking the project out of my team.
  • Not taking the project without managing to get assistance from more developers.
  • More automated/unit/integration testing (blame this on doing development by myself)
  • Arranging for one of the product leads to have full responsibility to delegate the work and serve as a middle man to other areas.

As a side note I felt like I let my team down by dissapearing for several days and doing a parallel work flow - although the days were noted as work and I was marked in the team kaban wall bringing our day to day methodology to this would not have delayed it but actually make it faster.


Back to posts