OK team, so here’s what I’m thinking:
NOW
We’re sorting out goals 1 and 2.
Spree Upgrade - the bulk of our pipe bandwidth is here until June.
Product Import - @Rachel + @Matt-Yorkley on this, likely not to be done till end of Feb.
Enterprise fees - @Kirsten + @kristinalim on this, likely not to be done till end of Feb.
Subscriptions - @Rachel + @kristinalim + @Matt-Yorkley on this, will be picked up properly once the two things above are done. Likely not to be done till end of March.
Document the API - @luisramos0 is taking the lead on this, and a group of students are doing the work. It will then open up the opportunity to build on the API, if we decide this is a priority for the platform.
NEXT
As soon as we achieve goal #1 which is to have no more than 2 features in the pipe at any given time, and we get the three features through to done, we can then start working on goal #3.
Shopping on mobile - @Kirsten + next available devs will work on this, but we need to wrangle scope back from ALL THE THINGS to being the core things that will allow shoppers to successfully place an order via their mobile. And we make that experience damn fine!
Shopping S3 bugs - to keep inline with the focus in the pipe, we’ll look to do the bugs identified within the shopping experience alongside of the mobile improvements. This means that we will have a solid push at improving the shopping experience for the first half of this year.
LATER
Once the Spree Upgrade is done, we will have wider dev availability and be able to add things to the pipe inline with the 2 things at a time rule. In no particular order:
Site performance - @sauloperez will drive work on improving performance, and the first task will be to define the pain points and then determine the success indicators to be achieved. Potentially giving it a red hot go for the month of June if we decide to timebox this work.
Admin UX - This will be fixing all the dumb things that drive users crazy and aren’t that hard to fix if we’d only focus on them. It can include all the admin UI-related S3 bugs that have been reported.
Reports via Zapier - @lin_d_hop can take the lead on this one, so that other instances can see how the UK are doing reports via Zapier and can have equivalent stuff set up. Though maybe I’m understanding this one wrong in terms of scope, happy to be corrected.
Thoughts? If everyone is happy with this approach then we’ll keep on trucking!
Ping @Kirsten @maikel @Jen @tschumilas @Rachel @MyriamBoure @lin_d_hop @NickWeir @SineadOFNUK @Matt-Yorkley @sauloperez @luisramos0 @lauriewayne1 @MSFutureFarm