Five things to know about Spacebank this week:
Working collaboratively with libraries
We considerably closer to pulling off a co-design workshop with library colleagues. A huge thank you to Sue and her team for juggling rotas to help us get this over the line.
Our MVP is emerging
My favourite moments this week have been the conversations about our MVP. Some great debate about what’s minimal vs what’s viable, and what’s achievable in a time-boxed build phase. It’s exciting to watch our list of user stories mature and grow as a result of all the hard work over the last 10 weeks.
Working out where our service starts and finishes
Sebastian has been looking into where our service starts and finishes. Yet again, GDS as come up trumps with some really solid guidance on the use of subdomains and URL naming conventions.
We are mystery shopping
Liam has been looking again at our “competitors” – aka other Councils and their booking processes for libraries and community halls. Our MVP will be based on our user needs and tested workflows, and early signs are we can add value to other councils by sharing what we are developing and making our code available.
We are (almost) ready for our service assessment
Our service assessment is in a couple of weeks. We’ve been building in preparation to our sprints, which is paying off. It’s a great opportunity to look back over the last couple of months and reflect on how far we’ve come and what we’ve learnt.
We are in the final two weeks of the prototype phase. It’s like Christmas Eve – everyone is excited, nervous and a little bit over tired!
Our sprint goal is:
“Define our MVP, co-design a workflow with library colleagues, get ready for our service assessment and tie up our loose ends.”
We welcomed Emma Lewis into the team this sprint. She is a front end developer who joined Hackney this week. We’re already benefiting from a fresh pair of eyes on our work.
Things I am excited about:
- Emma and Sebastian are coding a calendar which will show the availability of library rooms. There’s some great open source options and also the potential to build our own.
- A workshop with library colleagues to co-design their work flow. We’ve been itching to collaborate more closely and can’t wait to make something together! I get to join in this time and I’m looking forward to delivering this workshop with Joy and Sam.
- The final decision on what our MVP is going to look like. We’ve come along way from our “three experiments” at the end of discovery. Richard, our Product Owner is on the case, and will be presenting his proposal to the team at the end of the sprint.
Things I am nervous about:
- The decision to do a workshop with library colleagues is the right choice, but it’s the harder option. We could have pulled together a prototype based on evidence alone and done some testing to validate it. This didn’t feel right. To get this done, we have hefty dependency on whether duty managers can swap shifts and redraft rotas. It’s a big ask in a small amount of time.
- We’ve only got 9 days this sprint, instead of 10. Every day matters at the moment. I love bank holidays, but it’s a delivery manager’s nightmare when there are 4 in 7 weeks. I have more grey hairs as a result.