One Hour Upgrade - January 2017 edition

Posted in: One hour upgrade

The first One Hour Upgrade of 2017 was a compact but busy event with a number of interesting proposals put forward for consideration.

In total, there were 16 new stories added to the backlog by 7 participants. Of those, 8 stories proved particularly popular, receiving at least two votes. Given the small team on this One Hour Upgrade we experimented with each participant having fewer votes than usual.

5 stories eventually made their way on to the ‘To do’ board ready to be tackled on the Friday.

What we got done

  • Dan tidied up the User Research section of the wiki, pruning out old, redundant info and creating a centralised location for our User Research efforts.
  • Tegan fixed an accessibility issue with links in our calls-to-action. Apparently a combination of bright pink and yellow is not exactly AA compliant.
  • Iris and Sean updated the Content Publisher header with an updated product name. Tom T provided a code review within the hour.
  • Justin O and Tom D made further updates to our travel advice pages, working on a collection to bring all of the information together in a single place.
  • John worked through a number of outstanding blog posts, ensuring our blogging editorial calendar stays on track.

What we learned

  • Having fewer votes available meant participants focused on voting for stories they'd actually like to work on during the upgrade hour.
  • One Hour Upgrades should be scheduled so that they don’t fall on a Show and Tell Friday. Otherwise our available working hours on that Friday are significantly reduced.
  • If a technical or design story is in review at the end of 60 minutes, it will be considered ‘done’ and moved to the relevant board.
  • Stories that could involve soldering are not good candidates for One Hour Upgrade. However, everyone is keen to upgrade the Dragon of Deployment.

What’s next?

Our next One Hour Upgrade is scheduled for 17 February 2017.

Posted in: One hour upgrade

Respond

  • (we won't publish this)

Write a response